135.18.128.216
135.18.128.216 is an IPv4 address operated by Divya Quamara (AS8075), geolocated to Virginia, United States. It belongs to datacenter or hosting infrastructure. As of November 3, 2026, IPDebrief rates it High Risk (70/100); no anonymizing service was detected.
🏢 Ownership & Registration
| Organization | Divya Quamara |
| ASN | AS8075 |
| Network Name | cloud |
| CIDR Block | 135.18.128.0/17 |
| RIR | ARIN |
| Country | 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 Hygiene
| Hygiene Score | 40% (Fair) |
| SPF | Present |
| DMARC | Present |
| FCrDNS | Not verified |
| DNSSEC | Not signed |
| CAA | Not configured |
☁️ Network Classification
| Infrastructure | Infrastructure / Datacenter |
| Service Purpose | Web Server |
| Network Tier | Hosting — Infrastructure provider without advanced routing |
🔌 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
| SANs | fe2.update.microsoft.com |
| Valid From | 2026-01-22T20:47:39+00:00 |
| Valid Until | 2027-01-22T20:47:39+00:00 |
| TLS Protocol | Tls13 |
| Cipher Suite | TLS_AES_256_GCM_SHA384 |
| Signature Algorithm | sha256RSA |
| Validity Period | 365 days |
🛡️ Public Network Snapshot
| Origin ASN | AS8075 |
| Network Prefix | 135.18.0.0/16 |
| Route mapping | Found |
| Certificates in transparency logs | 0 certificates |
| HSTS | Not detected |
| CSP | Not detected |
| HTTP/2 | Enabled |
🎯 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 | 35% | 2 | 4 |
| ownership | 27% | 2 | 3 |
| reputation | 28% | 1 | 3 |
| geolocation | 27% | 2 | 3 |
| Overall | 27% | 10 | 18 |
| Data Coherence | Mostly Consistent (80%) — 1 contradiction(s) |
| Attribution | Low (35%) |
| OwnershipFCrDNSGeo ConsensusGeo PlausibleIRR MatchRPKI Valid |
📅 Observation Timeline 🔄 Live
| First Seen | 2026-10-21 08:25:31 UTC |
| Last Seen | 2026-11-03 11:43:42 UTC |
| Profile Built | 2026-11-03 12:25:40 UTC |
| Data Freshness | Live |
| Signal Types | 23 |
| Total Observations | 30 |
Full dossier details are available via our API.
❓ Frequently Asked Questions About 135.18.128.216
Who owns the IP address 135.18.128.216?
135.18.128.216 is registered to Divya Quamara. The address falls within the 135.18.128.0/17 network block. Registration is held at ARIN.
Where is 135.18.128.216 located?
Geolocation data places 135.18.128.216 in Virginia, VA, United States. The local time zone is America/New_York. IP geolocation is approximate and indicates the network's registered or routed location rather than a precise physical address.
Is 135.18.128.216 malicious or safe?
135.18.128.216 currently carries a high risk assessment, meaning indicators associated with malicious or abusive activity have been observed. This assessment is generated from continuously collected signals and can change over time.
What ports are open on 135.18.128.216?
Responsive ports observed on 135.18.128.216 include 80, 443. Port visibility reflects the most recent scan and may change as the host's configuration or firewall rules change.
Is 135.18.128.216 a VPN, proxy, or data center address?
135.18.128.216 is classified as cloud infrastructure and hosting infrastructure based on network ownership and behavioural analysis.