Skip to content

Hostname

gtri.org

Last fetched

gtri.org resolves to 130.207.193.236, announced in 130.207.0.0/16 by GEORGIA-TECH - Georgia Institute of Technology in US. gtri.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 · gtri.orgRouting diversity1.5/10Peering density2.4/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency10.0/10Resolver footprint8.3/10canon.whisper.security/host/gtri.org

Resolution chain

IPv6 resolution

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

Attribution

georgia institute of

ORIGIN_AS

WHOIS identity

Registrar
iana:1068
Registrant organisation
georgia tech research institute
Contact emails
scott.harlan@gtri.gatech.edu

Subdomains

Subdomain
2010mail.gtri.org
apiary.gtri.org
barracuda5-1.gtri.org
barracuda5-2.gtri.org
c2core.gtri.org
core.gtri.org
ctisl.gtri.org
directory.gtri.org
elsys.gtri.org
eosl.gtri.org
esdhost1.gtri.org
extmail1.gtri.org

Showing 12 of 160. View all subdomains →

Mail and authentication

Nameservers

  • brahma5.dns.gatech.edu
  • dns1.gatech.edu
  • dns2.gatech.edu
  • dns3.gatech.edu
  • 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

  • gtrigov.mail.protection.office365.us

SPF policy

  • ip: 130.207.205.170/32
  • mx: gtri.org
  • include: spf.protection.office365.us

Threat-feed evidence

History

Related pages

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