192.3.221.52
192.3.221.52 is an IPv4 address operated by AS-COLOCROSSING - HostPapa, US (AS36352), with approximate network location Newark, United States. As of November 13, 2026, IPDebrief rates it Low Risk (0/100); no anonymizing service was detected.
🏢 Ownership & Registration
| Registered holder | RackNerd LLC |
| ASN | AS36352 |
| Network Name | CC-192-3-221-0-27 |
| CIDR Block | 192.3.221.32/27 |
| RIR | ARIN |
| Network registration country | United States |
| Routing operator | AS-COLOCROSSING - HostPapa, US |
| Abuse Contact | — |
🌐 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.
| caa | Not checked |
| spf | Not checked |
| dmarc | Not checked |
| dnssec | Not checked |
| fcrDns | Not checked |
☁️ Network Classification
| Infrastructure | Unknown |
| Service Purpose | Web Server |
| Network Tier | Unknown — Insufficient routing data to classify |
🔌 Services & Open Ports
| Port | Service | Protocol | Banner |
|---|---|---|---|
| 443 | https | tcp | — |
| 22 | ssh | tcp | Banner detected |
| Closed Ports | 25, 80, 3389, 8080, 8443 (2 open / 7 scanned) | ||
| Server | — |
| HTTP Title | — |
🔐 TLS Certificate
| Port | Probe target | Certificate finding |
|---|---|---|
| (IP-targeted) | CN=los.mahaodong.top Previously observed certificate has since expired; current certificate unknown |
| SANs | los.mahaodong.top |
| Valid From | 2026-07-15T05:00:02+00:00 |
| Valid Until | 2026-10-13T05:00:01+00:00 |
| TLS Protocol | Tls13 |
| Cipher Suite | TLS_AES_128_GCM_SHA256 |
| Signature Algorithm | sha384ECDSA |
| Validity Period | 89 days |
🛡️ Public Network Snapshot
| Origin ASN | AS36352 |
| Network Prefix | 192.3.221.0/24 |
| Route mapping | Found |
| HSTS | Not detected |
| CSP | Not detected |
| HTTP/2 | Enabled |
🎯 Confidence Breakdown
Per-dimension confidence scores based on source diversity and data freshness
| Dimension | Score | Sources | Observations |
|---|---|---|---|
| threat | 17% | 2 | 3 |
| routing | 8% | 1 | 1 |
| services | 17% | 2 | 3 |
| ownership | 12% | 2 | 2 |
| reputation | 8% | 1 | 2 |
| geolocation | 17% | 2 | 3 |
| Overall | 13% | 10 | 14 |
| Data Coherence | Consistent (100%) |
| Attribution | Very Low (20%) |
| OwnershipFCrDNSGeo ConsensusGeo PlausibleIRR MatchRPKI Valid |
📅 Observation Timeline 🔄 Stale
| First Seen | 2026-07-08 13:02:59 UTC |
| Last Seen | 2026-10-06 10:19:04 UTC |
| Profile Built | 2026-11-13 04:12:06 UTC |
| Data Freshness | Stale |
| Signal Types | 22 |
| Total Observations | 22 |
Full dossier details are available via our API.
❓ Frequently Asked Questions About 192.3.221.52
Who owns the IP address 192.3.221.52?
192.3.221.52 is registered to RackNerd LLC. The address falls within the 192.3.221.32/27 network block. Registration is held at ARIN.
Where is 192.3.221.52 located?
Geolocation data places 192.3.221.52 in Newark, California, United States. IP geolocation is approximate, not a precise physical address. Registration country and certificate organization addresses do not establish service location.
Is 192.3.221.52 malicious or safe?
192.3.221.52 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 192.3.221.52?
Responsive ports observed on 192.3.221.52 include 443, 22. Port visibility reflects the most recent scan and may change as the host's configuration or firewall rules change.