Skip to content

Hostname

jetoffwithjess.com

Last fetched

jetoffwithjess.com resolves to 80.82.125.229, announced in 80.82.112.0/20 by UK-34SP-AS - 34SP.com Limited in GB. jetoffwithjess.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 · jetoffwithjess.comRouting diversity1.5/10Peering density2.8/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency10.0/10Resolver footprint8.0/10canon.whisper.security/host/jetoffwithjess.com

Resolution chain

IPv6 resolution

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

Attribution

34sp com

ORIGIN_AS

WHOIS identity

Registrar
iana:1068
Registrant organisation
jess downard
Contact emails
jessdownard@icloud.com, bb3faa8c7fa0464e8bf112ed24be54b5.protect@whoisguard.com, 2e1e8342e00e405299615a3981802889.protect@withheldforprivacy.com

Subdomains

Subdomain
0bc34b54b96a.jetoffwithjess.com
mail.jetoffwithjess.com
www.jetoffwithjess.com

Showing 3 of 6. View all subdomains →

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

  • carter.ns.cloudflare.com
  • rosemary.ns.cloudflare.com
  • 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

MX records

  • _dc-mx.0bc34b54b96a.jetoffwithjess.com

SPF policy

  • a: jetoffwithjess.com
  • mx: jetoffwithjess.com
  • include: spf.web-hosting.com
  • ip: 198.54.114.27
  • ip: 198.54.116.27

Threat-feed evidence

History

Related pages

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