IPDebrief

35.247.189.233

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

IP Intelligence Briefing: 35.247.189.233

Date: 2026-06-01

---

**1. Risk Profile**

---

**2. Network & Ownership**

---

**3. Threat & Activity Observations**

- TLS handshake (TLS1.3, AES-256-GCM).

- HTTP/2 server with 503 status code (potential misconfiguration).

---

**4. Relationships & Dependencies**

- DNS: `233.189.247.35.bc.googleusercontent.com` (Google-managed).

- Network: "GOOGLE-CLOUD" ASN (AS396982).

---

**5. Neighborhood Analysis**

- 0 abusive IPs, 0 high-risk neighbors.

- All sibling IPs unclassified (no active threats).

---

**6. Recommendations**

---

Source: IPDebrief Threat Intelligence Platform | Copyright 2026

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

🌍 Geolocation

CountryπŸ‡ΈπŸ‡¬ Singapore
RegionSG
CitySingapore
TimezoneAsia/Singapore
Latitude1.35
Longitude103.82

🏒 Ownership & Registration

OrganizationGoogle LLC
ASNAS396982
Network NameGOOGLE-CLOUD
CIDR Block35.208.0.0/12
RIRARIN
CountryUnited States
Abuse ContactAvailable via RDAP

🌐 DNS Intelligence

PTR233.189.247.35.bc.googleusercontent.com
Forward ConfirmedYes β€” FCrDNS verified
Forward Hostnames233.189.247.35.bc.googleusercontent.com

πŸ” DNS Hygiene

Hygiene Score100% (Excellent)
SPFPresent
DMARCPresent
FCrDNSVerified
DNSSECValid
CAAPresent

☁️ Network Classification

InfrastructureInfrastructure / Datacenter
Service PurposeWeb Server
Network TierTier 3 β€” Basic operator with some routing infrastructure
CloudHosting

πŸ”Œ Services & Open Ports

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

πŸ” TLS Certificate

A self-signed certificate was detected. This is common for development servers, internal services, or IoT devices.
⚠️
CN=letsencrypt-nginx-proxy-companion
Issued by CN=letsencrypt-nginx-proxy-companion
Self-signed: Yes
SANsNone
Valid From2026-01-21T15:23:09+00:00
Valid Until2027-01-21T15:23:09+00:00
TLS ProtocolTls13
Cipher SuiteTLS_AES_256_GCM_SHA384
Signature Algorithmsha256RSA
Validity Period365 days
Serial Number7BEBB975973C7123EFF45E9A1029E0AEAD88A54D
Thumbprint18440A0B4378424AEBE12342DDFE51C9180C1D65

🎯 Confidence Breakdown

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

DimensionScoreSourcesObservations
threat
27%
24
routing
27%
23
services
27%
23
ownership
30%
34
reputation
22%
13
geolocation
27%
23
Overall27%1220
Coverage: 6/6 dimensions Β· Data sufficiency: sufficient
Data CoherenceConsistent (100%)
AttributionModerate (70%)
OwnershipFCrDNSGeo ConsensusGeo PlausibleIRR MatchRPKI Valid

πŸ“… Observation Timeline πŸ”„ Live

First Seen2026-05-28 06:16:27 UTC
Last Seen2026-06-29 05:14:02 UTC
Profile Built2026-06-29 05:18:53 UTC
Data FreshnessLive
Signal Types30
Total Observations30
πŸ” 30 signal types Β· 30 observations collected
This report is generated from 30+ 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.