171.22.21.36
IP Intelligence Dossier
Your IP: 216.73.217.75
🏢 Ownership & Registration
| Organization | Unknown |
| ASN | — |
| Network Name | — |
| CIDR Block | — |
| RIR | — |
| Country | — |
| Abuse Contact | — |
🌐 DNS Intelligence
| PTR Record | No PTR |
| Forward Confirmed | No — PTR hostname does not resolve back to this IP (weak signal) |
🔐 DNS Hygiene
| Hygiene Score | 0% (None) |
| SPF | Not configured |
| DMARC | Not configured |
| FCrDNS | Not verified |
| DNSSEC | Not signed |
| CAA | Not configured |
☁️ Network Classification
| Infrastructure | Unknown |
| Service Purpose | Web Server |
| Network Tier | Unknown — Insufficient routing data to classify |
🔌 Services & Open Ports
| Port | Service | Protocol | Banner |
|---|---|---|---|
| 80 | http | tcp | — |
| 443 | https | tcp | — |
| 22 | ssh | tcp | Banner detected |
| Closed Ports | 25, 3389, 8080, 8443 (3 open / 7 scanned) | ||
| Server | Web server detected |
| HTTP Title | — |
🔐 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-24:5A:4C:C6:BF:D5, OU=Technical Support, O=Ubiquiti Networks Inc., L=San Jose, S=CA, C=US
Issued by E=support@ubnt.com, CN=UBNT-24:5A:4C:C6:BF:D5, OU=Technical Support, O=Ubiquiti Networks Inc., L=San Jose, S=CA, C=US
Self-signed: Yes
| SANs | UBNT-24:5A:4C:C6:BF:D5 |
| Valid From | 2019-01-01T00:00:00+00:00 |
| Valid Until | 2038-01-01T00:00:00+00:00 |
| TLS Protocol | Tls13 |
| Cipher Suite | TLS_AES_256_GCM_SHA384 |
| Signature Algorithm | sha256RSA |
| Validity Period | 6940 days |
🛡️ Public Network Snapshot
| Origin ASN | AS209491 |
| Network Prefix | 171.22.20.0/22 |
| Route mapping | Found |
| HSTS | Not detected |
| CSP | Not detected |
| HTTP/2 | Not detected |
📅 Observation Timeline 🔄 Live
| First Seen | 2026-11-06 02:39:36 UTC |
| Last Seen | 2026-11-06 02:39:36 UTC |
| Profile Built | 2026-11-06 02:53:17 UTC |
| Data Freshness | Live |
| Signal Types | 8 |
| Total Observations | 8 |
🔍 8 signal types · 8 observations collected
This report is generated from 8+ 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.
Full dossier details are available via our API.
❓ Frequently Asked Questions About 171.22.21.36
Where is 171.22.21.36 located?
Geolocation data places 171.22.21.36 in Zenica, Federation of Bosnia and Herzegovina, BA. IP geolocation is approximate and indicates the network's registered or routed location rather than a precise physical address.
Is 171.22.21.36 malicious or safe?
171.22.21.36 currently carries a low risk assessment, meaning no significant threat indicators have been observed. This assessment is generated from continuously collected signals and can change over time.
What ports are open on 171.22.21.36?
Responsive ports observed on 171.22.21.36 include 80, 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
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.