202.12.28.136
202.12.28.136 is an IPv4 address operated by APNIC-COLO - Asia Pacific Network Information Centre, JP (AS4777), with approximate network location New York, United States. As of November 14, 2026, IPDebrief rates it Low Risk (15/100); no anonymizing service was detected.
🏢 Ownership & Registration
| Registered holder | APNIC Infrastructure Contact |
| ASN | AS4777 |
| Network Name | APNIC-SERVICES-JP |
| CIDR Block | 202.12.28.0/24 |
| RIR | APNIC |
| Network registration country | JP |
| Routing operator | APNIC-COLO - Asia Pacific Network Information Centre, JP |
| 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.
| caa | Present / verified apnic.net |
| spf | Not checked |
| dmarc | Not checked |
| dnssec | Unknown / lookup inconclusive 136.28.12.202.in-addr.arpa |
| 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 |
|---|---|---|---|
| 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
| Port | Probe target | Certificate finding |
|---|---|---|
| (IP-targeted) | CN=*.apnic.net Historical certificate; current certificate unknown |
| SANs | *.apnic.net |
| Valid From | 2026-09-24T17:08:40+00:00 |
| Valid Until | 2026-12-23T17:08:39+00:00 |
| TLS Protocol | Tls13 |
| Cipher Suite | TLS_AES_256_GCM_SHA384 |
| Signature Algorithm | sha256RSA |
| Validity Period | 89 days |
🛡️ Public Network Snapshot
| Origin ASN | AS4777 |
| Network Prefix | 202.12.28.0/24 |
| Route mapping | Found |
| Certificates in transparency logs | 0 certificates |
| HSTS | Enabled |
| 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 | 44% | 2 | 6 |
| routing | 13% | 1 | 1 |
| services | 30% | 2 | 4 |
| ownership | 30% | 2 | 4 |
| reputation | 37% | 1 | 5 |
| geolocation | 27% | 2 | 3 |
| Overall | 30% | 10 | 23 |
| Data Coherence | Mostly Consistent (80%) — 1 contradiction(s) |
| Attribution | Very Low (20%) |
| OwnershipFCrDNSGeo ConsensusGeo PlausibleIRR MatchRPKI Valid |
📅 Observation Timeline 🔄 Recent
| First Seen | 2026-10-22 21:45:55 UTC |
| Last Seen | 2026-11-12 08:12:30 UTC |
| Profile Built | 2026-11-14 04:35:20 UTC |
| Data Freshness | Recent |
| Signal Types | 24 |
| Total Observations | 34 |
Full dossier details are available via our API.
❓ Frequently Asked Questions About 202.12.28.136
Who owns the IP address 202.12.28.136?
202.12.28.136 is registered to APNIC Infrastructure Contact. The address falls within the 202.12.28.0/24 network block. Registration is held at APNIC.
Where is 202.12.28.136 located?
Geolocation data places 202.12.28.136 in New York, US-NY, 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 202.12.28.136 malicious or safe?
202.12.28.136 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 202.12.28.136?
Responsive ports observed on 202.12.28.136 include 80, 443. Port visibility reflects the most recent scan and may change as the host's configuration or firewall rules change.