156.146.54.106
156.146.54.106 is an IPv4 address operated by DATACAMP-MNT (AS212238), geolocated to San Jose, United Kingdom. Its reverse DNS name is unn-156-146-54-106.cdn77.com. As of October 24, 2026, IPDebrief rates it Low Risk (20/100); no anonymizing service was detected.
Intelligence Briefing: 156.146.54.106/32
Ownership analysis confirmed the address belongs to DATACAMP-MNT (ASN 212238) within the CDNEXT-SJC CIDR block (156.146.54.0/24). Risk assessment assigned a Low Risk score of 20, with zero known attacker indicators, spam source flags, or blacklist listings. Network scanning indicated the host was Firewalled with no open ports or active services.
Forensic validation highlighted a geolocation contradiction, noting RTT measurements of 83ms contradicted the claimed distance to San Jose, GB (minimum 177.2ms). Route stability was recorded as false, and overall confidence remained Very Low (0.125). DNS hygiene scored 60, confirming valid SPF and DMARC records for the resolved PTR hostname (unn-156-146-54-106.cdn77.com).
Due to signal contradictions and low data sufficiency, the profile recommended a Monitor action with low severity.
This summary was generated by AI and may contain inaccuracies. Verify critical details independently.
🏢 Ownership & Registration
| Organization | DATACAMP-MNT |
| ASN | AS212238 |
| Network Name | CDNEXT-SJC |
| CIDR Block | 156.146.54.0/24 |
| RIR | ARIN |
| Country | US |
| Abuse Contact | Available via RDAP |
🌐 DNS Intelligence
| PTR | unn-156-146-54-106.cdn77.com |
| Forward Confirmed | No — PTR hostname does not resolve back to this IP (weak signal) |
| Forward Hostnames | unn-156-146-54-106.cdn77.com |
🔐 DNS Hygiene
| Hygiene Score | 60% (Good) |
| SPF | Present |
| DMARC | Present |
| FCrDNS | Not verified |
| DNSSEC | Not signed |
| CAA | Present |
☁️ Network Classification
| Infrastructure | Unknown |
| Service Purpose | Firewalled / No Services |
| Network Tier | Unknown — Insufficient routing data to classify |
🔌 Services & Open Ports
| Port | Service | Protocol | Banner |
|---|---|---|---|
| No open ports detected | |||
| Closed Ports | 22, 25, 80, 443, 3389, 8080, 8443 (0 open / 7 scanned) | ||
| Server | — |
| HTTP Title | — |
🔐 TLS Certificate
| SANs | None |
| Valid From | — |
| Valid Until | — |
🛡️ Public Network Snapshot
| Origin ASN | AS212238 |
| Network Prefix | 156.146.54.0/24 |
| Route mapping | Found |
🎯 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 | 0% | 0 | 0 |
| reputation | 0% | 0 | 0 |
| geolocation | 0% | 0 | 0 |
| Overall | 12% | 3 | 3 |
| Data Coherence | Mostly Consistent (80%) — 1 contradiction(s) |
| Attribution | Low (35%) |
| OwnershipFCrDNSGeo ConsensusGeo PlausibleIRR MatchRPKI Valid |
📅 Observation Timeline 🔄 Live
| First Seen | 2026-10-24 05:31:38 UTC |
| Last Seen | 2026-10-24 05:31:38 UTC |
| Profile Built | 2026-10-24 05:47:32 UTC |
| Data Freshness | Live |
| Signal Types | 18 |
| Total Observations | 18 |
Full dossier details are available via our API.
❓ Frequently Asked Questions About 156.146.54.106
Who owns the IP address 156.146.54.106?
156.146.54.106 is registered to DATACAMP-MNT. The address falls within the 156.146.54.0/24 network block. Registration is held at ARIN.
Where is 156.146.54.106 located?
Geolocation data places 156.146.54.106 in San Jose, CA, United Kingdom. The local time zone is Europe/London. IP geolocation is approximate and indicates the network's registered or routed location rather than a precise physical address.
Is 156.146.54.106 malicious or safe?
156.146.54.106 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 is the hostname for 156.146.54.106?
The reverse DNS (PTR) record for 156.146.54.106 is unn-156-146-54-106.cdn77.com. This hostname is not forward-confirmed, so it should be treated as a weak signal.