yellowmaps.com

Threat posture

Threat feeds listing this

0

Verdict coverage

known-clean

Nutrition Label

Resolution chain

• 104.21.66.240

  104.21.64.0/20 · CLOUDFLARENET - Cloudflare, Inc. · Toronto, CA

• 172.67.165.223

  172.67.160.0/20 · CLOUDFLARENET - Cloudflare, Inc. · Toronto, CA

• 188.114.96.3

  188.114.96.0/24 · CLOUDFLARENET - Cloudflare, Inc. · Toronto, CA

• 188.114.97.3

  188.114.97.0/24 · CLOUDFLARENET - Cloudflare, Inc. · Toronto, CA

IPv6 resolution

• 2a06:98c1:3120::3
• 2a06:98c1:3121::3

Attribution

WHOIS identity

Registrar

iana:1861

Registrant organisation

******** ******** (see notes section below on how to view unmasked data)

Contact emails

********@*****.***, info@yellowmaps.com

Subdomains

Web-graph footprint

Sampled `LINKS_TO` edges. The hyperlink layer is a pilot sample, not a web-scale crawl, so these are illustrative.

Mail and authentication

Threat-feed evidence

History

Related pages

Pivot from yellowmaps.com into the addresses, networks and registries it depends on.

• Whisper Internet Directory · Home
• TLD · .com
• Live MOAS conflicts
• IP address · 104.21.66.240
• Prefix · 104.21.64.0/20
• Network · CLOUDFLARENET - Cloudflare, Inc.
• TLD · .com
• Registrar · iana:1861
• Glossary · What is a hostname?

Cypher and MCP

Reproduce this hostname's resolution chain against graph.whisper.security:

MATCH (h:HOSTNAME {name: "yellowmaps.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 20

Or query Whisper from your own LLM workflow via the Whisper MCP server.