Skip to content

Hostname

personalbodyplan.com

Last fetched

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

Resolution chain

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

IPv6 resolution

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

WHOIS identity

Registrar
iana:468
Contact emails
pieter@personalbodyplan.com, 31c0c372-c415-44c1-8d54-22aa5da9142c@identity-protect.org, 34120588-0bdb-46e4-8d2e-ef944730ec46@identity-protect.org, dab7d354-abb4-4092-b80d-dd1d4c172e78@identity-protect.org, dde8b184-d9e7-46f3-8c5b-66f4430edc94@identity-protect.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-141.awsdns-17.com
  • ns-863.awsdns-43.net
  • ns-1519.awsdns-61.org
  • ns-1970.awsdns-54.co.uk

MX records

  • personalbodyplan-com.mail.protection.outlook.com

SPF policy

  • include: emsd1.com
  • include: spf.protection.outlook.com
  • include: spf.protection.personalbodyplan.com
  • include: mail.zendesk.com
  • include: sendgrid.net
  • include: spf.bhosted.nl
  • include: smtp.upcmail.nl

Threat-feed evidence

History

Related pages

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