209.68.38.182
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 (29y) +6
- Not on any threat blocklist +5
- Has a reverse-DNS (PTR) record +5
- Trust score 81 / 100
Experimental · trust-vectors model v1.3.0 — a transparent heuristic, not a definitive verdict. How it works →
DNS records
- Reverse DNS (PTR)
- woexchange.com
- Forward-confirmed (FCrDNS)
- Not checked
- PTR TTL
- 7200 s
- Reverse DNS last checked
- 2026-10-27 11:22 UTC
Forward DNS records for woexchange.com
| Type | Value | Priority | TTL |
|---|---|---|---|
| A | 209.68.38.182 | — | 300s |
| MX | mailwash14.pair.com | 50 | — |
| NS | ns-1175.awsdns-18.org | — | — |
| NS | ns-1934.awsdns-49.co.uk | — | — |
| NS | ns-228.awsdns-28.com | — | — |
| NS | ns-608.awsdns-12.net | — | — |
| TXT | 77f64camif1t3eb9lubgt6s6bl | — | — |
| TXT | 7bu39ao3lv6647n6ov4upcv44h | — | — |
| TXT | 7qu5k81sea3s3q046rhguvei7l | — | — |
| TXT | 9j0e0ljb7haj1562jnno6rs2r5 | — | — |
| TXT | cp74tekp007mc3c9fvgtdvog02 | — | — |
| TXT | e1rrnjvagl4pfmfku4o3satu7t | — | — |
| TXT | google-site-verification=Zi6owm6qIkGEHjrK0aKwcHgmmp0PRn2MLJTpHz2NiBY | — | — |
| TXT | i57rfbonpug7lqd33kbfc6c9uc | — | — |
| TXT | ib0l1fiftn4u3es1qekbsamjtf | — | — |
| TXT | krjm14703e804oeghalg1cllb6 | — | — |
| TXT | l0i9ce8r6on44p0qh43s7eecgm | — | — |
| TXT | sm2gudb1t2ue3i4o1numvqrb6t | — | — |
| TXT | v=spf1 include:us._netblocks.mimecast.com ip4:66.171.202.1 ip4:192.157.39.1 ip4:34.216.228.115 -all | — | — |
| TXT | vlcdv2q2vh5iqma2f1qtco1l63 | — | — |
| CAA | issue amazon.com | 0 | — |
| CAA | issue amazonaws.com | 0 | — |
| CAA | issue amazontrust.com | 0 | — |
| CAA | issue awstrust.com | 0 | — |
| CAA | issue godaddy.com | 0 | — |
| CAA | issue letsencrypt.org | 0 | — |
| CAA | issue pki.goog | 0 | — |
| CAA | issue sectigo.com | 0 | — |
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 UTC1
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
Network Allocation for 209.68.38.182
- CIDR range
- 209.68.0.0/18
- IP range (int)
- 3,510,894,592 — 3,510,910,975
- Prefix length
- /18
- Organization
- pair Networks
- ASN
- AS7859
- ASN name
- pair Networks
- Location
- Pittsburgh, Pennsylvania, United States
- Coordinates
- 40.442200, -79.992700
- Accuracy radius
- 20 km
- Postal code
- 15212
- Regional Internet Registry
- ARIN
- Allocated
- 1997-04-15
- Data source(s)
- maxmind_city, maxmind_asn, ipinfo_lite, maxmind_country
- Last updated
- 2026-10-27 08:49:53
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 209.68.38.182?
209.68.38.182 is allocated to pair Networks (AS7859), registered in Pittsburgh, United States.
Where is 209.68.38.182 located?
The geolocation for 209.68.38.182 maps to Pittsburgh, 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 209.68.38.182 on?
209.68.38.182 belongs to the 209.68.0.0/18 network block announced by AS7859. This range contains 16,384 addresses.
Does 209.68.38.182 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.
