Skip to content

Hostname

juit.com

Last fetched

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

Resolution chain

IPv6 resolution

Attribution

Cloudflare

cdn · ORIGIN_AS, CDN

WHOIS identity

Registrar
iana:468
Registrant organisation
on behalf of juit.com owner
Contact emails
admin@dexner.com, damin7@kornet.net, 11a3e00d-7958-4344-840e-3025c6f018fd@identity-protect.org, 19030a27-b8fb-4282-8c8a-44e5e6782bd6@identity-protect.org, 58d8e620-5234-405c-a504-84eda5d1be76@identity-protect.org, 6acfce64-f72c-4b8e-b35d-378e27bb588b@identity-protect.org, a1483e98-97f4-4db6-885a-e1fbce23fb9a@identity-protect.org, d5a313b7-748d-476e-a6c1-8e0a68d0b8c2@identity-protect.org, e29115a6-86d7-4078-b0b8-a706728b90a0@identity-protect.org, owner-5584607@juit.com.whoisprivacyservice.org, owner-5657174@juit.com.whoisprivacyservice.org, owner-644840@juit.com.whoisprivacyservice.org

Subdomains

Web-graph footprint

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

Mail and authentication

Nameservers

  • ben.ns.cloudflare.com
  • desi.ns.cloudflare.com

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: calendar-server.bounces.google.com
  • include: spf.dixa.io
  • include: 145866053.spf04.hubspotemail.net

Threat-feed evidence

History

Related pages

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