170.23.51.231
170.23.51.231 is an IPv4 address operated by SERVERS-COM - Servers.com, Inc., US (AS7979), with approximate network location United States. Its reverse DNS name is axis.dathost.net. As of November 13, 2026, IPDebrief rates it Low Risk (0/100); no anonymizing service was detected.
🏢 Ownership & Registration
| Registered holder | Servers.com, Inc. |
| ASN | AS7979 |
| Network Name | SERVERS-COM-WAS3 |
| CIDR Block | 170.23.48.0/22 |
| RIR | ARIN |
| Network registration country | United States |
| Routing operator | SERVERS-COM - Servers.com, Inc., US |
| Abuse Contact | Available via RDAP |
🌐 DNS Intelligence
| PTR | axis.dathost.net |
| Forward Confirmed | Yes — FCrDNS verified |
| Forward Hostnames | axis.dathost.net |
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 | Present / verified dathost.net |
| spf | Unknown / lookup inconclusive axis.dathost.net, dathost.net |
| dmarc | Unknown / lookup inconclusive _dmarc.axis.dathost.net, _dmarc.dathost.net |
| dnssec | Unknown / lookup inconclusive 231.51.23.170.in-addr.arpa |
| fcrDns | Unknown / lookup inconclusive axis.dathost.net |
☁️ 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=*.dathost.net Historical certificate; current certificate unknown |
| SANs | *.dathost.netdathost.net |
| Valid From | 2026-09-23T12:06:56+00:00 |
| Valid Until | 2026-12-22T12:06:55+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.51.0/24 |
| Route mapping | Found |
| HSTS | Enabled |
| CSP | Not detected |
| HTTP/2 | Enabled |
🎯 Confidence Breakdown
Per-dimension confidence scores based on source diversity and data freshness
| Dimension | Score | Sources | Observations |
|---|---|---|---|
| threat | 25% | 1 | 1 |
| routing | 25% | 1 | 1 |
| services | 25% | 1 | 1 |
| ownership | 0% | 0 | 0 |
| reputation | 0% | 0 | 0 |
| geolocation | 25% | 1 | 1 |
| Overall | 16% | 4 | 4 |
| Data Coherence | Consistent (100%) |
| Attribution | Moderate (55%) |
| OwnershipFCrDNSGeo ConsensusGeo PlausibleIRR MatchRPKI Valid |
📅 Observation Timeline 🔄 Live
| First Seen | 2026-11-01 17:10:22 UTC |
| Last Seen | 2026-11-08 02:30:52 UTC |
| Profile Built | 2026-11-13 07:34:55 UTC |
| Data Freshness | Live |
| Signal Types | 20 |
| Total Observations | 27 |
Full dossier details are available via our API.
❓ Frequently Asked Questions About 170.23.51.231
Who owns the IP address 170.23.51.231?
170.23.51.231 is registered to Servers.com, Inc.. The address falls within the 170.23.48.0/22 network block. Registration is held at ARIN.
Where is 170.23.51.231 located?
Geolocation data places 170.23.51.231 in United States. IP geolocation is approximate, not a precise physical address. Registration country and certificate organization addresses do not establish service location.
Is 170.23.51.231 malicious or safe?
170.23.51.231 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 is the hostname for 170.23.51.231?
The reverse DNS (PTR) record for 170.23.51.231 is axis.dathost.net. This hostname is forward-confirmed, meaning it resolves back to the same address.
What ports are open on 170.23.51.231?
Responsive ports observed on 170.23.51.231 include 80, 443. Port visibility reflects the most recent scan and may change as the host's configuration or firewall rules change.