216.106.176.240
216.106.176.240 is an IPv4 address, with approximate network location Ashburn, United States. Its reverse DNS name is 240-176-106-216.clients.gthost.com. As of November 12, 2026, IPDebrief rates it Low Risk (0/100); no anonymizing service was detected.
🏢 Ownership & Registration
| Registered holder | Unknown |
| ASN | — |
| Network Name | — |
| CIDR Block | — |
| RIR | — |
| Network registration country | — |
| Abuse Contact | — |
🌐 DNS Intelligence
| PTR | 240-176-106-216.clients.gthost.com |
| Forward Confirmed | No — PTR hostname does not resolve back to this IP (weak signal) |
| Forward Hostnames | 240-176-106-216.clients.gthost.com |
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.
| spf | Not checked |
| dmarc | Not checked |
| fcrDns | Not checked |
| dnssec | Not checked |
| caa | 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 | — |
| 22 | ssh | tcp | Banner detected |
| Closed Ports | 25, 3389, 8080, 8443 (3 open / 7 scanned) | ||
| Server | — |
| HTTP Title | — |
🔐 TLS Certificate
| SANs | *.ad-teknexchange.comad-teknexchange.com |
| Valid From | 2026-09-04T10:54:32+00:00 |
| Valid Until | 2027-03-21T11:00:09+00:00 |
| TLS Protocol | Tls13 |
| Cipher Suite | TLS_CHACHA20_POLY1305_SHA256 |
| Signature Algorithm | sha256RSA |
| Validity Period | 198 days |
🛡️ Public Network Snapshot
| Origin ASN | AS63023 |
| Network Prefix | 216.106.176.0/24 |
| Route mapping | Found |
| 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 | 25% | 1 | 1 |
| routing | 25% | 1 | 1 |
| services | 0% | 0 | 0 |
| ownership | 0% | 0 | 0 |
| reputation | 0% | 0 | 0 |
| geolocation | 35% | 2 | 2 |
| Overall | 14% | 4 | 4 |
| Data Coherence | Consistent (100%) |
| Attribution | Low (30%) |
| OwnershipFCrDNSGeo ConsensusGeo PlausibleIRR MatchRPKI Valid |
📅 Observation Timeline 🔄 Aging
| First Seen | 2026-10-20 22:25:35 UTC |
| Last Seen | 2026-11-01 15:48:47 UTC |
| Profile Built | 2026-11-12 14:31:53 UTC |
| Data Freshness | Aging |
| Signal Types | 14 |
| Total Observations | 14 |
Full dossier details are available via our API.
❓ Frequently Asked Questions About 216.106.176.240
Where is 216.106.176.240 located?
Geolocation data places 216.106.176.240 in Ashburn, VA, United States. The local time zone is America/New_York. IP geolocation is approximate, not a precise physical address. Registration country and certificate organization addresses do not establish service location.
Is 216.106.176.240 malicious or safe?
216.106.176.240 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 216.106.176.240?
The reverse DNS (PTR) record for 216.106.176.240 is 240-176-106-216.clients.gthost.com. This hostname is not forward-confirmed, so it should be treated as a weak signal.
What ports are open on 216.106.176.240?
Responsive ports observed on 216.106.176.240 include 80, 443, 22. Port visibility reflects the most recent scan and may change as the host's configuration or firewall rules change.