Hostname
gator.io
Last fetched
gator.io resolves to 100.20.112.59, announced in 100.20.0.0/14 by AMAZON-02 - Amazon.com, Inc. in US. gator.io is not listed on any threat feed indexed by WhisperGraph; reconciled level NONE.
Threat posture
0threat score (procedure-native scale)
NONENo threats observed.
- Threat feeds listing this
- 0
- Verdict coverage
- known-clean
Nutrition Label
Resolution chain
- 100.20.112.59
100.20.0.0/14 · AMAZON-02 - Amazon.com, Inc. · Boardman, US
- 16.145.111.229
16.145.0.0/16 · AMAZON-02 - Amazon.com, Inc. · Portland, US
- 34.210.251.81
34.208.0.0/12 · AMAZON-02 - Amazon.com, Inc. · Boardman, US
- 34.218.26.150
34.208.0.0/12 · AMAZON-02 - Amazon.com, Inc. · Boardman, US
- 35.85.205.150
35.80.0.0/12 · AMAZON-02 - Amazon.com, Inc. · Boardman, US
- 44.229.133.124
44.224.0.0/11 · AMAZON-02 - Amazon.com, Inc. · Boardman, US
- 44.230.8.95
44.224.0.0/11 · AMAZON-02 - Amazon.com, Inc. · Boardman, US
- 44.232.235.217
44.224.0.0/11 · AMAZON-02 - Amazon.com, Inc. · Boardman, US
- 44.250.16.164
44.224.0.0/11 · AMAZON-02 - Amazon.com, Inc. · Boardman, US
- 52.24.137.233
52.24.0.0/14 · AMAZON-02 - Amazon.com, Inc. · Boardman, US
- 52.38.244.141
52.36.0.0/14 · AMAZON-02 - Amazon.com, Inc. · Boardman, US
- 54.189.5.14
54.188.0.0/15 · AMAZON-02 - Amazon.com, Inc. · Boardman, US
- 54.68.131.78
54.68.0.0/15 · AMAZON-02 - Amazon.com, Inc. · Boardman, US
- 54.185.109.230
54.184.0.0/15 · AMAZON-02 - Amazon.com, Inc. · Boardman, US
- 32.187.72.232
- 16.148.225.58
IPv6 resolution
No AAAA record for gator.io is recorded in WhisperGraph.
Attribution
Aws
cloud · ORIGIN_AS
WHOIS identity
- Registrar
- iana:48
- Registrant organisation
- owner orgname netapplications.com
Subdomains
Mail and authentication
Nameservers
- ns-235.awsdns-29.com
- ns-625.awsdns-14.net
- ns-1356.awsdns-41.org
- ns-1955.awsdns-52.co.uk
MX records
- gator-io.mail.protection.outlook.com
SPF policy
- include: amazonses.com
- include: spf.protection.outlook.com
Threat-feed evidence
History
Related pages
Pivot from gator.io 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: "gator.io"})-[: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 20Or query Whisper from your own LLM workflow via the Whisper MCP server.