Hostname
p3.no
Last fetched
p3.no resolves to 16 IPv4 addresses operated by AKAMAI-ASN1 in DE.
Nutrition Label
Resolution chain
p3.no resolves to 16 distinct IPv4 addresses via WhisperGraph DNS data. Each row links to the IP, prefix, and announcing ASN.
| IP | Prefix | ASN | Operator | Country |
|---|---|---|---|---|
| 184.24.77.27 | 184.24.77.0/24 | AS20940 | AKAMAI-ASN1 | DE |
| 184.24.77.31 | 184.24.77.0/24 | AS20940 | AKAMAI-ASN1 | DE |
| 2.16.10.141 | 2.16.10.0/24 | AS20940 | AKAMAI-ASN1 | DE |
| 2.16.10.155 | 2.16.10.0/24 | AS20940 | AKAMAI-ASN1 | DE |
| 2.16.154.115 | 2.16.154.0/24 | AS20940 | AKAMAI-ASN1 | RU |
| 2.16.154.146 | 2.16.154.0/24 | AS20940 | AKAMAI-ASN1 | RU |
| 2.16.2.40 | 2.16.2.0/24 | AS20940 | AKAMAI-ASN1 | CZ |
| 2.16.2.64 | 2.16.2.0/24 | AS20940 | AKAMAI-ASN1 | CZ |
| 23.219.36.107 | 23.219.36.0/24 | AS20940 | AKAMAI-ASN1 | US |
| 23.219.36.111 | 23.219.36.0/24 | AS20940 | AKAMAI-ASN1 | US |
| 23.32.239.51 | 23.32.238.0/23 | AS20940 | AKAMAI-ASN1 | DE |
| 23.32.239.8 | 23.32.238.0/23 | AS20940 | AKAMAI-ASN1 | DE |
| 23.53.40.25 | 23.53.40.0/22 | AS20940 | AKAMAI-ASN1 | DE |
| 23.53.40.49 | 23.53.40.0/22 | AS20940 | AKAMAI-ASN1 | DE |
| 95.100.146.97 | 95.100.146.0/24 | AS20940 | AKAMAI-ASN1 | CZ |
| 95.100.146.99 | 95.100.146.0/24 | AS20940 | AKAMAI-ASN1 | CZ |
WHOIS identity
- Registrar
- —
- Organization
- norsk rikskringkasting as
- Contact emails
Subdomains
11 observed subdomains of p3.no.
Web-graph footprint
Distinct hostnames that link to or from p3.no in the public web crawl.
939 sites link to this hostname.
Sample inbound links
Threat posture
History
Mail and authentication
Related pages
Pivot deeper into the graph from p3.no.
- IP · 184.24.77.27
- ASN · AS20940AKAMAI-ASN1
- Country · DE
- Email · j8h4qdjcqswfv6uaxgcgcbdg@emailprotection.domainnameshop.com
- TLD · .no
- Browse hostnames · p3…
- Glossary · What is a hostname?
- Whisper Internet Directory — home
- Live MOAS conflicts feed
- Threat feed · Spamhaus DROP
- United States internet infrastructure
Cypher and MCP
Reproduce the resolution chain directly against graph.whisper.security:
MATCH (h:HOSTNAME {name: "p3.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.