Skip to content

Hostname

yaoiscan.com

Last fetched

yaoiscan.com resolves to 104.21.36.160, announced in 104.21.32.0/20 by CLOUDFLARENET - Cloudflare, Inc. in CA. yaoiscan.com is not listed on any threat feed indexed by WhisperGraph; reconciled level NONE.

Threat posture

0threat score (procedure-native scale)

NONE

No threats observed.

Threat feeds listing this
0
Verdict coverage
known-clean

Nutrition Label

WHISPER CANON · yaoiscan.comRouting diversity1.5/10Peering density10.0/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency10.0/10Resolver footprint8.0/10canon.whisper.security/host/yaoiscan.com

Resolution chain

IPv6 resolution

Attribution

Cloudflare

cdn · ORIGIN_AS, CDN

WHOIS identity

Registrar
iana:1068
Registrant organisation
privacy service provided by withheld for privacy ehf
Contact emails
bfe644031c62479d9c2f8c2fdb497c44.protect@withheldforprivacy.com, c7e7cb97e54e446aafbecfb1703f9e27.protect@withheldforprivacy.com

Subdomains

Subdomain
img.yaoiscan.com
img1.yaoiscan.com
img3.yaoiscan.com
img4.yaoiscan.com
img5.yaoiscan.com
img6.yaoiscan.com
staging.yaoiscan.com
www.yaoiscan.com

Showing 8 of 8 subdomains (8 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

  • cheryl.ns.cloudflare.com
  • venkat.ns.cloudflare.com
  • 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

Threat-feed evidence

History

Related pages

Pivot from yaoiscan.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: "yaoiscan.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.