172.105.66.93
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 (11y) +3
- Trust score 78 / 100
Experimental · trust-vectors model v1.2.0 — a transparent heuristic, not a definitive verdict. How it works →
DNS records
- Reverse DNS (PTR)
- kron.no
- Forward-confirmed (FCrDNS)
- Not checked
- PTR TTL
- 300 s
- Reverse DNS last checked
- 2026-09-19 16:03 UTC
- Forward DNS last checked
- 2026-09-19 14:05 UTC
Forward DNS records for kron.no
| Type | Value | Priority | TTL |
|---|---|---|---|
| A | 35.227.251.236 | — | 172800s |
| MX | mxa-0028d802.gslb.pphosted.com | 10 | — |
| MX | mxb-0028d802.gslb.pphosted.com | 10 | — |
| NS | ns1-06.azure-dns.com | — | — |
| NS | ns2-06.azure-dns.net | — | — |
| NS | ns3-06.azure-dns.org | — | — |
| NS | ns4-06.azure-dns.info | — | — |
| TXT | 1password-site-verification=L6ZASKTE7VB4RFXCO2OEMACDKI | — | — |
| TXT | MS=ms49648126 | — | — |
| TXT | MS=ms84400851 | — | — |
| TXT | apple-domain-verification=TQ3vdNeuF5h0kebL | — | — |
| TXT | atlassian-domain-verification=v2BF5p7FUXxcrY3C9ysTBilol2nXQkFsO91UawI86ZtBHQNx/pHLBZKesEr5YHtN | — | — |
| TXT | facebook-domain-verification=ednagkyy1wxt8518oukyf0scwfb1no | — | — |
| TXT | figma-domain-verification=5942a544435e8e594710853997217a7942726c3ac44f73d2852d44f5487e47df-1712752933 | — | — |
| TXT | google-gws-recovery-domain-verification=72899359 | — | — |
| TXT | google-site-verification=58wqzLpvvptRuC1VEr0hUiCZF7QlS0TVAi90Xj05zwA | — | — |
| TXT | google-site-verification=HmCDIMi3-vKkjusQSi5EdVXJ7xMD7NwHJbnkDmKslJg | — | — |
| TXT | google-site-verification=_OvnTUY9Et3cuCPlaiTBGoatBllvRKVpHC5_d3ijAx4 | — | — |
| TXT | google-site-verification=bU84KAx9ZVd65FAre9WsC1AF6wPFcrqhqMrTEGtcnGg | — | — |
| TXT | google-site-verification=wfF-x82Ipt17ATbyXmlz8AN-gq47k4tzx2rf4DTHPfc | — | — |
| TXT | v=DMARC1; p=reject;rua=mailto:dmarc_rua@emaildefense.proofpoint.com;ruf=mailto:dmarc_ruf@emaildefense.proofpoint.com | — | — |
| TXT | v=spf1 a:prod.kron.no a:kron.no a:mail.kron.no include:spf-0028d802.pphosted.com include:spf.protection.outlook.com -all | — | — |
| CAA | issue letsencrypt.org | 128 | — |
Reverse & forward DNS collected by the WorldIP scanner fleet — FCrDNS confirms the PTR hostname resolves back to this IP.
Network Allocation for 172.105.66.93
- CIDR range
- 172.105.64.0/21
- IP range (int)
- 2,892,578,816 — 2,892,580,863
- Prefix length
- /21
- Organization
- Akamai Connected Cloud
- ASN
- AS63949
- ASN name
- Akamai Connected Cloud
- Location
- Frankfurt am Main, Hesse, Germany
- Coordinates
- 50.116900, 8.683700
- Accuracy radius
- 20 km
- Postal code
- 60313
- Regional Internet Registry
- ARIN
- Allocated
- 2015-06-19
- Data source(s)
- maxmind_city, maxmind_country, ipinfo_lite, maxmind_asn
- Last updated
- 2026-09-18 05:24:51
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 | New Allocation | — | US |
See the full history for 172.105.0.0/17.
Frequently Asked Questions
Who owns 172.105.66.93?
172.105.66.93 is allocated to Akamai Connected Cloud (AS63949), registered in Frankfurt am Main, Germany.
Where is 172.105.66.93 located?
The geolocation for 172.105.66.93 maps to Frankfurt am Main, 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 172.105.66.93 on?
172.105.66.93 belongs to the 172.105.64.0/21 network block announced by AS63949. This range contains 2,048 addresses.
Does 172.105.66.93 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.
