66.39.69.70
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 (26y) +6
- Not on any threat blocklist +5
- Has a reverse-DNS (PTR) record +5
- Trust score 81 / 100
Experimental · trust-vectors model v1.2.0 — a transparent heuristic, not a definitive verdict. How it works →
DNS records
- Reverse DNS (PTR)
- loder-plants.co.uk
- Forward-confirmed (FCrDNS)
- Not checked
- PTR TTL
- 7200 s
- Reverse DNS last checked
- 2026-09-18 06:38 UTC
Forward DNS records for loder-plants.co.uk
| Type | Value | Priority | TTL |
|---|---|---|---|
| A | 172.66.40.101 | — | 172800s |
| A | 172.66.43.155 | — | 172800s |
| AAAA | 2606:4700:3108::ac42:2865 | — | 172800s |
| AAAA | 2606:4700:3108::ac42:2b9b | — | 172800s |
| MX | mail2.g24.pair.com | 50 | — |
| NS | guy.ns.cloudflare.com | — | — |
| NS | megan.ns.cloudflare.com | — | — |
| TXT | google-site-verification=D3HHLJ4L_QwylLpXhcWLoBHardunKZ7mr-NeMmP9R_4 | — | — |
| TXT | google-site-verification=xU2582_ABPGsLtHb1VtDCYfGufmu6cXNn9Oipo1VXiA | — | — |
| TXT | v=DMARC1; p=reject; rua=mailto:chris@loder.co.uk | — | — |
| TXT | v=spf1 include:webmail.pair.com include:relay.pair.com include:pairlist.com a:www4.g24.pair.com a:mail2.g24.pair.com ~all | — | — |
| CAA | issue comodoca.com | 0 | — |
| CAA | issue digicert.com; cansignhttpexchanges=yes | 0 | — |
| CAA | issue letsencrypt.org | 0 | — |
| CAA | issue pki.goog; cansignhttpexchanges=yes | 0 | — |
| CAA | issue ssl.com | 0 | — |
| CAA | issuewild comodoca.com | 0 | — |
| CAA | issuewild digicert.com; cansignhttpexchanges=yes | 0 | — |
| CAA | issuewild letsencrypt.org | 0 | — |
| CAA | issuewild pki.goog; cansignhttpexchanges=yes | 0 | — |
| CAA | issuewild ssl.com | 0 | — |
Reverse & forward DNS collected by the WorldIP scanner fleet — FCrDNS confirms the PTR hostname resolves back to this IP.
Network Allocation for 66.39.69.70
- CIDR range
- 66.39.0.0/17
- IP range (int)
- 1,109,852,160 — 1,109,884,927
- Prefix length
- /17
- 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
- 2000-10-27
- Data source(s)
- maxmind_city, maxmind_country, maxmind_asn, ipinfo_lite
- Last updated
- 2026-09-17 05:21:54
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 66.39.69.70?
66.39.69.70 is allocated to pair Networks (AS7859), registered in Pittsburgh, United States.
Where is 66.39.69.70 located?
The geolocation for 66.39.69.70 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 66.39.69.70 on?
66.39.69.70 belongs to the 66.39.0.0/17 network block announced by AS7859. This range contains 32,768 addresses.
Does 66.39.69.70 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.
