IPDebrief

172.253.115.139

IP Intelligence Dossier
Your IP: 216.73.217.34
{ } JSON πŸ”§ Full Actions API
πŸ€– Witness AIThis summary was generated by AI and may contain inaccuracies. Verify critical details independently.

IP 172.253.115.139 was identified as an infrastructure asset belonging to Google LLC (ASN 15169) within the 172.253.0.0/16 block. The address resolved to a CloudCompute web server located in New York, US. Risk analysis assigned a reputation of Low Risk with a risk score of 0.0. Network services were observed on ports 80 and 443 supporting HTTP and HTTPS traffic, resolving to the PTR hostname bg-in-f139.1e100.net. Authentication records confirmed the presence of SPF and DMARC policies. Threat intelligence feeds reported zero blacklists, known campaigns, or abuse indicators. Behavioral monitoring recorded zero malicious activity, including zero honeypot hits or WAF violations. The neighborhood assessment classified the subnet as clean with zero threat siblings. The overall recommendation was to allow traffic based on high authority scores and trusted infrastructure status.

This summary was generated by AI and may contain inaccuracies. Verify critical details independently.

🌍 Geolocation

CountryπŸ‡ΊπŸ‡Έ United States
RegionUS-NY
CityNew York
Timezoneβ€”
Latitudeβ€”
Longitudeβ€”

🏒 Ownership & Registration

OrganizationGoogle LLC
ASNAS15169
Network NameGOOGLE
CIDR Block172.253.0.0/16
RIRARIN
CountryUnited States
Abuse ContactAvailable via RDAP

🌐 DNS Intelligence

PTRbg-in-f139.1e100.net
Forward ConfirmedYes β€” FCrDNS verified
Forward Hostnamesbg-in-f139.1e100.net

πŸ” DNS Hygiene

Hygiene Score80% (Excellent)
SPFPresent
DMARCPresent
FCrDNSVerified
DNSSECNot signed
CAAPresent

☁️ Network Classification

InfrastructureInfrastructure / Datacenter
Service PurposeWeb Server
Network TierHosting β€” Infrastructure provider without advanced routing
CloudHosting

πŸ”Œ Services & Open Ports

PortServiceProtocolBanner
80httptcpβ€”
443httpstcpβ€”
Closed Ports22, 25, 3389, 8080, 8443 (2 open / 7 scanned)
Servergws
HTTP Titleβ€”

πŸ” TLS Certificate

A self-signed certificate was detected. This is common for development servers, internal services, or IoT devices.
⚠️
CN=invalid2.invalid, OU=No SNI provided - please fix your client.
Issued by CN=invalid2.invalid, OU=No SNI provided - please fix your client.
Self-signed: Yes
SANsinvalid2.invalid
Valid From2026-09-04T09:09:26+00:00
Valid Until2026-11-27T09:09:25+00:00
TLS ProtocolTls13
Cipher SuiteTLS_AES_256_GCM_SHA384
Signature Algorithmsha256RSA
Validity Period83 days
Serial Number6D68D40D8C521DCB61CE9EDFA7A69C64
Thumbprint24457C193824715270B0CD97584E95F19A01432E

🎯 Confidence Breakdown

Per-dimension confidence scores based on source diversity and data freshness

DimensionScoreSourcesObservations
threat
35%
22
routing
25%
11
services
25%
11
ownership
0%
00
reputation
25%
11
geolocation
0%
00
Overall18%55
Coverage: 4/6 dimensions Β· Data sufficiency: partial
Data CoherenceMostly Consistent (80%) β€” 1 contradiction(s)
AttributionModerate (55%)
OwnershipFCrDNSGeo ConsensusGeo PlausibleIRR MatchRPKI Valid
⚠ Claimed geolocation contradicts RTT physics measurement

πŸ“… Observation Timeline πŸ”„ Live

First Seen2026-09-17 21:09:58 UTC
Last Seen2026-09-17 21:09:58 UTC
Profile Built2026-09-17 21:19:38 UTC
Data FreshnessLive
Signal Types23
Total Observations23
πŸ” 23 signal types Β· 23 observations collected
This report is generated from 23+ independent intelligence signals including ownership records, DNS analysis, BGP routing, TLS certificates, port scanning, threat feeds, behavioral fingerprinting, and more.
Full dossier details are available via our API.
{ } JSON API πŸ”§ Actions API πŸ“§ Enterprise Access

ℹ️ About This Report

All data shown is publicly available network metadata β€” IP addresses do not reliably identify individuals. Assessments are probabilistic and should not be used as sole basis for access control decisions. To report an issue or request data review, contact admin@ipdebrief.com.