70.32.89.100
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 (18y) +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)
- lgcypower.com
- Forward-confirmed (FCrDNS)
- Not checked
- PTR TTL
- 3600 s
- Reverse DNS last checked
- 2026-11-05 17:40 UTC
Forward DNS records for lgcypower.com
| Type | Value | Priority | TTL |
|---|---|---|---|
| A | 70.32.89.100 | — | 172800s |
| MX | lgcypower-com.mail.protection.outlook.com | 0 | — |
| MX | ms79510736.msv1.invalid | 32767 | — |
| NS | ns17.domaincontrol.com | — | — |
| NS | ns18.domaincontrol.com | — | — |
| TXT | 8dl5sa2fsc7b3n087ms3hpl38g | — | — |
| TXT | apple-domain-verification=V2TdZDVIvBXDj5vT | — | — |
| TXT | canva-site-verification=aBeSWYF7qnyYXY4od26AHg | — | — |
| TXT | clickfunnels-domain-verification=jqOWwr | — | — |
| TXT | dqu9367kp0eppu8ipqc9774p82 | — | — |
| TXT | facebook-domain-verification=0blvjcstov98694p9uhihi5bvijx41 | — | — |
| TXT | facebook-domain-verification=h8i2y2l3dxfhryd0zwfeswr1xclgpy | — | — |
| TXT | google-site-verification=0Ww1yajfNu0paPCN2EaBdBDGMnNAP2xUAlhpE7caXB0 | — | — |
| TXT | google-site-verification=rkzH7ZMalggC8V0IbKyffcvCGgkQm5EUS9YUprW6Je8 | — | — |
| TXT | lpdtjbni7s7r9vm82t7n2fcilk | — | — |
| TXT | s9575mt0nbi1l4eid22dknbhur | — | — |
| TXT | v=DMARC1; p=quarantine; rua=mailto:dmarc@lgcypower.com; ruf=mailto:dmarc@lgcypower.com; fo=1;sp=quarantine | — | — |
| TXT | v=spf1 mx ip4:70.32.89.100 include:spf.protection.outlook.com include:_spf.salesforce.com include:sent-via.netsuite.com include:amazonses.com ~all | — | — |
Reverse & forward DNS collected by the WorldIP scanner fleet — FCrDNS confirms the PTR hostname resolves back to this IP.
Domains hosted
as of 2026-11-05 UTC7
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.
- lgcypower.com stable — Jun 12, 2026 → present 1 brief no-PTR dropout
Network Allocation for 70.32.89.100
- CIDR range
- 70.32.80.0/20
- IP range (int)
- 1,176,522,752 — 1,176,526,847
- Prefix length
- /20
- Organization
- GoDaddy.com, LLC
- ASN
- AS398101
- ASN name
- GoDaddy.com, LLC
- Location
- Ashburn, Virginia, United States
- Coordinates
- 39.046900, -77.490300
- Accuracy radius
- 20 km
- Postal code
- 20149
- Regional Internet Registry
- ARIN
- Allocated
- 2008-06-26
- Data source(s)
- maxmind_city, maxmind_asn, ipinfo_lite, maxmind_country
- Last updated
- 2026-11-03 08:44:07
BGP Routing
Live BGP anomalies →Origin AS announcing the most-specific prefix that covers this IP, observed across our RIPE RIS collectors.
RIR Ownership History
Atom feed ⇲Allocation changes captured from regional internet registry (RIR) delegation files, re-imported every six hours, for ranges that have contained this IP.
| Date | Event | From | To |
|---|---|---|---|
| 2026-05-10 | New Allocation | — | US |
See the full history for 70.32.0.0/16.
Frequently Asked Questions
Who owns 70.32.89.100?
70.32.89.100 is allocated to GoDaddy.com, LLC (AS398101), registered in Ashburn, United States.
Where is 70.32.89.100 located?
The geolocation for 70.32.89.100 maps to Ashburn, 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 70.32.89.100 on?
70.32.89.100 belongs to the 70.32.80.0/20 network block announced by AS398101. This range contains 4,096 addresses.
Does 70.32.89.100 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.
