Hostname
nohu90.com
Last fetched
nohu90.com resolves to 13.248.207.111, announced in 13.248.192.0/20 by AMAZON-02 - Amazon.com, Inc. in CA. nohu90.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.248.207.111
13.248.192.0/20 · AMAZON-02 - Amazon.com, Inc. · Montreal, CA
- 166.117.127.109
166.117.112.0/20 · AMAZON-02 - Amazon.com, Inc. · Seattle, US
- 166.117.142.117
166.117.128.0/20 · AMAZON-02 - Amazon.com, Inc. · Seattle, US
- 35.71.157.115
- 75.2.25.109
75.2.16.0/20 · AMAZON-02 - Amazon.com, Inc. · Seattle, US
- 75.2.104.78
75.2.96.0/20 · AMAZON-02 - Amazon.com, Inc. · Seattle, US
- 35.71.177.108
35.71.176.0/20 · AMAZON-02 - Amazon.com, Inc. · Montreal, CA
- 166.117.213.75
166.117.208.0/20 · AMAZON-02 - Amazon.com, Inc. · Seattle, US
- 166.117.125.119
166.117.112.0/20 · AMAZON-02 - Amazon.com, Inc. · Seattle, US
- 35.71.130.112
35.71.128.0/20 · AMAZON-02 - Amazon.com, Inc. · Montreal, CA
- 13.248.139.127
13.248.128.0/20 · AMAZON-02 - Amazon.com, Inc. · Montreal, CA
- 3.33.229.85
3.33.224.0/20 · AMAZON-02 - Amazon.com, Inc. · Montreal, CA
- 3.33.222.92
3.33.208.0/20 · AMAZON-02 - Amazon.com, Inc. · Montreal, CA
- 166.117.44.71
166.117.32.0/20 · AMAZON-02 - Amazon.com, Inc. · Seattle, US
IPv6 resolution
No AAAA record for nohu90.com is recorded in WhisperGraph.
Attribution
Aws
cloud · ORIGIN_AS
WHOIS identity
- Registrar
- iana:146
- Registrant organisation
- domains by proxy,
Subdomains
Showing 5 of 9. View all subdomains →
Web-graph footprint
Sampled `LINKS_TO` edges. The hyperlink layer is a pilot sample, not a web-scale crawl, so these are illustrative.
Mail and authentication
Nameservers
- amy.ns.cloudflare.com
- carmelo.ns.cloudflare.com
Threat-feed evidence
History
Related pages
Pivot from nohu90.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: "nohu90.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.