Skip to content

Hostname

havenpower.com

Last fetched

havenpower.com is a hostname indexed by WhisperGraph, the internet-infrastructure graph behind the Whisper Internet Directory. havenpower.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 · havenpower.comRouting diversity0.0/10Peering density0.0/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency10.0/10Resolver footprint4.6/10canon.whisper.security/host/havenpower.com

Resolution chain

No IPv4 resolution is recorded for havenpower.com in WhisperGraph.

IPv6 resolution

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

WHOIS identity

Registrar
iana:468
Registrant organisation
andrew webster
Contact emails
einstein.ece@gmail.com, webmaster@havenpower.com, 3fd811bf-74d9-4f4a-a023-942eb1923aee@identity-protect.org, 5fc44825-726a-4346-960c-9ee2ae5a3c00@identity-protect.org, a8ef5d19-0391-48f6-926f-d96264f3b342@identity-protect.org, d54608b5-c772-493b-9b21-bb66aaf5caac@identity-protect.org, db9a3cbe-c83d-470f-a163-718438339c4e@identity-protect.org, fb55de92-1aed-4d47-9882-d56adbde2ee8@identity-protect.org, owner-6614465@havenpower.com.whoisprivacyservice.org, owner-6811847@havenpower.com.whoisprivacyservice.org

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

  • ns-367.awsdns-45.com
  • ns-682.awsdns-21.net
  • ns-1173.awsdns-18.org
  • ns-1667.awsdns-16.co.uk

MX records

  • havenpower-com.mail.protection.outlook.com

SPF policy

  • ip: 205.201.128.0/20
  • ip: 188.127.91.24/29
  • include: spf1.havenpower.com
  • include: spf.protection.outlook.com
  • ip: 195.72.71.145
  • ip: 40.85.92.201
  • ip: 84.19.61.215

Threat-feed evidence

History

Related pages

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