Hostname
wimpykid.com
Last fetched
wimpykid.com resolves to 104.21.68.58, announced in 104.21.64.0/20 by CLOUDFLARENET - Cloudflare, Inc. in CA. wimpykid.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.68.58
104.21.64.0/20 · CLOUDFLARENET - Cloudflare, Inc. · Toronto, CA
- 172.67.187.192
172.67.176.0/20 · CLOUDFLARENET - Cloudflare, Inc. · Toronto, CA
IPv6 resolution
Attribution
Cloudflare
cdn · ORIGIN_AS, CDN
WHOIS identity
- Registrar
- iana:9
- Registrant organisation
- domain discreet privacy service attn: wimpykid.com
- Contact emails
- 17ec085b0a28fd0a7302f35c8e79d89e@domaindiscreet.com, 22e6647d0a28fd0a0fdb744e7999a64c@domaindiscreet.com, 23f531210a28fd0a32f7fa37d3673767@domaindiscreet.com, 4b1f9ccd0a28fd0a04d43787f5568a8e@domaindiscreet.com, 4f5a08360a1612334f7351e4906c88be@domaindiscreet.com, 51e8f8560a28fd0a7066621d8790289e@domaindiscreet.com, 57837499@myprivatename.com, 7286eebd0a28fd0a488981aac90a6aea@domaindiscreet.com, be45d27e0a28fd0a5a59a1c3eb548b58@domaindiscreet.com, c909abb70a28fd0a332924371547bc20@domaindiscreet.com, cfd1622c0a28fd0a2ea220c514e4f673@domaindiscreet.com, e251795b0a28fd0a5755eea7913ea9b7@domaindiscreet.com, ed3atdasqugu4bl42m9mj1ud7f@domaindiscreet.com, fd8863150a1612334e408c3c41b5f039@domaindiscreet.com
Subdomains
Showing 4 of 4 subdomains (4 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
- grace.ns.cloudflare.com
- lakas.ns.cloudflare.com
MX records
- wimpykid-com.mail.protection.outlook.com
SPF policy
- include: spf.protection.outlook.com
Threat-feed evidence
History
Related pages
Pivot from wimpykid.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: "wimpykid.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.