Hostname
dnb.no
Last fetched
dnb.no resolves to 20 IPv4 addresses operated by AKAMAI-ASN1 in DE.
Nutrition Label
Resolution chain
dnb.no resolves to 20 distinct IPv4 addresses via WhisperGraph DNS data. Each row links to the IP, prefix, and announcing ASN.
| IP | Prefix | ASN | Operator | Country |
|---|---|---|---|---|
| 2.17.100.218 | 2.17.100.0/24 | AS20940 | AKAMAI-ASN1 | DE |
| 2.17.100.219 | 2.17.100.0/24 | AS20940 | AKAMAI-ASN1 | DE |
| 2.17.100.232 | 2.17.100.0/24 | AS20940 | AKAMAI-ASN1 | DE |
| 2.17.100.234 | 2.17.100.0/24 | AS20940 | AKAMAI-ASN1 | DE |
| 2.17.100.240 | 2.17.100.0/24 | AS20940 | AKAMAI-ASN1 | DE |
| 2.17.100.241 | 2.17.100.0/24 | AS20940 | AKAMAI-ASN1 | DE |
| 2.17.100.243 | 2.17.100.0/24 | AS20940 | AKAMAI-ASN1 | DE |
| 2.17.100.250 | 2.17.100.0/24 | AS20940 | AKAMAI-ASN1 | DE |
| 2.17.147.176 | 2.17.147.0/24 | AS20940 | AKAMAI-ASN1 | CZ |
| 2.17.147.200 | 2.17.147.0/24 | AS20940 | AKAMAI-ASN1 | CZ |
| 2.17.162.11 | 2.17.162.0/24 | AS20940 | AKAMAI-ASN1 | BR |
| 2.17.162.12 | 2.17.162.0/24 | AS20940 | AKAMAI-ASN1 | BR |
| 2.17.162.13 | 2.17.162.0/24 | AS20940 | AKAMAI-ASN1 | BR |
| 2.17.162.17 | 2.17.162.0/24 | AS20940 | AKAMAI-ASN1 | BR |
| 2.17.162.18 | 2.17.162.0/24 | AS20940 | AKAMAI-ASN1 | BR |
| 2.17.162.19 | 2.17.162.0/24 | AS20940 | AKAMAI-ASN1 | BR |
| 2.17.162.3 | 2.17.162.0/24 | AS20940 | AKAMAI-ASN1 | BR |
| 2.17.162.9 | 2.17.162.0/24 | AS20940 | AKAMAI-ASN1 | BR |
| 23.33.42.68 | 23.33.42.0/24 | AS20940 | AKAMAI-ASN1 | US |
| 23.33.42.69 | 23.33.42.0/24 | AS20940 | AKAMAI-ASN1 | US |
WHOIS identity
WHOIS data is temporarily unavailable. Refresh in a moment to retry.
Subdomains
Subdomain count is temporarily unavailable. Refresh in a moment to retry.
Web-graph footprint
Distinct hostnames that link to or from dnb.no in the public web crawl.
Sample inbound links
Threat posture
History
Mail and authentication
SPF policy
1 SPF mechanism authorising senders for dnb.no.
| Mechanism | Target |
|---|---|
| SPF_INCLUDE | %{ir}.%{v}.%{d}.spf.has.pphosted.com |
Related pages
Pivot deeper into the graph from dnb.no.
Cypher and MCP
Reproduce the resolution chain directly against graph.whisper.security:
MATCH (h:HOSTNAME {name: "dnb.no"})-[:RESOLVES_TO]->(ip:IPV4)
-[:ANNOUNCED_BY]->(ap:ANNOUNCED_PREFIX)
-[:ROUTES]->(asn:ASN)-[:HAS_NAME]->(n:ASN_NAME)
RETURN ip.name AS ip, ap.name AS prefix, asn.name AS asn, n.name AS operator
LIMIT 20Or query Whisper from your own LLM workflow via the Whisper MCP server.