64.31.6.18
64.31.6.18 is an IPv4 address operated by LIMESTONENETWORKS - Limestone Networks, Inc., US (AS46475), with approximate network location Los Angeles, United States. As of November 13, 2026, IPDebrief rates it Low Risk (0/100); no anonymizing service was detected.
🏢 Ownership & Registration
| Registered holder | Private Customer |
| ASN | AS46475 |
| Network Name | LSN-DLLSTX-1 |
| CIDR Block | 64.31.6.16/29 |
| RIR | ARIN |
| Network registration country | Spain |
| Routing operator | LIMESTONENETWORKS - Limestone Networks, Inc., US |
| Abuse Contact | — |
🌐 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 | — |
| HTTP Title | — |
🔐 TLS Certificate
| Port | Probe target | Certificate finding |
|---|---|---|
| (IP-targeted) | CN=dummy.local Historical certificate; current certificate unknown |
| SANs | None |
| Valid From | 2025-07-31T14:12:54+00:00 |
| Valid Until | 2035-07-29T14:12:54+00:00 |
| TLS Protocol | Tls13 |
| Cipher Suite | TLS_AES_256_GCM_SHA384 |
| Signature Algorithm | sha256RSA |
| Validity Period | 3650 days |
🛡️ Public Network Snapshot
| Origin ASN | AS46475 |
| Network Prefix | 64.31.6.0/23 |
| Route mapping | Found |
🎯 Confidence Breakdown
Per-dimension confidence scores based on source diversity and data freshness
| Dimension | Score | Sources | Observations |
|---|---|---|---|
| threat | 33% | 2 | 4 |
| routing | 13% | 1 | 1 |
| services | 33% | 2 | 4 |
| ownership | 19% | 2 | 2 |
| reputation | 13% | 1 | 2 |
| geolocation | 35% | 2 | 3 |
| Overall | 24% | 10 | 16 |
| Data Coherence | Consistent (100%) |
| Attribution | Low (35%) |
| OwnershipFCrDNSGeo ConsensusGeo PlausibleIRR MatchRPKI Valid |
📅 Observation Timeline 🔄 Aging
| First Seen | 2026-10-02 23:20:23 UTC |
| Last Seen | 2026-10-25 02:42:36 UTC |
| Profile Built | 2026-11-13 05:11:55 UTC |
| Data Freshness | Aging |
| Signal Types | 21 |
| Total Observations | 27 |
Full dossier details are available via our API.
❓ Frequently Asked Questions About 64.31.6.18
Who owns the IP address 64.31.6.18?
64.31.6.18 is registered to Private Customer. The address falls within the 64.31.6.16/29 network block. Registration is held at ARIN.
Where is 64.31.6.18 located?
Geolocation data places 64.31.6.18 in Los Angeles, CA, United States. The local time zone is America/Los_Angeles. IP geolocation is approximate, not a precise physical address. Registration country and certificate organization addresses do not establish service location.
Is 64.31.6.18 malicious or safe?
64.31.6.18 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 64.31.6.18?
Responsive ports observed on 64.31.6.18 include 80, 443. Port visibility reflects the most recent scan and may change as the host's configuration or firewall rules change.