IPDebrief

31.76.11.83

IP Intelligence Dossier
Your IP: 216.73.217.131
{ } JSON 🔧 Full Actions API

🌍 Geolocation

Country🇩🇪 Germany
Region—
City—
TimezoneEurope/Berlin
Latitude—
Longitude—

🏢 Ownership & Registration

OrganizationAbuse contact role object
ASNAS215439
Network NamePLAY2GO-CUSTOMERS-NETWORK
CIDR Block31.76.11.0/24
RIRRIPE
CountryDE
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 Score60% (Good)
SPFPresent
DMARCPresent
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—
22sshtcpBanner detected
Closed Ports25, 80, 3389, 8080, 8443 (2 open / 7 scanned)
ServerWeb server detected
HTTP Title—

🔐 TLS Certificate

An expired certificate for CN=*.telegram.org was found on this IP. This may indicate a previously hosted website, a decommissioned service, or stale infrastructure.
🔒
CN=*.telegram.org
Issued by CN=Go Daddy Secure Certificate Authority - G2, OU=http://certs.godaddy.com/repository/, O="GoDaddy.com, Inc.", L=Scottsdale, S=Arizona, C=US
Self-signed: No
SANs*.telegram.orgtelegram.org
Valid From2025-08-11T13:36:48+00:00
Valid Until2026-09-12T13:36:48+00:00 (expired)

🛡️ Public Network Snapshot

Origin ASNAS215439
Network Prefix31.76.11.0/24
Route mappingFound
HSTSEnabled
CSPNot detected
HTTP/2Enabled

🎯 Confidence Breakdown

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

DimensionScoreSourcesObservations
threat
31%
25
routing
8%
11
services
17%
23
ownership
17%
23
reputation
22%
14
geolocation
17%
23
Overall19%1019
Coverage: 6/6 dimensions · Data sufficiency: sufficient
Data CoherenceMixed Signals (60%) — 2 contradiction(s)
AttributionVery Low (20%)
OwnershipFCrDNSGeo ConsensusGeo PlausibleIRR MatchRPKI Valid
⚠ Claimed geolocation contradicts RTT physics measurement
⚠ Geo sources disagree on country: GB, DE

📅 Observation Timeline 🔄 Live

First Seen2026-07-13 21:32:30 UTC
Last Seen2026-09-14 05:25:46 UTC
Profile Built2026-09-14 05:30:50 UTC
Data FreshnessLive
Signal Types21
Total Observations33
🔍 21 signal types · 33 observations collected
This report is generated from 21+ 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

❓ Frequently Asked Questions About 31.76.11.83

Who owns the IP address 31.76.11.83?

31.76.11.83 is registered to Abuse contact role object. The address falls within the 31.76.11.0/24 network block. Registration is held at RIPE.

Where is 31.76.11.83 located?

Geolocation data places 31.76.11.83 in Germany. The local time zone is Europe/Berlin. IP geolocation is approximate and indicates the network's registered or routed location rather than a precise physical address.

Is 31.76.11.83 malicious or safe?

31.76.11.83 currently carries a moderate risk assessment, meaning some indicators warrant caution, but the evidence is mixed. This assessment is generated from continuously collected signals and can change over time.

What ports are open on 31.76.11.83?

Responsive ports observed on 31.76.11.83 include 443, 22. Port visibility reflects the most recent scan and may change as the host's configuration or firewall rules change.

🏘️ Related IP Addresses

Nearby addresses in 31.76.11.0/24

Browse related networks

ℹ️ 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.