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
- Recently allocated (1y) −3
- Trust score 72 / 100
Experimental · trust-vectors model v1.1.0 — a transparent heuristic, not a definitive verdict. How it works →
DNS records
- Reverse DNS (PTR)
- delta.blue
- Forward-confirmed (FCrDNS)
- Not checked
- PTR TTL
- 1800 s
- Reverse DNS last checked
- 2026-07-20 15:57 UTC
- Forward DNS last checked
- 2026-07-20 15:57 UTC
Forward DNS records for delta.blue
| Type | Value | Priority | TTL |
|---|---|---|---|
| A | 104.18.28.234 | — | 300s |
| A | 104.18.29.234 | — | 300s |
| AAAA | 2606:4700::6812:1cea | — | 300s |
| AAAA | 2606:4700::6812:1dea | — | 300s |
| MX | alt1.aspmx.l.google.com | 10 | — |
| MX | alt2.aspmx.l.google.com | 10 | — |
| MX | aspmx.l.google.com | 10 | — |
| MX | aspmx2.googlemail.com | 10 | — |
| MX | aspmx3.googlemail.com | 10 | — |
| NS | blue.foundationdns.com | — | — |
| NS | blue.foundationdns.net | — | — |
| NS | blue.foundationdns.org | — | — |
| TXT | anthropic-domain-verification-6z29xg=hI5sYJmB5xikQhjMc2ubxYAti | — | — |
| TXT | atlassian-domain-verification=gWhFwCBJsPODBD7w66MEx2V9CEiJIqDLRHYZwdPeOPDJQLOpIGYIiucgC9qkce1i | — | — |
| TXT | google-site-verification=3qUI1njqtL-6DW6VcCwTH_iby8Mv5iNnWux_K3cPoV8 | — | — |
| TXT | google-site-verification=q0jZVhz84KjPbGOjyi3ZZjF616tvV8ySjK5y9I4OVZk | — | — |
| TXT | openai-domain-verification=dv-cch9Z0oop3wc2VnXvFkeBGl4 | — | — |
| TXT | pandadoc-domain-verification=sRhSYFUkFWodFricCan9S9 | — | — |
| TXT | v=DMARC1; p=reject; rua=mailto:it@delta.blue | — | — |
| TXT | v=spf1 ip4:209.85.219.198/32 ip4:209.85.221.47/32 ip4:188.172.137.47/32 ip4:198.2.179.37/32 ip4:188.172.137.53/32 ip4:188.172.137.60/32 ip4:195.81.120.192/26 ip4:81.82.216.124/32 ip4:194.42.75.192/26 ip4:95.211.220.20/32 include:spf.mandrillapp.com include:mail.zendesk.com include:servers.mcsv.net include:_spf.google.com include:_spf.atlassian.net -all | — | — |
| CAA | iodef mailto:security@delta.blue | 0 | — |
| CAA | issue amazon.com | 0 | — |
| CAA | issue comodoca.com | 0 | — |
| CAA | issue digicert.com; cansignhttpexchanges=yes | 0 | — |
| CAA | issue letsencrypt.org | 0 | — |
| CAA | issue pki.goog; cansignhttpexchanges=yes | 0 | — |
| CAA | issue sectigo.com | 0 | — |
| CAA | issue ssl.com | 0 | — |
| CAA | issuewild comodoca.com | 0 | — |
| CAA | issuewild digicert.com; cansignhttpexchanges=yes | 0 | — |
| CAA | issuewild letsencrypt.org | 0 | — |
| CAA | issuewild pki.goog; cansignhttpexchanges=yes | 0 | — |
| CAA | issuewild ssl.com | 0 | — |
Reverse & forward DNS collected by the WorldIP scanner fleet — FCrDNS confirms the PTR hostname resolves back to this IP.
Network Allocation for 167.17.70.109
- CIDR range
- 167.17.70.0/24
- IP range (int)
- 2,802,927,104 — 2,802,927,359
- Prefix length
- /24
- Organization
- GTHost
- ASN
- AS63023
- ASN name
- GTHost
- Location
- Amsterdam, North Holland, The Netherlands
- Coordinates
- 52.371600, 4.888300
- Accuracy radius
- 20 km
- Postal code
- 1012
- Regional Internet Registry
- ARIN
- Allocated
- 2025-08-04
- Data source(s)
- maxmind_city, maxmind_country, ipinfo_lite, maxmind_asn
- Last updated
- 2026-07-11 09:23:45
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 167.17.70.109?
167.17.70.109 is allocated to GTHost (AS63023), registered in Amsterdam, The Netherlands.
Where is 167.17.70.109 located?
The geolocation for 167.17.70.109 maps to Amsterdam, The Netherlands 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 167.17.70.109 on?
167.17.70.109 belongs to the 167.17.70.0/24 network block announced by AS63023. This range contains 256 addresses.
Does 167.17.70.109 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.
