Hostname
de.nlx.org
Last fetched
de.nlx.org resolves to 18.64.174.127, announced in 18.64.168.0/21 by AMAZON-02 - Amazon.com, Inc. in US. de.nlx.org 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.64.174.127
18.64.168.0/21 · AMAZON-02 - Amazon.com, Inc. · Ashburn, US
- 18.64.174.55
18.64.168.0/21 · AMAZON-02 - Amazon.com, Inc. · Ashburn, US
- 18.64.174.61
18.64.168.0/21 · AMAZON-02 - Amazon.com, Inc. · Ashburn, US
- 18.64.174.83
18.64.168.0/21 · AMAZON-02 - Amazon.com, Inc. · Ashburn, US
- 3.166.81.38
3.166.80.0/21 · AMAZON-02 - Amazon.com, Inc. · Rome, IT
- 3.166.81.80
3.166.80.0/21 · AMAZON-02 - Amazon.com, Inc. · Rome, IT
- 3.166.81.84
3.166.80.0/21 · AMAZON-02 - Amazon.com, Inc. · Rome, IT
- 3.166.81.93
3.166.80.0/21 · AMAZON-02 - Amazon.com, Inc. · Rome, IT
IPv6 resolution
No AAAA record for de.nlx.org is recorded in WhisperGraph.
Attribution
Aws
cloud · ORIGIN_AS
WHOIS identity
WhisperGraph holds no WHOIS registrar, registrant organisation or contact email for de.nlx.org. 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.
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
- ns-49.awsdns-06.com
- ns-771.awsdns-32.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-1092.awsdns-08.org
- ns-1835.awsdns-37.co.uk
Threat-feed evidence
History
Related pages
Pivot from de.nlx.org 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: "de.nlx.org"})-[: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.