138.201.220.53
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
- Active-threat / abuse risk −17
- Long-established allocation (36y) +6
- Not on any threat blocklist +5
- Has a reverse-DNS (PTR) record +5
- Trust score 64 / 100
Experimental · trust-vectors model v1.2.0 — a transparent heuristic, not a definitive verdict. How it works →
DNS records
- Reverse DNS (PTR)
- kmbs.ua
- Forward-confirmed (FCrDNS)
- Not checked
- PTR TTL
- 86400 s
- Reverse DNS last checked
- 2026-09-24 07:28 UTC
- Forward DNS last checked
- 2026-09-24 07:28 UTC
Forward DNS records for kmbs.ua
| Type | Value | Priority | TTL |
|---|---|---|---|
| A | 188.114.96.11 | — | 172800s |
| A | 188.114.97.11 | — | 172800s |
| AAAA | 2606:4700:20::681a:85c | — | 172800s |
| AAAA | 2606:4700:20::681a:95c | — | 172800s |
| AAAA | 2606:4700:20::ac43:487e | — | 172800s |
| MX | kmbs-ua.mail.protection.outlook.com | 0 | — |
| NS | jakub.ns.cloudflare.com | — | — |
| NS | megan.ns.cloudflare.com | — | — |
| TXT | MS=ms63231099 | — | — |
| TXT | esputnik-verification=RVNQX0RWS19WMQAAZf0AAAGNofOWFavwk56wL2iq | — | — |
| TXT | facebook-domain-verification=8vu8ygwhcc6dn3feenxvlu12mxj7f5 | — | — |
| TXT | google-site-verification=7iCIahVqKg3tXTe82wAQdoWkw19BKfUhkDzBVa0drqc | — | — |
| TXT | google-site-verification=ZWp9CzBp7fNllEX9fvJKEWBwXcd0OIn0Nt96xUvebhM | — | — |
| TXT | google-site-verification=cOkIl9-im7GFRMRDLDPwmmKNbtlGxri8-tv72qoIZA8 | — | — |
| TXT | google-site-verification=iNKxFdCEyoMAFmRqOFwZni2EqO6Ne_jx79dh8ZF3a5g | — | — |
| TXT | openai-domain-verification=dv-8xkj8ODrta6HSpzWnxsieAhG | — | — |
| TXT | perplexity-ai-domain-verification-75fvvw=lZ5wXD4GTTb2UOGQR1iBpbrne | — | — |
| TXT | v=BIMI1; l=https://kmbs.ua/bundle/img/default/layout/logo_primary_grey.svg; a=; | — | — |
| TXT | v=DMARC1; p=none; rua=mailto:85697f301f9d49649a6ec9ef55236d32@dmarc-reports.cloudflare.net | — | — |
| TXT | v=DMARC1; p=none | — | — |
| TXT | v=DMARC1; p=none; | — | — |
| TXT | v=spf1 include:spf.protection.outlook.com include:one.zoho.com include:servers.mcsv.net include:spf2.esputnik.com ~all | — | — |
| TXT | zoho-verification=zb39487973.zmverify.zoho.com | — | — |
Reverse & forward DNS collected by the WorldIP scanner fleet — FCrDNS confirms the PTR hostname resolves back to this IP.
Network Allocation for 138.201.220.53
- CIDR range
- 138.201.216.0/21
- IP range (int)
- 2,328,483,840 — 2,328,485,887
- Prefix length
- /21
- Organization
- Hetzner Online GmbH
- ASN
- AS24940
- ASN name
- Hetzner Online GmbH
- Location
- Falkenstein, Saxony, Germany
- Coordinates
- 50.477700, 12.364900
- Accuracy radius
- 20 km
- Postal code
- 08223
- Regional Internet Registry
- RIPE
- Allocated
- 1990-05-23
- Data source(s)
- maxmind_city, maxmind_asn, ipinfo_lite, maxmind_country
- Last updated
- 2026-09-24 05:24:13
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 | arin | ripe |
See the full history for 138.200.0.0/15.
Frequently Asked Questions
Who owns 138.201.220.53?
138.201.220.53 is allocated to Hetzner Online GmbH (AS24940), registered in Falkenstein, Germany.
Where is 138.201.220.53 located?
The geolocation for 138.201.220.53 maps to Falkenstein, Germany 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 138.201.220.53 on?
138.201.220.53 belongs to the 138.201.216.0/21 network block announced by AS24940. This range contains 2,048 addresses.
Does 138.201.220.53 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.
