Hostname
aooni-database.com
Last fetched
aooni-database.com resolves to 13.225.196.108, announced in 13.225.192.0/21 by AMAZON-02 - Amazon.com, Inc. in CA. aooni-database.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
- 13.225.196.108
13.225.192.0/21 · AMAZON-02 - Amazon.com, Inc. · Montreal, CA
- 13.225.196.125
13.225.192.0/21 · AMAZON-02 - Amazon.com, Inc. · Montreal, CA
- 13.225.196.19
13.225.192.0/21 · AMAZON-02 - Amazon.com, Inc. · Montreal, CA
- 13.225.196.52
13.225.192.0/21 · AMAZON-02 - Amazon.com, Inc. · Montreal, CA
- 18.66.102.105
18.66.102.0/24 · AMAZON-02 - Amazon.com, Inc. · Frankfurt am Main, DE
- 18.66.102.15
18.66.102.0/24 · AMAZON-02 - Amazon.com, Inc. · Frankfurt am Main, DE
- 18.66.102.39
18.66.102.0/24 · AMAZON-02 - Amazon.com, Inc. · Frankfurt am Main, DE
- 18.66.102.83
18.66.102.0/24 · AMAZON-02 - Amazon.com, Inc. · Frankfurt am Main, DE
- 3.175.207.24
3.175.207.0/24 · AMAZON-02 - Amazon.com, Inc. · Hong Kong, HK
- 3.175.207.32
3.175.207.0/24 · AMAZON-02 - Amazon.com, Inc. · Hong Kong, HK
- 3.175.207.63
3.175.207.0/24 · AMAZON-02 - Amazon.com, Inc. · Hong Kong, HK
- 3.175.207.95
3.175.207.0/24 · AMAZON-02 - Amazon.com, Inc. · Hong Kong, HK
IPv6 resolution
No AAAA record for aooni-database.com is recorded in WhisperGraph.
Attribution
Aws
cloud · ORIGIN_AS
WHOIS identity
- Registrar
- iana:49
- Registrant organisation
- whois privacy protection service by onamae.com
- Contact emails
- proxy@whoisprotectservice.com
Mail and authentication
Nameservers
- ns-210.awsdns-26.com
- ns-729.awsdns-27.net
- ns-1064.awsdns-05.org
- ns-1926.awsdns-48.co.uk
MX records
- aspmx.l.google.com
- alt1.aspmx.l.google.com
- alt2.aspmx.l.google.com
- aspmx2.googlemail.com
- aspmx3.googlemail.com
Threat-feed evidence
History
Related pages
Pivot from aooni-database.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: "aooni-database.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.