62.168.38.130
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 (29y) +6
- Not on any threat blocklist +5
- Has a reverse-DNS (PTR) record +5
- Mobile allocation +2
- Trust score 83 / 100
Experimental · trust-vectors model v1.2.1 — a transparent heuristic, not a definitive verdict. How it works →
DNS records
- Reverse DNS (PTR)
- ami.cz
- Forward-confirmed (FCrDNS)
- Not checked
- PTR TTL
- 21600 s
- Reverse DNS last checked
- 2026-10-03 21:19 UTC
- Forward DNS last checked
- 2026-10-03 21:19 UTC
Forward DNS records for ami.cz
| Type | Value | Priority | TTL |
|---|---|---|---|
| A | 37.46.80.177 | — | 172800s |
| MX | ami-cz.mail.protection.outlook.com | 10 | — |
| NS | ns.adminit.cz | — | — |
| NS | ns.iinfo.cz | — | — |
| NS | ns6.adminit.cz | — | — |
| TXT | _88s04ntm2gfn3r2x7091tfh3rwzpnio | — | — |
| TXT | anthropic-domain-verification-90sxps=1qlbAsFkEgsgBWkfvW2MpOnyY | — | — |
| TXT | atlassian-domain-verification=C9FVGu2AKhn6qLXZUC3GJ4PsGKtLbYgNwXukSyYOoh5SDcRaGjcposT07ABttqYL | — | — |
| TXT | cloudflare_dashboard_sso=59525d1834a3cf14fe2a20c50ae45472 | — | — |
| TXT | google-site-verification=fjKGn5T63tnBchuLNmVUTee1Uye20aeWq2vHKaYe4ZI | — | — |
| TXT | google-site-verification=n4KOzsq91aZjbWsAnWpTPj8akh5-HiFiw3wRvYOkzM8 | — | — |
| TXT | v=DMARC1; p=quarantine; pct=100; rua=mailto:dmarc-rua@ami.cz; ruf=mailto:dmarc-ruf@ami.cz; fo=1 | — | — |
| TXT | v=spf1 ip4:81.31.34.114 ip4:81.31.37.26 ip4:89.185.246.202 ip4:89.185.246.210 include:spf.protection.outlook.com include:spf-de.emailsignatures365.com -all | — | — |
| CAA | issuewild digicert.com | 0 | — |
Reverse & forward DNS collected by the WorldIP scanner fleet — FCrDNS confirms the PTR hostname resolves back to this IP.
Reverse DNS history
How this IP's reverse DNS (PTR) has changed over time, from our scans.
This IP's reverse DNS changes frequently — the timeline below shows the most recent changes.
- ami.cz — Oct 3, 2026 → present
- greenhorn.ami.cz — Oct 3, 2026 → Oct 3, 2026
- ami.cz — Oct 2, 2026 → Oct 3, 2026
- greenhorn.ami.cz — Oct 1, 2026 → Oct 2, 2026
- ami.cz — Sep 29, 2026 → Oct 1, 2026
- greenhorn.ami.cz — Sep 28, 2026 → Sep 29, 2026
- ami.cz — Sep 26, 2026 → Sep 28, 2026
- greenhorn.ami.cz — Aug 24, 2026 → Sep 26, 2026
- ami.cz — Aug 18, 2026 → Aug 24, 2026
- greenhorn.ami.cz — Jul 4, 2026 → Aug 18, 2026
- ami.cz — Jun 26, 2026 → Jul 4, 2026
- greenhorn.ami.cz — Jun 13, 2026 → Jun 26, 2026
- ami.cz — Jun 11, 2026 → Jun 13, 2026
- greenhorn.ami.cz — Jun 3, 2026 → Jun 11, 2026
- ami.cz — Jun 3, 2026 → Jun 3, 2026
- greenhorn.ami.cz — Jun 3, 2026 → Jun 3, 2026
- ami.cz — Jun 1, 2026 → Jun 3, 2026
- greenhorn.ami.cz — Jun 1, 2026 → Jun 1, 2026
- ami.cz — Jun 1, 2026 → Jun 1, 2026
Network Allocation for 62.168.38.130
- CIDR range
- 62.168.32.0/20
- IP range (int)
- 1,051,205,632 — 1,051,209,727
- Prefix length
- /20
- Organization
- T-Mobile Czech Republic a.s.
- ASN
- AS13036
- ASN name
- T-Mobile Czech Republic a.s.
- Location
- Prague, Prague, Czechia
- Coordinates
- 50.111300, 14.406300
- Accuracy radius
- 50 km
- Postal code
- 170 00
- Regional Internet Registry
- RIPE
- Allocated
- 1997-05-07
- Data source(s)
- maxmind_city, maxmind_country, maxmind_asn, ipinfo_lite
- Last updated
- 2026-10-03 05:21:29
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 62.168.38.130?
62.168.38.130 is allocated to T-Mobile Czech Republic a.s. (AS13036), registered in Prague, Czechia.
Where is 62.168.38.130 located?
The geolocation for 62.168.38.130 maps to Prague, Czechia 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 62.168.38.130 on?
62.168.38.130 belongs to the 62.168.32.0/20 network block announced by AS13036. This range contains 4,096 addresses.
Does 62.168.38.130 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.
