Hostname
goofiworld.com
Last fetched
goofiworld.com resolves to 104.21.30.207, announced in 104.21.16.0/20 by CLOUDFLARENET - Cloudflare, Inc. in CA. goofiworld.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
- 104.21.30.207
104.21.16.0/20 · CLOUDFLARENET - Cloudflare, Inc. · Toronto, CA
- 172.67.173.233
172.67.160.0/20 · CLOUDFLARENET - Cloudflare, Inc. · Toronto, CA
- 188.114.96.10
188.114.96.0/24 · CLOUDFLARENET - Cloudflare, Inc. · Toronto, CA
- 188.114.96.3
188.114.96.0/24 · CLOUDFLARENET - Cloudflare, Inc. · Toronto, CA
- 188.114.97.10
188.114.97.0/24 · CLOUDFLARENET - Cloudflare, Inc. · Toronto, CA
- 188.114.97.3
188.114.97.0/24 · CLOUDFLARENET - Cloudflare, Inc. · Toronto, CA
IPv6 resolution
Attribution
Cloudflare
cdn · ORIGIN_AS, CDN
WHOIS identity
- Registrar
- iana:472
- Registrant organisation
- nazmul arefin
- Contact emails
- mmn.arefin@gmail.com, privacy@dynadot.com
Subdomains
| Subdomain |
|---|
| capi.goofiworld.com |
| deals.goofiworld.com |
| gw.goofiworld.com |
| mail.goofiworld.com |
| webmail.goofiworld.com |
| www.goofiworld.com |
Showing 6 of 6 subdomains (6 per page).
Web-graph footprint
Sampled `LINKS_TO` edges. The hyperlink layer is a pilot sample, not a web-scale crawl, so these are illustrative.
Sample inbound links
Mail and authentication
Nameservers
- melnicoff.ns.cloudflare.com
- poppy.ns.cloudflare.com
MX records
- mail.goofiworld.com
- aspmx.l.google.com
- alt1.aspmx.l.google.com
- alt2.aspmx.l.google.com
- alt3.aspmx.l.google.com
- alt4.aspmx.l.google.com
- mx.zoho.com
- mx2.zoho.com
- mx3.zoho.com
SPF policy
- a: goofiworld.com
- mx: goofiworld.com
- include: zohomail.com
- include: sendclean.net
- include: _spf.us.sendclean.net
- ip: 103.163.246.33
- ip: 103.163.246.84
Threat-feed evidence
History
Related pages
Pivot from goofiworld.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: "goofiworld.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.