Skip to content

Hostname

fankeeper.com

Last fetched

fankeeper.com resolves to 100.29.235.229, announced in 100.24.0.0/13 by AMAZON-AES - Amazon.com, Inc. in US. fankeeper.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 · fankeeper.comRouting diversity1.5/10Peering density7.1/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency10.0/10Resolver footprint8.3/10canon.whisper.security/host/fankeeper.com

Resolution chain

IPv6 resolution

No AAAA record for fankeeper.com is recorded in WhisperGraph.

Attribution

Aws

cloud · ORIGIN_AS

WHOIS identity

Registrar
iana:468
Registrant organisation
on behalf of fankeeper.com owner
Contact emails
patrice@zepto.ca, a1498d6c-c4ef-414c-ba0e-e1cf6ef97ba6@identity-protect.org, cf0fbc6a-1e76-4ec1-b448-01e9ab15906b@identity-protect.org, f7761e7a-74a1-4477-8645-0da353ab0cf8@identity-protect.org

Subdomains

Subdomain
mail.fankeeper.com
wildcard.fankeeper.com
www.fankeeper.com

Showing 3 of 3 subdomains (3 per page).

Mail and authentication

Nameservers

  • ns-102.awsdns-12.com
  • ns-858.awsdns-43.net
  • 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
  • ns-1128.awsdns-13.org
  • ns-2043.awsdns-63.co.uk

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: amazonses.com
  • include: _spf.google.com

Threat-feed evidence

History

Related pages

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