Hostname
norednk.com
Last fetched
norednk.com resolves to 5.79.79.209, announced in 5.79.64.0/18 by LEASEWEB-NL-AMS-01 - LeaseWeb Netherlands B.V. in NL. norednk.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
- 5.79.79.209
5.79.64.0/18 · LEASEWEB-NL-AMS-01 - LeaseWeb Netherlands B.V. · Amsterdam, NL
- 213.227.156.74
213.227.128.0/19 · LEASEWEB-NL-AMS-01 - LeaseWeb Netherlands B.V. · Amsterdam, NL
- 64.31.3.229
64.31.3.0/24 · LIMESTONENETWORKS - Limestone Networks, Inc. · Salt Lake City, US
- 64.31.3.226
64.31.3.0/24 · LIMESTONENETWORKS - Limestone Networks, Inc. · Salt Lake City, US
- 37.48.110.47
37.48.64.0/18 · LEASEWEB-NL-AMS-01 - LeaseWeb Netherlands B.V. · Amsterdam, NL
- 37.48.110.48
37.48.64.0/18 · LEASEWEB-NL-AMS-01 - LeaseWeb Netherlands B.V. · Amsterdam, NL
- 213.227.156.75
213.227.128.0/19 · LEASEWEB-NL-AMS-01 - LeaseWeb Netherlands B.V. · Amsterdam, NL
IPv6 resolution
No AAAA record for norednk.com is recorded in WhisperGraph.
Attribution
leaseweb netherlands
ORIGIN_AS
WHOIS identity
- Registrar
- iana:1114
- Registrant organisation
- whois protection, this company does not own this domain name s.r.o.
- Contact emails
- yuming@yinsibaohu.aliyun.com, norednk.com@domainsbyproxy.com, domains@fundacionprivacy.com, privacyprotect@hebeidomains.com, contact@privacyprotect.org
Subdomains
Showing 3 of 3 subdomains (3 per page).
Mail and authentication
Nameservers
- ns1.dingodns.com
- ns2.dingodns.com
- ns1.tacomadc.com
- ns2.tacomadc.com
- ns1.wombatdns.com
- 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
Threat-feed evidence
History
Related pages
Pivot from norednk.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: "norednk.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.