IPDebrief

185.92.182.129

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: 185.92.182.129

Date: 2026-06-17

---

**1. Risk Profile**

- Listed in 3/8 threat feeds (low-severity).

- DNSSEC valid, but certificate is self-signed and invalid.

- No known malware campaigns or spam sources.

---

**2. Ownership & Geolocation**

- Region: Missouri (conflict with geolocation data; likely error).

- Coordinates: 52.13°N, 5.29°E (Amsterdam area).

---

**3. Network Behavior**

- Open ports: 443 (HTTPS), 22 (SSH).

- TLS certificate: Invalid, self-signed.

- HTTP server: Google Workspace (gws), 301 redirect.

---

**4. Threat Observations**

- 18 observations, 12 high-confidence.

- DNS and geolocation inferences with moderate accuracy.

- No persistent malicious activity detected.

---

**5. Relationships**

- Same network: as56971-net (CloudBackbone).

- No peer IPs or subdomains linked.

---

**6. Recommendations**

- Allow HTTPS (port 443) for legitimate traffic.

- Restrict SSH (port 22) to trusted sources.

Note: Low-risk but requires validation of certificate and geolocation accuracy. No immediate mitigation needed, but ongoing monitoring advised.

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

๐ŸŒ Geolocation

Country๐Ÿ‡ณ๐Ÿ‡ฑ Netherlands
RegionMissouri
CityKansas City
TimezoneEurope/Amsterdam
Latitude52.13
Longitude5.29

๐Ÿข Ownership & Registration

OrganizationCloudBackbone NOC
ASNAS56971
Network Nameโ€”
CIDR Block185.92.182.0/24
RIRRIPE
Countryโ€”
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 Score20% (Poor)
SPFNot configured
DMARCNot configured
FCrDNSNot verified
DNSSECValid
CAANot configured

โ˜๏ธ Network Classification

InfrastructureUnknown
Service PurposeWeb Server
Network TierUnknown โ€” Insufficient routing data to classify
No specific classification

๐Ÿ”Œ Services & Open Ports

PortServiceProtocolBanner
443httpstcpโ€”
22sshtcp
Closed Ports25, 80, 3389, 8080, 8443 (2 open / 7 scanned)
Servergws
HTTP Titleโ€”
SSH VersionSSH-2.0-OpenSSH_9.6p1 Ubuntu-3ubuntu13.14

๐Ÿ” 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-05-25T09:42:12+00:00
Valid Until2026-08-17T09:42:11+00:00
TLS ProtocolTls13
Cipher SuiteTLS_AES_256_GCM_SHA384
Signature Algorithmsha256RSA
Validity Period83 days
Serial Number0080E5CABDF41B68E0BA718F4A1224EFA3
Thumbprint3A63B90C03534246ABA67F1652C5B5CD08B7BAAB

๐ŸŽฏ Confidence Breakdown

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

DimensionScoreSourcesObservations
threat
25%
24
routing
27%
23
services
28%
23
ownership
24%
34
reputation
22%
13
geolocation
19%
22
Overall24%1219
Coverage: 6/6 dimensions ยท Data sufficiency: sufficient
Data CoherenceMostly Consistent (80%) โ€” 1 contradiction(s)
AttributionLow (35%)
OwnershipFCrDNSGeo ConsensusGeo PlausibleIRR MatchRPKI Valid
โš  Geo sources disagree on country: US, DE, NL

๐Ÿ“… Observation Timeline ๐Ÿ”„ Fresh

First Seen2026-05-07 23:04:01 UTC
Last Seen2026-06-26 18:10:55 UTC
Profile Built2026-06-25 23:25:27 UTC
Data FreshnessFresh
Signal Types24
Total Observations25
๐Ÿ” 24 signal types ยท 25 observations collected
This report is generated from 24+ 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.