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 (25y) +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)
- dont.work
- Forward-confirmed (FCrDNS)
- Not checked
- PTR TTL
- 3600 s
- Reverse DNS last checked
- 2026-09-19 05:19 UTC
- Forward DNS last checked
- 2026-09-19 05:19 UTC
Forward DNS records for dont.work
| Type | Value | Priority | TTL |
|---|---|---|---|
| A | 216.150.1.1 | — | 1800s |
| A | 216.150.1.129 | — | 172800s |
| A | 216.150.1.193 | — | 1800s |
| A | 216.150.1.65 | — | 1800s |
| A | 216.150.16.1 | — | 1800s |
| A | 216.150.16.129 | — | 172800s |
| A | 216.150.16.193 | — | 172800s |
| A | 216.150.16.65 | — | 172800s |
| A | 216.198.79.65 | — | 300s |
| A | 64.29.17.1 | — | 300s |
| MX | alt1.aspmx.l.google.com | 5 | — |
| MX | alt2.aspmx.l.google.com | 5 | — |
| MX | alt3.aspmx.l.google.com | 10 | — |
| MX | alt4.aspmx.l.google.com | 10 | — |
| MX | aspmx.l.google.com | 1 | — |
| NS | arnold.ns.cloudflare.com | — | 86400s |
| NS | mckinley.ns.cloudflare.com | — | 86400s |
| NS | ns1.vercel-dns.com | — | — |
| NS | ns2.vercel-dns.com | — | — |
| TXT | google-site-verification=UO3c0wz-c4lAVemmVCG0NXAn69Kz8r1lIuaTKy3V1q0 | — | — |
| TXT | v=DMARC1; p=none; rua=mailto:jaden@dont.work | — | — |
| TXT | v=spf1 include:_spf.google.com ~all | — | — |
| CAA | issue comodoca.com | 0 | 3600s |
| CAA | issue digicert.com; cansignhttpexchanges=yes | 0 | 3600s |
| CAA | issue letsencrypt.org | 0 | — |
| CAA | issue pki.goog | 0 | — |
| CAA | issue pki.goog; cansignhttpexchanges=yes | 0 | 3600s |
| CAA | issue sectigo.com | 0 | — |
| CAA | issue ssl.com | 0 | 3600s |
| CAA | issuewild comodoca.com | 0 | 3600s |
| CAA | issuewild digicert.com; cansignhttpexchanges=yes | 0 | 3600s |
| CAA | issuewild letsencrypt.org | 0 | 3600s |
| CAA | issuewild pki.goog; cansignhttpexchanges=yes | 0 | 3600s |
| CAA | issuewild ssl.com | 0 | 3600s |
Reverse & forward DNS collected by the WorldIP scanner fleet — FCrDNS confirms the PTR hostname resolves back to this IP.
Network Allocation for 80.85.141.176
- CIDR range
- 80.85.140.0/23
- IP range (int)
- 1,347,783,680 — 1,347,784,191
- Prefix length
- /23
- Organization
- NovoServe B.V.
- ASN
- AS204601
- ASN name
- NovoServe B.V.
- Location
- The Netherlands
- Coordinates
- 52.382400, 4.899500
- Accuracy radius
- 100 km
- Regional Internet Registry
- RIPE
- Allocated
- 2001-08-15
- Data source(s)
- maxmind_city, maxmind_asn, ipinfo_lite, maxmind_country
- Last updated
- 2026-07-07 06:21:43
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 80.85.141.176?
80.85.141.176 is allocated to NovoServe B.V. (AS204601), registered in The Netherlands.
Where is 80.85.141.176 located?
The geolocation for 80.85.141.176 maps to The Netherlands 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 80.85.141.176 on?
80.85.141.176 belongs to the 80.85.140.0/23 network block announced by AS204601. This range contains 512 addresses.
Does 80.85.141.176 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.
