Reputation · trust score
A transparent 0–100 signal. Every entity starts at a neutral baseline of 65; threat-intel blocklists, exposure, reverse-DNS, routing and allocation each adjust it up or down. Higher is more trustworthy.
- Baseline (neutral) 65
- Long-established allocation (20y) +6
- Not on any threat blocklist +5
- Has a reverse-DNS (PTR) record +5
- Enterprise allocation +4
- Trust score 85 / 100
Experimental · trust-vectors model v1.3.0 — a transparent heuristic, not a definitive verdict. How it works →
Exposure · open ports & services
Internet-facing services Shodan observed on this IP.
| Port | Service | Product |
|---|---|---|
| 53/tcp | dns-tcp | — |
| 53/udp | dns-udp | — |
| 80/tcp | http | nginx |
| 443/tcp | https | — |
| 443/udp | mdns | mDNS |
| 5353/udp | mdns | mDNS |
Exposure data via Shodan · last seen 2026-08-31.
DNS records
- Reverse DNS (PTR)
- dns.umbrella.com
- Forward-confirmed (FCrDNS)
- Not checked
- PTR TTL
- 1218 s
- Reverse DNS last checked
- 2026-10-27 06:35 UTC
Forward DNS records for dns.umbrella.com
| Type | Value | Priority | TTL |
|---|---|---|---|
| A | 208.67.220.220 | — | 2545s |
| A | 208.67.222.222 | — | 2545s |
| AAAA | 2620:119:35::35 | — | 2488s |
| AAAA | 2620:119:53::53 | — | 2488s |
Reverse & forward DNS collected by the WorldIP scanner fleet — FCrDNS confirms the PTR hostname resolves back to this IP.
Domains hosted
as of 2026-10-25 UTC190
Registrable domains (like example.com) with at least one name resolving to this IP — updated daily from issued.live's DNS data.
Domain data provided by issued.live — for full details visit https://issued.live/pricing
Reverse DNS history
How this IP's reverse DNS (PTR) has changed over time, from our scans.
This IP's reverse DNS changes frequently — the timeline below shows the most recent changes.
- dns.umbrella.com — Oct 27, 2026 → present
- resolver1.opendns.com — Oct 26, 2026 → Oct 27, 2026
- dns.sse.cisco.com — Oct 24, 2026 → Oct 26, 2026
- dns.umbrella.com — Oct 22, 2026 → Oct 24, 2026
- dns.opendns.com — Oct 20, 2026 → Oct 22, 2026
- dns.sse.cisco.com — Oct 19, 2026 → Oct 20, 2026
- dns.opendns.com — Oct 16, 2026 → Oct 19, 2026
- resolver1.opendns.com — Oct 13, 2026 → Oct 16, 2026
- dns.sse.cisco.com — Oct 11, 2026 → Oct 13, 2026
- resolver1.opendns.com — Oct 10, 2026 → Oct 11, 2026
- dns.sse.cisco.com — Oct 8, 2026 → Oct 10, 2026
- resolver1.opendns.com — Oct 7, 2026 → Oct 8, 2026
- dns.umbrella.com — Oct 7, 2026 → Oct 7, 2026
- dns.sse.cisco.com — Oct 6, 2026 → Oct 7, 2026
- resolver1.opendns.com — Oct 4, 2026 → Oct 6, 2026
- dns.sse.cisco.com — Oct 3, 2026 → Oct 4, 2026
- resolver1.opendns.com — Sep 30, 2026 → Oct 3, 2026
- dns.umbrella.com — Sep 29, 2026 → Sep 30, 2026
- resolver1.opendns.com — Sep 26, 2026 → Sep 29, 2026
- dns.umbrella.com — Sep 26, 2026 → Sep 26, 2026
- resolver1.opendns.com — Jun 12, 2026 → Sep 26, 2026
Network Allocation for 208.67.222.222
- CIDR range
- 208.67.220.0/22
- IP range (int)
- 3,494,108,160 — 3,494,109,183
- Prefix length
- /22
- Organization
- Cisco OpenDNS, LLC
- ASN
- AS36692
- ASN name
- Cisco OpenDNS, LLC
- Location
- United States
- Coordinates
- 37.751000, -97.822000
- Accuracy radius
- 1000 km
- Regional Internet Registry
- ARIN
- Allocated
- 2006-06-06
- Data source(s)
- maxmind_city, maxmind_asn, ipinfo_lite, maxmind_country
- Last updated
- 2026-10-26 08:49:13
BGP Routing
Live BGP anomalies →Origin AS announcing the most-specific prefix that covers this IP, observed across our RIPE RIS collectors.
Frequently Asked Questions
Who owns 208.67.222.222?
208.67.222.222 is allocated to Cisco OpenDNS, LLC (AS36692), registered in United States.
Where is 208.67.222.222 located?
The geolocation for 208.67.222.222 maps to United States based on MaxMind GeoLite2 data. Accuracy depends on the provider and may represent the ISP's regional hub rather than the exact endpoint.
What network is 208.67.222.222 on?
208.67.222.222 belongs to the 208.67.220.0/22 network block announced by AS36692. This range contains 1,024 addresses.
Does 208.67.222.222 have a reverse DNS record?
Reverse DNS (PTR) records are resolved live when you visit this page. If a PTR record exists, it appears in the Reverse DNS field above. PTR records map IP addresses back to hostnames and are commonly used for email authentication and network diagnostics.
Neighbors
Other addresses in the same /24.
