176.118.212.214
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
- Not on any threat blocklist +5
- Has a reverse-DNS (PTR) record +5
- Established allocation (14y) +3
- Trust score 78 / 100
Experimental · trust-vectors model v1.2.1 — a transparent heuristic, not a definitive verdict. How it works →
DNS records
- Reverse DNS (PTR)
- kanzpark.ru
- Forward-confirmed (FCrDNS)
- Not checked
- PTR TTL
- 11000 s
- Reverse DNS last checked
- 2026-10-10 07:02 UTC
- Forward DNS last checked
- 2026-10-10 07:02 UTC
Forward DNS records for kanzpark.ru
| Type | Value | Priority | TTL |
|---|---|---|---|
| A | 185.215.4.38 | — | 172800s |
| MX | mx1.beget.com | 10 | — |
| MX | mx2.beget.com | 20 | — |
| NS | ns3-l2.nic.ru | — | — |
| NS | ns4-cloud.nic.ru | — | — |
| NS | ns4-l2.nic.ru | — | — |
| NS | ns8-cloud.nic.ru | — | — |
| NS | ns8-l2.nic.ru | — | — |
| TXT | _globalsign-domain-verification=1XOTCugxfL8ea8Me8_AmRy_2TOSYFP2WJr8cxLmEK7 | — | — |
| TXT | _globalsign-domain-verification=CRuMyJui6uNfxswXWwn8Gx09Pij6n-ViEs2uKT2_6j | — | — |
| TXT | _globalsign-domain-verification=FNuU_x8kPcYtCVn421j2CpJHrRg_QeUIPt0DGqklLH | — | — |
| TXT | _globalsign-domain-verification=MuLw1MILsqPJ0wHBVUGriR2MbjYHmFhsznaHWK2yk8 | — | — |
| TXT | _globalsign-domain-verification=UEM6AVY7DddQzzwnt7E-ZiXDBa6fuHyjv1Mt-zFTuL | — | — |
| TXT | _globalsign-domain-verification=UhPXiXFs2eL5yWuAX8gkn3qR3mcpsiR-yHdqnDodGn | — | — |
| TXT | _globalsign-domain-verification=a3ETFbfMmvBARtcwLyqrVE14qjifkDslpqN7xrEZMY | — | — |
| TXT | _globalsign-domain-verification=fX8SaOP2JL8sCMuoiqhEpbn4Wdx2KVamS4Qt3W-bot | — | — |
| TXT | _globalsign-domain-verification=llirkS53Tm4ljHEG57zN56-fK7AW82eNH1rDDurBW5 | — | — |
| TXT | _globalsign-domain-verification=qkQ4ELELgfzfolamP4tbDo7ObENANnTqhMXuPf2O6B | — | — |
| TXT | google-site-verification=OioicD61Tmwx3rM7OSXGCElsSPnL1OD4rmTdmxRqfqA | — | — |
| TXT | mailru-verification: 7f05077ffe971541 | — | — |
| TXT | v=DMARC1; p=none; rua=mailto:dmarc@kanzpark.ru; ruf=mailto:dmarc@kanzpark.ru | — | — |
| TXT | v=spf1 include:e3.kanzpark.ru include:353.ensend.ru include:spf.unisender.com include:beget.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-10-04 UTC0
issued.live saw no domain resolving to this IP in its latest weekly snapshot.
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.
- kanzpark.ru stable — Jun 12, 2026 → present 1 brief no-PTR dropout
Network Allocation for 176.118.212.214
- CIDR range
- 176.118.212.0/24
- IP range (int)
- 2,960,577,536 — 2,960,577,791
- Prefix length
- /24
- Organization
- Relyef Centr LLC
- ASN
- AS209873
- ASN name
- Relyef Centr LLC
- Location
- Ryazan, Ryazan Oblast, Russia
- Coordinates
- 54.616100, 39.737600
- Accuracy radius
- 20 km
- Postal code
- 390005
- Regional Internet Registry
- RIPE
- Allocated
- 2012-06-01
- Data source(s)
- maxmind_asn, ipinfo_lite, maxmind_city, maxmind_country
- Last updated
- 2026-06-09 06:05:37
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 176.118.212.214?
176.118.212.214 is allocated to Relyef Centr LLC (AS209873), registered in Ryazan, Russia.
Where is 176.118.212.214 located?
The geolocation for 176.118.212.214 maps to Ryazan, Russia 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 176.118.212.214 on?
176.118.212.214 belongs to the 176.118.212.0/24 network block announced by AS209873. This range contains 256 addresses.
Does 176.118.212.214 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.
