Skip to content

Hostname

guernseyms.com

Last fetched

guernseyms.com resolves to 83.223.113.211, announced in 83.223.96.0/19 by GYRON - NTT Global Data Centers EMEA UK Ltd. in GB. guernseyms.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 · guernseyms.comRouting diversity1.5/10Peering density4.7/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency10.0/10Resolver footprint8.3/10canon.whisper.security/host/guernseyms.com

Resolution chain

Attribution

ntt global centers emea uk

ORIGIN_AS

WHOIS identity

Registrar
iana:468
Registrant organisation
on behalf of guernseyms.com owner
Contact emails
robplatts@guernsey.net, 24ae130f-e8a9-4d18-9c5e-53069ae9adb1@identity-protect.org, 6d4bcea9-fa63-4146-a1fb-eff55975f105@identity-protect.org, 8bdea114-454a-4410-82e2-fb69773b2815@identity-protect.org, ff7f0086-8d95-4f7e-a4e3-74a71ebb39d2@identity-protect.org

Subdomains

Subdomain
www.guernseyms.com

Showing 1 of 1 subdomain (1 per page).

Mail and authentication

Nameservers

  • ns-263.awsdns-32.com
  • ns-757.awsdns-30.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-1357.awsdns-41.org
  • ns-1824.awsdns-36.co.uk

MX records

  • aspmx.l.google.com
  • alt1.aspmx.l.google.com
  • alt2.aspmx.l.google.com
  • aspmx2.googlemail.com
  • aspmx3.googlemail.com

SPF policy

  • mx: guernseyms.com
  • include: spf.pjwd.net

Threat-feed evidence

History

Related pages

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