Hostname
goocto.com
Last fetched
goocto.com resolves to 13.32.241.109, announced in 13.32.241.0/24 by AMAZON-02 - Amazon.com, Inc. in US. goocto.com is not listed on any threat feed indexed by WhisperGraph; reconciled level NONE.
Threat posture
0threat score (procedure-native scale)
NONENo threats observed.
- Threat feeds listing this
- 0
- Verdict coverage
- known-clean
Nutrition Label
Resolution chain
- 13.32.241.109
13.32.241.0/24 · AMAZON-02 - Amazon.com, Inc. · New York, US
- 13.32.241.38
13.32.241.0/24 · AMAZON-02 - Amazon.com, Inc. · New York, US
- 13.32.241.63
13.32.241.0/24 · AMAZON-02 - Amazon.com, Inc. · New York, US
- 13.32.241.67
13.32.241.0/24 · AMAZON-02 - Amazon.com, Inc. · New York, US
IPv6 resolution
No AAAA record for goocto.com is recorded in WhisperGraph.
Attribution
Aws
cloud · ORIGIN_AS
WHOIS identity
- Registrar
- iana:468
- Registrant organisation
- on behalf of goocto.com owner
- Contact emails
- paul.dunn@telus.net, 14bc057a-5192-42df-b3d1-ff5c2784c42d@identity-protect.org, 7834c4d8-23fd-4c21-a5cd-10806e1572c5@identity-protect.org, 97d2ee71-73d1-41c1-a89a-2d91f64f82b8@identity-protect.org, d315b8ff-acb8-4abf-9a1a-e5f87ca11ca2@identity-protect.org, owner-9906147@goocto.com.whoisprivacyservice.org
Subdomains
| Subdomain |
|---|
| bf.goocto.com |
| webgl.goocto.com |
Showing 2 of 2 subdomains (2 per page).
Mail and authentication
Nameservers
- ns-415.awsdns-51.com
- ns-777.awsdns-33.net
- a.root-servers.net
- b.root-servers.net
- c.root-servers.net
- d.root-servers.net
- e.root-servers.net
- f.root-servers.net
- g.root-servers.net
- h.root-servers.net
- i.root-servers.net
- j.root-servers.net
- k.root-servers.net
- l.root-servers.net
- m.root-servers.net
- ns-1278.awsdns-31.org
- ns-1885.awsdns-43.co.uk
MX records
- aspmx.l.google.com
- alt1.aspmx.l.google.com
- alt2.aspmx.l.google.com
- aspmx2.googlemail.com
- aspmx3.googlemail.com
Threat-feed evidence
History
Related pages
Pivot from goocto.com into the addresses, networks and registries it depends on.
Cypher and MCP
Reproduce this hostname's resolution chain against graph.whisper.security:
MATCH (h:HOSTNAME {name: "goocto.com"})-[:RESOLVES_TO]->(ip:IPV4)
-[:ANNOUNCED_BY]->(ap:ANNOUNCED_PREFIX)-[:ROUTES]->(a:ASN)
OPTIONAL MATCH (a)-[:HAS_NAME]->(n:ASN_NAME)
RETURN ip.name AS ip, ap.name AS prefix, a.name AS asn, n.name AS network
LIMIT 20Or query Whisper from your own LLM workflow via the Whisper MCP server.