80.97.124.105
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 (25y) +6
- Not on any threat blocklist +5
- Has a reverse-DNS (PTR) record +5
- Trust score 81 / 100
Experimental · trust-vectors model v1.2.0 — a transparent heuristic, not a definitive verdict. How it works →
DNS records
- Reverse DNS (PTR)
- turbo.com
- Forward-confirmed (FCrDNS)
- Not checked
- PTR TTL
- 7200 s
- Reverse DNS last checked
- 2026-09-19 08:27 UTC
- Forward DNS last checked
- 2026-09-19 08:27 UTC
Forward DNS records for turbo.com
| Type | Value | Priority | TTL |
|---|---|---|---|
| A | 104.81.130.250 | — | 171907s |
| A | 104.85.55.37 | — | 172800s |
| A | 104.94.65.249 | — | 20s |
| A | 184.25.219.63 | — | 172800s |
| A | 23.12.12.92 | — | 20s |
| A | 23.203.75.250 | — | 172800s |
| A | 23.36.208.30 | — | 172800s |
| A | 23.52.198.36 | — | 20s |
| AAAA | 2600:1413:5000:186::901 | — | 172800s |
| AAAA | 2600:1413:5000:18d::901 | — | 172800s |
| AAAA | 2600:1413:5000:a81::901 | — | 172800s |
| AAAA | 2600:1413:5000:a8b::901 | — | 172800s |
| AAAA | 2a02:26f0:2b80:986::901 | — | 172800s |
| AAAA | 2a02:26f0:2b80:98d::901 | — | 172800s |
| AAAA | 2a02:26f0:3780:982::901 | — | 171907s |
| AAAA | 2a02:26f0:3780:996::901 | — | 171907s |
| AAAA | 2a02:26f0:4700:196::901 | — | 172800s |
| AAAA | 2a02:26f0:4700:198::901 | — | 172800s |
| AAAA | 2a02:26f0:480:59b::901 | — | 172800s |
| AAAA | 2a02:26f0:480:5a1::901 | — | 172800s |
| AAAA | 2a02:26f0:480:5a2::901 | — | 172800s |
| AAAA | 2a02:26f0:e300:2a9::901 | — | 172800s |
| AAAA | 2a02:26f0:e300:2ae::901 | — | 172800s |
| NS | a1-182.akam.net | — | — |
| NS | a11-64.akam.net | — | — |
| NS | a18-64.akam.net | — | — |
| NS | a24-67.akam.net | — | — |
| NS | a6-66.akam.net | — | — |
| NS | a7-66.akam.net | — | — |
| NS | dns1.p01.nsone.net | — | — |
| NS | dns2.p01.nsone.net | — | — |
| NS | dns3.p01.nsone.net | — | — |
| NS | dns4.p01.nsone.net | — | — |
| TXT | v=DMARC1; p=reject; rua=mailto:dmarc_rua@emaildefense.proofpoint.com; ruf=mailto:dmarc_ruf@emaildefense.proofpoint.com;fo=1 | — | — |
| CAA | iodef mailto:Tech-PINetworkServiceOperations@intuit.com | 0 | — |
| CAA | issue amazon.com | 0 | — |
| CAA | issue digicert.com | 0 | — |
Reverse & forward DNS collected by the WorldIP scanner fleet — FCrDNS confirms the PTR hostname resolves back to this IP.
Network Allocation for 80.97.124.105
- CIDR range
- 80.97.124.0/24
- IP range (int)
- 1,348,566,016 — 1,348,566,271
- Prefix length
- /24
- Organization
- Alexhost Srl
- ASN
- AS200019
- ASN name
- Alexhost Srl
- Location
- Chisinau, Chi In U Municipality, Moldova
- Coordinates
- 47.004200, 28.857400
- Accuracy radius
- 20 km
- Postal code
- MD-2000
- Regional Internet Registry
- RIPE
- Allocated
- 2001-07-05
- Data source(s)
- maxmind_city, maxmind_country, maxmind_asn, ipinfo_lite
- Last updated
- 2026-09-18 05:22:55
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 | — | RO |
See the full history for 80.97.112.0/20.
Frequently Asked Questions
Who owns 80.97.124.105?
80.97.124.105 is allocated to Alexhost Srl (AS200019), registered in Chisinau, Moldova.
Where is 80.97.124.105 located?
The geolocation for 80.97.124.105 maps to Chisinau, Moldova 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 80.97.124.105 on?
80.97.124.105 belongs to the 80.97.124.0/24 network block announced by AS200019. This range contains 256 addresses.
Does 80.97.124.105 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.
