IPDebrief

45.135.196.219

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

IP Intelligence Briefing: 45.135.196.219

*Generated via IPDebrief Analysis*

---

**1. Core Profile**

---

**2. Observation History**

- DNSBL listings (3/8 total lists) detected in June 2026.

- Subnet abuse density: 0.2 (mostly clean, 2 threat siblings in /24 range).

- No persistent malicious behavior or ownership changes.

---

**3. Network Relationships**

---

**4. Neighborhood Analysis**

- 1 high-risk IP (45.135.196.78, 80/100 score).

- 8 medium-risk IPs (40–55/100).

- 1 low-risk IP (45.135.196.79, 0/100).

---

**5. Recommendations**

---

Conclusion: This IP is part of a low-to-moderate risk network with no direct malicious activity. However, its subnet contains some risky neighbors, warranting closer monitoring. No immediate mitigation required unless the subnet’s abuse density escalates.

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

🌍 Geolocation

CountryπŸ‡ͺπŸ‡Έ Spain
RegionAndalusia
CityAlbox
TimezoneEurope/Madrid
Latitude37.38
Longitude-2.14

🏒 Ownership & Registration

Organizationes-digitalbox-1-mnt
ASNAS202375
Network NameES-DIGITALBOX-20190731
CIDR Block45.135.196.0/22
RIRARIN
CountryES
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
8443https-alttcpβ€”
Closed Ports25, 80, 3389, 8080 (3 open / 7 scanned)
Serverlighttpd/1.4.54
HTTP Titleβ€”
SSH VersionSSH-2.0-dropbear ?V??J^?T??l?(mC???curve25519-sha256,curve25519-sha256@libssh.org,diffie-hellman-gr

πŸ” TLS Certificate

A self-signed certificate was detected. This is common for development servers, internal services, or IoT devices.
⚠️
E=support@ubnt.com, CN=UBNT-F4:E2:C6:3E:F7:3A, OU=Technical Support, O=Ubiquiti Networks Inc., L=San Jose, S=CA, C=US
Issued by E=support@ubnt.com, CN=UBNT-F4:E2:C6:3E:F7:3A, OU=Technical Support, O=Ubiquiti Networks Inc., L=San Jose, S=CA, C=US
Self-signed: Yes
SANsUBNT-F4:E2:C6:3E:F7:3A
Valid From2019-01-01T00:00:00+00:00
Valid Until2038-01-01T00:00:00+00:00
TLS ProtocolTls13
Cipher SuiteTLS_AES_256_GCM_SHA384
Signature Algorithmsha256RSA
Validity Period6940 days
Serial Number8DD11472
ThumbprintC5AAF735726DFB3DBCD44B13ED3F799F68A54B6B

🎯 Confidence Breakdown

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

DimensionScoreSourcesObservations
threat
42%
23
routing
25%
11
services
13%
11
ownership
27%
23
reputation
28%
13
geolocation
27%
22
Overall27%913
Coverage: 6/6 dimensions Β· Data sufficiency: sufficient
Data CoherenceMixed Signals (68%) β€” 2 contradiction(s)
AttributionLow (35%)
OwnershipFCrDNSGeo ConsensusGeo PlausibleIRR MatchRPKI Valid
⚠ Geo sources disagree on country: ES, US
⚠ TLS certificate claims US but primary geo says ES

πŸ“… Observation Timeline πŸ”„ Live

First Seen2026-05-14 01:10:02 UTC
Last Seen2026-06-07 02:09:41 UTC
Profile Built2026-06-07 02:21:37 UTC
Data FreshnessLive
Signal Types23
Total Observations23
πŸ” 23 signal types Β· 23 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.