Skip to content

Hostname

jacketsjunction.com

Last fetched

jacketsjunction.com resolves to 104.26.12.157, announced in 104.26.0.0/20 by CLOUDFLARENET - Cloudflare, Inc. in CA. jacketsjunction.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 · jacketsjunction.comRouting diversity1.5/10Peering density10.0/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency10.0/10Resolver footprint3.2/10canon.whisper.security/host/jacketsjunction.com

Resolution chain

IPv6 resolution

Attribution

Cloudflare

cdn · ORIGIN_AS, CDN

WHOIS identity

Registrar
iana:1068
Registrant organisation
farhan sunka
Contact emails
fsunka1992@gmail.com, 07dba344189348ca82acba52abcc856e.protect@withheldforprivacy.com, 3fadee6dc3ff4265830ae12eebc98273.protect@withheldforprivacy.com, a130d542b1e44fa18674eb9d44b70d69.protect@withheldforprivacy.com, synergyoutfit@gmail.com

Subdomains

Subdomain
88195598713c.jacketsjunction.com
cpanel.jacketsjunction.com
cpcalendars.jacketsjunction.com
cpcontacts.jacketsjunction.com
f8523c677b55.jacketsjunction.com
mail.jacketsjunction.com
ns1.jacketsjunction.com
ns2.jacketsjunction.com
webdisk.jacketsjunction.com
webmail.jacketsjunction.com
whm.jacketsjunction.com
www.jacketsjunction.com

Showing 12 of 14. 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

Mail and authentication

Nameservers

  • jerry.ns.cloudflare.com
  • ligia.ns.cloudflare.com

MX records

  • mail.jacketsjunction.com

SPF policy

  • a: jacketsjunction.com
  • mx: jacketsjunction.com
  • include: sendersrv.com
  • include: relay.mailchannels.net
  • ip: 104.247.72.250
  • ip: 5.161.214.209

Threat-feed evidence

History

Related pages

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