51.81.34.188
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
- Datacenter — common VPN/proxy host −6
- Not on any threat blocklist +5
- Has a reverse-DNS (PTR) record +5
- Trust score 69 / 100
Experimental · trust-vectors model v1.1.0 — a transparent heuristic, not a definitive verdict. How it works →
DNS records
- Reverse DNS (PTR)
- certified-parts.com
- Forward-confirmed (FCrDNS)
- ✗ Mismatch
- PTR TTL
- 86400 s
- Reverse DNS last checked
- 2026-07-18 06:47 UTC
- Forward DNS last checked
- 2026-07-18 06:47 UTC
Forward DNS records for certified-parts.com
| Type | Value | Priority | TTL |
|---|---|---|---|
| A | 104.26.12.75 | — | 172800s |
| A | 104.26.13.75 | — | 172800s |
| A | 172.67.71.1 | — | 172800s |
| AAAA | 2606:4700:20::681a:c4b | — | 172800s |
| AAAA | 2606:4700:20::681a:d4b | — | 172800s |
| AAAA | 2606:4700:20::ac43:4701 | — | 172800s |
| 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 | donna.ns.cloudflare.com | — | — |
| NS | nero.ns.cloudflare.com | — | — |
| TXT | google-site-verification=ua93xdBUOw80vIYNCYeyc2ZSoX4BF1Jm00ydXhd6A9Y | — | — |
| TXT | stripe-verification=66752fe0f1ee02549b6fbbb953114dec8b29cd6aa72c36946f464de94e9d42d2 | — | — |
| TXT | v=DMARC1; p=quarantine; sp=quarantine; pct=100; adkim=r; aspf=r; fo=0; rua=mailto:8165992a27b942c7986c63b60b3bed69@dmarc-reports.cloudflare.net,mailto:dmarc@certified-parts.com,mailto:15834bfe@mxtoolbox.dmarc-report.com; ruf=mailto:15834bfe@forensics.dmarc-report.com | — | — |
| TXT | v=spf1 include:_spf.google.com include:amazonses.com a:shipstation.com a:cp-webstore.p.tawk.email ip4:51.81.34.188 ~all | — | — |
| CAA | iodef mailto:security@certified-parts.com | 0 | — |
| 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 | issuemail ; | 0 | — |
| CAA | issuevmc ; | 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 51.81.34.188
- CIDR range
- 51.81.34.0/24
- IP range (int)
- 860,955,136 — 860,955,391
- Prefix length
- /24
- Organization
- OVH SAS
- ASN
- AS16276
- ASN name
- OVH SAS
- Location
- United States
- Coordinates
- 37.751000, -97.822000
- Accuracy radius
- 1000 km
- Regional Internet Registry
- RIPE
- Allocated
- 2019-03-11
- Data source(s)
- maxmind_city, maxmind_country, maxmind_asn, ipinfo_lite
- Last updated
- 2026-07-05 06:19:09
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 weekly from regional internet registry (RIR) delegation files for ranges that have contained this IP.
| Date | Event | From | To |
|---|---|---|---|
| 2026-05-10 | RIR Transfer | ripe | arin |
See the full history for 51.81.0.0/16.
Frequently Asked Questions
Who owns 51.81.34.188?
51.81.34.188 is allocated to OVH SAS (AS16276), registered in United States.
Where is 51.81.34.188 located?
The geolocation for 51.81.34.188 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 51.81.34.188 on?
51.81.34.188 belongs to the 51.81.34.0/24 network block announced by AS16276. This range contains 256 addresses.
Does 51.81.34.188 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.
