Skip to content

Hostname

sailorjerry.com

Last fetched

sailorjerry.com resolves to 64.239.109.1, announced in 64.239.109.0/24 by AMAZON-02 - Amazon.com, Inc. in US. sailorjerry.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 · sailorjerry.comRouting diversity1.5/10Peering density9.7/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency10.0/10Resolver footprint6.0/10canon.whisper.security/host/sailorjerry.com

Resolution chain

IPv6 resolution

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

Attribution

amazon com

ORIGIN_AS

WHOIS identity

Registrar
iana:470
Registrant organisation
domain admin
Contact emails
cctld@demys.com, sailorjerry.com+registrant@customer.demys.com, gtld@demys.com, sailorjerry.com-registrant@anonymised.email

Subdomains

Subdomain
connected.sailorjerry.com
outsidethelines.sailorjerry.com
winwith.sailorjerry.com
www.sailorjerry.com

Showing 4 of 4 subdomains (4 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

  • ns0.demysdns.net
  • ns1.demysdns.net
  • ns2.demysdns.net
  • ns3.demysdns.net
  • ns4.demysdns.co.uk
  • ns5.demysdns.co.uk
  • ns6.demysdns.co.uk

MX records

  • cust3131-1.in.mailcontrol.com
  • cust3131-2.in.mailcontrol.com
  • cust3131-3.in.mailcontrol.com
  • cust3131-4.in.mailcontrol.com
  • sailorjerry-com.mail.protection.outlook.com

SPF policy

  • include: mailcontrol.com
  • include: spf.protection.outlook.com

Threat-feed evidence

History

Related pages

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