Skip to content

Hostname

jair.org

Last fetched

jair.org resolves to 204.187.13.158, announced in 204.187.12.0/22 by GOSSAMERTHREADS - Gossamer Threads Inc. in CA. jair.org 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 · jair.orgRouting diversity1.5/10Peering density2.8/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency10.0/10Resolver footprint8.0/10canon.whisper.security/host/jair.org

Resolution chain

IPv6 resolution

No AAAA record for jair.org is recorded in WhisperGraph.

Attribution

gossamer threads

ORIGIN_AS

WHOIS identity

Registrar
iana:2
Contact emails
b32f49b84g8@networksolutionsprivateregistration.com, g33m67456jm@networksolutionsprivateregistration.com, gt8xb9fq2rb@networksolutionsprivateregistration.com, k53s54vz4ak@networksolutionsprivateregistration.com, rq5sz4xd84u@networksolutionsprivateregistration.com, sf7wc6j246t@networksolutionsprivateregistration.com, xm2f53va28m@networksolutionsprivateregistration.com

Subdomains

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.

Mail and authentication

Nameservers

  • ns29.worldnic.com
  • ns30.worldnic.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

  • 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

  • a: jair.org
  • mx: jair.org
  • ip: 204.187.13.158

Threat-feed evidence

History

Related pages

Pivot from jair.org 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: "jair.org"})-[: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.