Skip to content

Hostname

peterjacksons.com

Last fetched

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

Resolution chain

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

IPv6 resolution

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

WHOIS identity

Registrar
iana:468
Registrant organisation
on behalf of peterjacksons.com owner
Contact emails
nick@peterjacksons.com, 249dc1ed-67d7-4c19-9f5e-2fd71c264a3a@identity-protect.org, cac68a14-a140-40a7-a230-5285b67757de@identity-protect.org, d9a68a91-19a9-40f3-9945-bca35e44e521@identity-protect.org

Subdomains

Subdomain
account.peterjacksons.com
cfjump.peterjacksons.com
www.peterjacksons.com

Showing 3 of 3 subdomains (3 per page).

Web-graph footprint

Sampled `LINKS_TO` edges. The hyperlink layer is a pilot sample, not a web-scale crawl, so these are illustrative.

Sample inbound links

Sample outbound links

Mail and authentication

Nameservers

  • ns-283.awsdns-35.com
  • ns-901.awsdns-48.net
  • ns-1413.awsdns-48.org
  • ns-2012.awsdns-59.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
  • include: shops.shopify.com
  • ip: 101.187.14.201
  • ip: 13.55.103.189
  • ip: 180.214.74.181
  • ip: 180.214.74.183
  • ip: 60.231.165.110

Threat-feed evidence

History

Related pages

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