Skip to content

Hostname

christopherdurham.com

Last fetched

christopherdurham.com resolves to 209.196.146.115, announced in 209.196.146.0/24 by EPIK-LLC - Epik LLC in US. christopherdurham.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 · christopherdurham.comRouting diversity1.5/10Peering density1.2/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency10.0/10Resolver footprint3.2/10canon.whisper.security/host/christopherdurham.com

Resolution chain

IPv6 resolution

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

Attribution

epik

ORIGIN_AS

WHOIS identity

Registrar
iana:617
Registrant organisation
anonymize, llc.
Contact emails
administrator@cdcservices.ca, christopherdurham.com-1hrrkubncjak4@anonymize.com, christopherdurham.com-1huzxi54vskf9@anonymize.com, christopherdurham.com-1iycoxr79fvxg@anonymize.com, christopherdurham.com-qe3u5vwtvazn@anonymize.com, christopherdurham.com-qxfj4za2iqet@anonymize.com, christopherdurham.com-qxqji2j7ebtt@anonymize.com, christopherdurham.com-sl1507nxn41e@anonymize.com, christopherdurham.com-sl15pjk72gc6@anonymize.com, christopherdurham.com-sl3dm4dc7tpx@anonymize.com, christopherdurham.com-sl6o37utvyhv@anonymize.com, christopherdurham.com-t843de05v2nq@anonymize.com, christopherdurham.com-t8a636pxiyxw@anonymize.com, christopherdurham.com-to4kvd29t278@anonymize.com, christopherdurham.com-vf0v412y0y0m@anonymize.com, christopherdurham.com-vf99kblixc2r@anonymize.com, pw-5d8f269b48011322c7acb5fb50324204@privacyguardian.org

Subdomains

Showing 1 of 1 subdomain (1 per page).

Mail and authentication

Nameservers

  • ns3.epik.com
  • ns4.epik.com

Threat-feed evidence

History

Related pages

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