2.16.153.20
2.16.153.20 is an IPv4 address operated by Akamai (AS20940), with approximate network location Cambridge, United States. It belongs to datacenter or hosting infrastructure. As of November 12, 2026, IPDebrief rates it Low Risk (0/100); no anonymizing service was detected.
🏢 Ownership & Registration
| Registered holder | AKAM1-RIPE-MNT |
| ASN | AS20940 |
| Network Name | AKAMAI-PA |
| CIDR Block | 2.16.152.0/23 |
| RIR | RIPE |
| Network registration country | EU |
| Abuse Contact | Available via RDAP |
🌐 DNS Intelligence
| PTR Record | No PTR |
| Forward Confirmed | No — PTR hostname does not resolve back to this IP (weak signal) |
DNS Posture
Results describe the queried names. SPF, DMARC and CAA are domain policies, not requirements for every IP. DNSSEC here describes reverse DNS; inconclusive validation does not mean unsigned.
Not assessed: 0 conclusive IP DNS checks.
| spf | Not checked |
| dmarc | Not checked |
| fcrDns | Not checked |
| dnssec | Not checked |
| caa | Not checked |
☁️ Network Classification
| Infrastructure | Infrastructure / Datacenter |
| Service Purpose | Web Server |
| Network Tier | Hosting — Infrastructure provider without advanced routing |
🔌 Services & Open Ports
| Port | Service | Protocol | Banner |
|---|---|---|---|
| 80 | http | tcp | — |
| 443 | https | tcp | — |
| Closed Ports | 22, 25, 3389, 8080, 8443 (2 open / 7 scanned) | ||
| Server | Web server detected |
| HTTP Title | — |
🔐 TLS Certificate
| SANs | a248.e.akamai.net*.akamaihd-staging.net*.akamaihd.net*.akamaized-staging.net*.akamaized.net |
| Valid From | 2026-09-15T00:00:00+00:00 |
| Valid Until | 2027-04-01T23:59:59+00:00 |
| TLS Protocol | Tls13 |
| Cipher Suite | TLS_AES_256_GCM_SHA384 |
| Signature Algorithm | sha384ECDSA |
| Validity Period | 198 days |
🛡️ Public Network Snapshot
| Origin ASN | AS20940 |
| Network Prefix | 2.16.153.0/24 |
| Route mapping | Found |
| HSTS | Not detected |
| CSP | Not detected |
| HTTP/2 | Not detected |
🎯 Confidence Breakdown
Per-dimension confidence scores based on source diversity and data freshness
| Dimension | Score | Sources | Observations |
|---|---|---|---|
| threat | 25% | 1 | 1 |
| routing | 25% | 1 | 1 |
| services | 25% | 1 | 1 |
| ownership | 25% | 1 | 2 |
| reputation | 0% | 0 | 0 |
| geolocation | 50% | 2 | 3 |
| Overall | 25% | 6 | 8 |
| Data Coherence | Mostly Consistent (80%) — 1 contradiction(s) |
| Attribution | Low (35%) |
| OwnershipFCrDNSGeo ConsensusGeo PlausibleIRR MatchRPKI Valid |
📅 Observation Timeline 🔄 Aging
| First Seen | 2026-11-04 03:54:31 UTC |
| Last Seen | 2026-11-08 05:41:50 UTC |
| Profile Built | 2026-11-12 17:57:01 UTC |
| Data Freshness | Aging |
| Signal Types | 19 |
| Total Observations | 19 |
Full dossier details are available via our API.
❓ Frequently Asked Questions About 2.16.153.20
Who owns the IP address 2.16.153.20?
2.16.153.20 is registered to AKAM1-RIPE-MNT. The address falls within the 2.16.152.0/23 network block. Registration is held at RIPE.
Where is 2.16.153.20 located?
Geolocation data places 2.16.153.20 in Cambridge, MA, United States. The local time zone is America/New_York. IP geolocation is approximate, not a precise physical address. Registration country and certificate organization addresses do not establish service location.
Is 2.16.153.20 malicious or safe?
2.16.153.20 currently carries a low risk assessment, meaning no significant threat indicators have been observed. This assessment is generated from continuously collected signals and can change over time.
What ports are open on 2.16.153.20?
Responsive ports observed on 2.16.153.20 include 80, 443. Port visibility reflects the most recent scan and may change as the host's configuration or firewall rules change.
Is 2.16.153.20 a VPN, proxy, or data center address?
2.16.153.20 is classified as a content delivery network based on network ownership and behavioural analysis.