64.233.180.18
IP Intelligence Dossier
Your IP: 216.73.216.157
🏢 Ownership & Registration
| Organization | Unknown |
| ASN | — |
| Network Name | — |
| CIDR Block | — |
| RIR | — |
| Country | — |
| Abuse Contact | — |
🌐 DNS Intelligence
| PTR | on-in-f18.1e100.net |
| Forward Confirmed | Yes — FCrDNS verified |
| Forward Hostnames | on-in-f18.1e100.net |
🔐 DNS Hygiene
| Hygiene Score | 80% (Excellent) |
| SPF | Present |
| DMARC | Present |
| FCrDNS | Verified |
| DNSSEC | Not signed |
| CAA | Present |
☁️ 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
A self-signed certificate was detected. This is common for development servers, internal services, or IoT devices.
CN=invalid2.invalid, OU=No SNI provided - please fix your client.
Issued by CN=invalid2.invalid, OU=No SNI provided - please fix your client.
Self-signed: Yes
| SANs | invalid2.invalid |
| Valid From | 2026-09-18T21:04:58+00:00 |
| Valid Until | 2026-12-11T21:04:57+00:00 |
| TLS Protocol | Tls13 |
| Cipher Suite | TLS_AES_256_GCM_SHA384 |
| Signature Algorithm | sha256RSA |
| Validity Period | 83 days |
🛡️ Public Network Snapshot
| Origin ASN | AS15169 |
| Network Prefix | 64.233.180.0/24 |
| Route mapping | Found |
| HSTS | Not detected |
| CSP | Not detected |
| HTTP/2 | Enabled |
📅 Observation Timeline 🔄 Live
| First Seen | 2026-10-06 05:13:06 UTC |
| Last Seen | 2026-10-06 05:13:06 UTC |
| Profile Built | 2026-10-06 05:23:46 UTC |
| Data Freshness | Live |
| Signal Types | 9 |
| Total Observations | 9 |
🔍 9 signal types · 9 observations collected
This report is generated from 9+ 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 64.233.180.18
Is 64.233.180.18 malicious or safe?
64.233.180.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 is the hostname for 64.233.180.18?
The reverse DNS (PTR) record for 64.233.180.18 is on-in-f18.1e100.net. This hostname is forward-confirmed, meaning it resolves back to the same address.
What ports are open on 64.233.180.18?
Responsive ports observed on 64.233.180.18 include 80, 443. Port visibility reflects the most recent scan and may change as the host's configuration or firewall rules change.
🏘️ Related IP Addresses
Nearby addresses
64.233.180.1764.233.180.8164.233.180.8364.233.180.8464.233.180.9164.233.180.9264.233.180.9464.233.180.9564.233.180.10064.233.180.10164.233.180.10264.233.180.113
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.