Hostname
testnet.bitagent.io
Last fetched
testnet.bitagent.io resolves to 18.165.72.3, announced in 18.165.72.0/23 by AMAZON-02 - Amazon.com, Inc. in BG. testnet.bitagent.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
- 18.165.72.3
18.165.72.0/23 · AMAZON-02 - Amazon.com, Inc. · Sofia, BG
- 18.165.72.42
18.165.72.0/23 · AMAZON-02 - Amazon.com, Inc. · Sofia, BG
- 18.165.72.76
18.165.72.0/23 · AMAZON-02 - Amazon.com, Inc. · Sofia, BG
- 18.165.72.97
18.165.72.0/23 · AMAZON-02 - Amazon.com, Inc. · Sofia, BG
- 99.84.203.112
99.84.200.0/21 · AMAZON-02 - Amazon.com, Inc. · Minneapolis, US
- 99.84.203.122
99.84.200.0/21 · AMAZON-02 - Amazon.com, Inc. · Minneapolis, US
- 99.84.203.31
99.84.200.0/21 · AMAZON-02 - Amazon.com, Inc. · Minneapolis, US
- 99.84.203.68
99.84.200.0/21 · AMAZON-02 - Amazon.com, Inc. · Minneapolis, US
IPv6 resolution
No AAAA record for testnet.bitagent.io is recorded in WhisperGraph.
Attribution
Aws
cloud · ORIGIN_AS
WHOIS identity
WhisperGraph holds no WHOIS registrar, registrant organisation or contact email for testnet.bitagent.io. 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-295.awsdns-36.com
- ns-721.awsdns-26.net
- ns-1358.awsdns-41.org
- ns-1821.awsdns-35.co.uk
Threat-feed evidence
History
Related pages
Pivot from testnet.bitagent.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: "testnet.bitagent.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.