IPDebrief

142.250.31.119

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.

Intelligence analysis identified 142.250.31.119 as a Google LLC cloud compute host within the 142.250.0.0/15 block. The infrastructure resolved to the hostname bj-in-f119.1e100.net and responded to HTTP and HTTPS requests with a "gws" server banner. Risk assessment assigned a score of 25, categorizing the address as low risk.

Operational data indicated the endpoint appeared on one of eight DNS blocklists, yet the surrounding neighborhood classification remained clean with zero abuse density. Control plane metrics showed route instability. Threat actor classification flagged the host as suspicious; however, behavioral logs showed no active attacks, honeypot interactions, or enumeration strikes.

Technical inspection revealed TLS certificate validation failures with an issuer labeled "invalid2.invalid." The recommendation was to monitor the traffic due to low severity and the clean neighborhood context. No immediate threat indicators were confirmed despite the suspicious host tag.

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
ASNAS15169
Network NameGOOGLE
CIDR Block142.250.0.0/15
RIRARIN
CountryUnited States
Abuse ContactAvailable via RDAP

🌐 DNS Intelligence

PTRbj-in-f119.1e100.net
Forward ConfirmedYes β€” FCrDNS verified
Forward Hostnamesbj-in-f119.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-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 Number0A0192130865F4876CD88E4C2FC591
ThumbprintAF3BC8F83CFF426D599E24002419EC614AC33EBF

🎯 Confidence Breakdown

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

DimensionScoreSourcesObservations
threat
25%
11
routing
25%
11
services
25%
11
ownership
0%
00
reputation
0%
00
geolocation
25%
11
Overall16%44
Coverage: 4/6 dimensions Β· Data sufficiency: partial
Data CoherenceConsistent (100%)
AttributionModerate (70%)
OwnershipFCrDNSGeo ConsensusGeo PlausibleIRR MatchRPKI Valid

πŸ“… Observation Timeline πŸ”„ Live

First Seen2026-09-15 22:30:49 UTC
Last Seen2026-09-15 22:30:49 UTC
Profile Built2026-09-15 22:48:22 UTC
Data FreshnessLive
Signal Types22
Total Observations22
πŸ” 22 signal types Β· 22 observations collected
This report is generated from 22+ 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.