Hostname
auth.relaygo.com
Last fetched
auth.relaygo.com resolves to 18.225.116.132, announced in 18.224.0.0/14 by AMAZON-02 - Amazon.com, Inc. in US. auth.relaygo.com 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
- 18.225.116.132
18.224.0.0/14 · AMAZON-02 - Amazon.com, Inc. · Columbus, US
- 18.225.132.151
18.224.0.0/14 · AMAZON-02 - Amazon.com, Inc. · Columbus, US
- 3.131.45.119
3.131.0.0/16 · AMAZON-02 - Amazon.com, Inc. · Dublin, US
- 3.136.99.23
3.136.0.0/13 · AMAZON-02 - Amazon.com, Inc. · Dublin, US
- 3.146.249.206
3.144.0.0/13 · AMAZON-02 - Amazon.com, Inc. · Columbus, US
- 3.150.54.167
3.144.0.0/13 · AMAZON-02 - Amazon.com, Inc. · Columbus, US
- 3.22.207.202
3.20.0.0/14 · AMAZON-02 - Amazon.com, Inc. · Columbus, US
- 52.15.189.192
52.15.128.0/17 · AMAZON-02 - Amazon.com, Inc. · Columbus, US
- 16.58.93.77
16.58.0.0/17 · AMAZON-02 - Amazon.com, Inc. · Columbus, US
IPv6 resolution
No AAAA record for auth.relaygo.com is recorded in WhisperGraph.
Attribution
Aws
cloud · ORIGIN_AS
WHOIS identity
WhisperGraph holds no WHOIS registrar, registrant organisation or contact email for auth.relaygo.com. WHOIS is recorded against the registrable domain, so a subdomain such as a www. host carries none of its own — check the registrable domain for this name.
Mail and authentication
Nameservers
- ns-127.awsdns-15.com
- ns-598.awsdns-10.net
- 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
- ns-1076.awsdns-06.org
- ns-1722.awsdns-23.co.uk
Threat-feed evidence
History
Related pages
Pivot from auth.relaygo.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: "auth.relaygo.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 20Or query Whisper from your own LLM workflow via the Whisper MCP server.