IPDebrief

34.143.78.2

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.

On 2026-09-22, IP address 34.143.78.2/32 was analyzed. The asset was assigned to Google LLC under ASN 396982 within the 34.128.0.0/10 block. Reputation assessment classified the IP as Low Risk with a score of 25, yet the threat actor profile labeled it as a Suspicious Host. The network role was identified as CloudCompute and Hosting, presenting open ports 80 and 443 for HTTP and HTTPS respectively. A TLS certificate with the subject CN=invalid2.invalid was detected. Geolocation data was inconsistent, as the claimed US origin contradicted RTT physics measurements for the reported distance. Neighborhood analysis indicated an abuse density of 1 with one active threat sibling. DNS hygiene was absent, lacking SPF, DMARC, or DNSSEC records. The overall confidence level was Very Low, and the recommendation was to Monitor the asset for potential changes.

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

🌍 Geolocation

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

🏒 Ownership & Registration

OrganizationGoogle LLC
ASNAS396982
Network NameGOOGL-2
CIDR Block34.128.0.0/10
RIRARIN
CountryUnited States
Abuse ContactAvailable via RDAP

🌐 DNS Intelligence

PTR RecordNo PTR
Forward ConfirmedNo β€” PTR hostname does not resolve back to this IP (weak signal)

πŸ” DNS Hygiene

Hygiene Score0% (None)
SPF0/2 domains
DMARC0/2 domains
FCrDNSNot verified
DNSSECNot signed
CAANot configured
Domains Checked2 domains

☁️ 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)
Serverβ€”
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-08-10T09:42:20+00:00
Valid Until2026-11-02T09:42:19+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
38%
25
routing
13%
11
services
42%
26
ownership
27%
24
reputation
22%
14
geolocation
36%
27
Overall30%1027
Coverage: 6/6 dimensions Β· Data sufficiency: sufficient
Data CoherenceMostly Consistent (80%) β€” 1 contradiction(s)
AttributionLow (35%)
OwnershipFCrDNSGeo ConsensusGeo PlausibleIRR MatchRPKI Valid
⚠ Claimed geolocation contradicts RTT physics measurement

πŸ“… Observation Timeline πŸ”„ Live

First Seen2026-08-29 13:54:34 UTC
Last Seen2026-09-22 22:27:05 UTC
Profile Built2026-09-23 00:50:59 UTC
Data FreshnessLive
Signal Types23
Total Observations44
πŸ” 23 signal types Β· 44 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.