170.23.218.153
170.23.218.153 is an IPv4 address operated by SERVERS-COM - Servers.com, Inc., US (AS7979), with approximate network location Netherlands. As of November 14, 2026, IPDebrief rates it Low Risk (10/100); no anonymizing service was detected.
🏢 Ownership & Registration
| Registered holder | Servers Guy |
| ASN | AS7979 |
| Network Name | SERVERS-COM-DFW5 |
| CIDR Block | 170.23.216.0/22 |
| RIR | ARIN |
| Network registration country | US |
| Routing operator | SERVERS-COM - Servers.com, Inc., US |
| Abuse Contact | Available via RDAP |
🌐 DNS Intelligence
| PTR Record | No PTR |
| Forward Confirmed | No — PTR hostname does not resolve back to this IP (weak signal) |
DNS Posture
Results describe the queried names. SPF, DMARC and CAA are domain policies, not requirements for every IP. DNSSEC here describes reverse DNS; inconclusive validation does not mean unsigned.
Not assessed: 0 conclusive IP DNS checks.
| caa | Not checked |
| spf | Not checked |
| dmarc | Not checked |
| dnssec | Not checked |
| fcrDns | Not checked |
☁️ 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 | — |
| Closed Ports | 22, 25, 3389, 8080, 8443 (2 open / 7 scanned) | ||
| Server | Web server detected |
| HTTP Title | — |
🔐 TLS Certificate
| Port | Probe target | Certificate finding |
|---|---|---|
| (IP-targeted) | CN=bidease.com Historical certificate; current certificate unknown |
| SANs | *.bidease.combidease.com |
| Valid From | 2026-10-19T11:09:45+00:00 |
| Valid Until | 2027-01-17T11:09:44+00:00 |
| TLS Protocol | Tls13 |
| Cipher Suite | TLS_AES_256_GCM_SHA384 |
| Signature Algorithm | sha384ECDSA |
| Validity Period | 89 days |
🛡️ Public Network Snapshot
| Origin ASN | AS7979 |
| Network Prefix | 170.23.218.0/24 |
| Route mapping | Found |
| HSTS | Not detected |
| CSP | Not detected |
| HTTP/2 | Not detected |
🎯 Confidence Breakdown
Per-dimension confidence scores based on source diversity and data freshness
| Dimension | Score | Sources | Observations |
|---|---|---|---|
| threat | 50% | 2 | 3 |
| routing | 25% | 1 | 1 |
| services | 35% | 2 | 2 |
| ownership | 50% | 2 | 3 |
| reputation | 25% | 1 | 1 |
| geolocation | 50% | 2 | 3 |
| Overall | 39% | 10 | 13 |
| Data Coherence | Consistent (100%) |
| Attribution | Low (35%) |
| OwnershipFCrDNSGeo ConsensusGeo PlausibleIRR MatchRPKI Valid |
📅 Observation Timeline 🔄 Aging
| First Seen | 2026-10-20 00:53:56 UTC |
| Last Seen | 2026-11-01 09:09:49 UTC |
| Profile Built | 2026-11-14 05:41:36 UTC |
| Data Freshness | Aging |
| Signal Types | 26 |
| Total Observations | 26 |
Full dossier details are available via our API.
❓ Frequently Asked Questions About 170.23.218.153
Who owns the IP address 170.23.218.153?
170.23.218.153 is registered to Servers Guy. The address falls within the 170.23.216.0/22 network block. Registration is held at ARIN.
Where is 170.23.218.153 located?
Geolocation data places 170.23.218.153 in Netherlands. The local time zone is Europe/Amsterdam. IP geolocation is approximate, not a precise physical address. Registration country and certificate organization addresses do not establish service location.
Is 170.23.218.153 malicious or safe?
170.23.218.153 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 170.23.218.153?
Responsive ports observed on 170.23.218.153 include 80, 443. Port visibility reflects the most recent scan and may change as the host's configuration or firewall rules change.