Skip to content

Hostname

killerfrogs.com

Last fetched

killerfrogs.com resolves to 104.21.20.130, announced in 104.21.16.0/20 by CLOUDFLARENET - Cloudflare, Inc. in CA. killerfrogs.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 · killerfrogs.comRouting diversity1.5/10Peering density10.0/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency10.0/10Resolver footprint3.2/10canon.whisper.security/host/killerfrogs.com

Resolution chain

IPv6 resolution

Attribution

Cloudflare

cdn · ORIGIN_AS, CDN

WHOIS identity

Registrar
iana:2
Contact emails
cf7k66rz764@networksolutionsprivateregistration.com, dy3kx7wj49p@networksolutionsprivateregistration.com, gp25r8v93dz@networksolutionsprivateregistration.com, h28zm89t5za@networksolutionsprivateregistration.com, he9xt5fc9s6@networksolutionsprivateregistration.com, jc3mf9bf32h@networksolutionsprivateregistration.com, nt4vz9br72c@networksolutionsprivateregistration.com, nx97954j3qq@networksolutionsprivateregistration.com, ve7w69pv5me@networksolutionsprivateregistration.com, vh6gr8p74st@networksolutionsprivateregistration.com, yn4vq3h643n@networksolutionsprivateregistration.com, zx7e69ut8m9@networksolutionsprivateregistration.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

Nameservers

  • jessica.ns.cloudflare.com
  • neil.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

SPF policy

  • include: _spf.google.com
  • a: killerfrogs.com
  • mx: killerfrogs.com
  • include: mailgun.org
  • ip: 162.254.117.67

Threat-feed evidence

History

Related pages

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