Hostname
nordicdataresources.net
Last fetched
nordicdataresources.net is a hostname indexed by WhisperGraph, the internet-infrastructure graph behind the Whisper Internet Directory. nordicdataresources.net 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
No IPv4 resolution is recorded for nordicdataresources.net in WhisperGraph.
IPv6 resolution
No AAAA record for nordicdataresources.net is recorded in WhisperGraph.
WHOIS identity
- Registrar
- iana:269
- Registrant organisation
- c/o whoisproxy.com
- Contact emails
- 02bd14627a977cda69b402d9c89b9143a9486611621e55248b8573956bd03ad0@nordicdataresources.net.whoisproxy.org, 0327c9cb56736f7731173ef86c892ab59a44d207d2234f0f82624af5422aebf2@nordicdataresources.net.whoisproxy.org, 04816685019f0f1adb05eb3a190a78a8ae5b332025808654772f372bf168cd16@nordicdataresources.net.whoisproxy.org, 0fd7b49030f588b5061c9cc8446ba8202dcc266a33ebbc08ed5ac54d7c1aa087@nordicdataresources.net.whoisproxy.org, 50be06d44b0143e17397f7d6d894ce5201e6077e2b41f2bca4e7099da61548c0@nordicdataresources.net.whoisproxy.org, 716efe6dc6b495c22b20e8f3dbdac29dc8a69a08347f4d54d61b6100c017fb4a@nordicdataresources.net.whoisproxy.org, a4938063c14dfe2dd633464bc1536e2b2d3c0352c5d68770457bccf313c92157@nordicdataresources.net.whoisproxy.org, c53c8223d5d5e5eb618356970c3c71695eca53c952608fbbe744c795edd51a87@nordicdataresources.net.whoisproxy.org, d59c0835e65ec50d95a0efb4164d329976ff15e9e212bd520f151f088eb5f47c@nordicdataresources.net.whoisproxy.org, f1f75ed3ea3928cab1e184d88910a450cd111328962cf0ca23870e8044b57895@nordicdataresources.net.whoisproxy.org
Subdomains
Showing 2 of 2 subdomains (2 per page).
Mail and authentication
Nameservers
- dns106.ovh.net
- ns106.ovh.net
- dns.home.pl
- dns2.home.pl
- dns3.home.pl
Threat-feed evidence
History
Related pages
Pivot from nordicdataresources.net 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: "nordicdataresources.net"})-[: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.