Skip to content

Hostname

idlescape.com

Last fetched

idlescape.com resolves to 104.21.38.60, announced in 104.21.32.0/20 by CLOUDFLARENET - Cloudflare, Inc. in CA. idlescape.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 · idlescape.comRouting diversity2.4/10Peering density10.0/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency10.0/10Resolver footprint4.6/10canon.whisper.security/host/idlescape.com

Resolution chain

IPv6 resolution

Attribution

Cloudflare

cdn · ORIGIN_AS, CDN

WHOIS identity

Registrar
iana:1068
Registrant organisation
da bo
Contact emails
bon.da@outlook.be, 2f741c95467544fba66aba65eb417ee2.protect@withheldforprivacy.com, 4d59d173fc954fc5b39c5da95614bed5.protect@withheldforprivacy.com

Subdomains

Subdomain
dev.idlescape.com
documentation.idlescape.com
monitor.idlescape.com
play.idlescape.com
shop.idlescape.com
wiki.idlescape.com
wikitest.idlescape.com
www.idlescape.com

Showing 8 of 11. View all subdomains →

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

Sample outbound links

Mail and authentication

Nameservers

  • elsa.ns.cloudflare.com
  • kara.ns.cloudflare.com
  • peyton.ns.cloudflare.com
  • ray.ns.cloudflare.com

MX records

  • aspmx.l.google.com
  • alt1.aspmx.l.google.com
  • alt2.aspmx.l.google.com
  • alt3.aspmx.l.google.com
  • alt4.aspmx.l.google.com
  • route1.mx.cloudflare.net
  • route2.mx.cloudflare.net
  • route3.mx.cloudflare.net

SPF policy

  • include: _spf.google.com
  • include: _spf.mx.cloudflare.net

Threat-feed evidence

History

Related pages

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