104.168.4.245
104.168.4.245 is an IPv4 address operated by AS-COLOCROSSING - HostPapa, US (AS36352), with approximate network location Buffalo, United States. As of November 13, 2026, IPDebrief rates it Low Risk (0/100); no anonymizing service was detected.
🏢 Ownership & Registration
| Registered holder | Ankit Jain |
| ASN | AS36352 |
| Network Name | CC-104-168-4-0-27 |
| CIDR Block | 104.168.4.224/27 |
| RIR | ARIN |
| Network registration country | India |
| 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 |
|---|---|---|---|
| 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=*.198107.xyz Previously observed certificate has since expired; current certificate unknown |
| SANs | *.198107.xyz |
| Valid From | 2026-08-13T01:27:08+00:00 |
| Valid Until | 2026-11-11T01:27:07+00:00 |
| TLS Protocol | Tls13 |
| Cipher Suite | TLS_AES_256_GCM_SHA384 |
| Signature Algorithm | sha384ECDSA |
| Validity Period | 89 days |
🛡️ Public Network Snapshot
| Origin ASN | AS36352 |
| Network Prefix | 104.168.4.0/22 |
| Route mapping | Found |
| HSTS | Enabled |
| CSP | Not detected |
| HTTP/2 | Enabled |
🎯 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 | 35% | 2 | 2 |
| Overall | 18% | 5 | 5 |
| Data Coherence | Consistent (100%) |
| Attribution | Very Low (20%) |
| OwnershipFCrDNSGeo ConsensusGeo PlausibleIRR MatchRPKI Valid |
📅 Observation Timeline 🔄 Stale
| First Seen | 2026-07-17 11:03:27 UTC |
| Last Seen | 2026-10-06 01:51:25 UTC |
| Profile Built | 2026-11-13 03:32:05 UTC |
| Data Freshness | Stale |
| Signal Types | 19 |
| Total Observations | 23 |
Full dossier details are available via our API.
❓ Frequently Asked Questions About 104.168.4.245
Who owns the IP address 104.168.4.245?
104.168.4.245 is registered to Ankit Jain. The address falls within the 104.168.4.224/27 network block. Registration is held at ARIN.
Where is 104.168.4.245 located?
Geolocation data places 104.168.4.245 in Buffalo, New York, United States. IP geolocation is approximate, not a precise physical address. Registration country and certificate organization addresses do not establish service location.
Is 104.168.4.245 malicious or safe?
104.168.4.245 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 104.168.4.245?
Responsive ports observed on 104.168.4.245 include 80, 443. Port visibility reflects the most recent scan and may change as the host's configuration or firewall rules change.