Hostname
geopostuk.com
Last fetched
geopostuk.com resolves to 16 IPv4 addresses operated by AKAMAI-ASN1 in DE. WHOIS lists iana:470 as the registrar.
Nutrition Label
Resolution chain
geopostuk.com resolves to 16 distinct IPv4 addresses via WhisperGraph DNS data. Each row links to the IP, prefix, and announcing ASN.
| IP | Prefix | ASN | Operator | Country |
|---|---|---|---|---|
| 2.17.100.193 | 2.17.100.0/24 | AS20940 | AKAMAI-ASN1 | DE |
| 2.17.100.203 | 2.17.100.0/24 | AS20940 | AKAMAI-ASN1 | DE |
| 2.17.147.201 | 2.17.147.0/24 | AS20940 | AKAMAI-ASN1 | CZ |
| 2.17.147.202 | 2.17.147.0/24 | AS20940 | AKAMAI-ASN1 | CZ |
| 23.200.88.46 | 23.200.88.0/24 | AS20940 | AKAMAI-ASN1 | US |
| 23.200.88.51 | 23.200.88.0/24 | AS20940 | AKAMAI-ASN1 | US |
| 23.212.110.145 | 23.212.110.0/24 | AS20940 | AKAMAI-ASN1 | CZ |
| 23.212.110.160 | 23.212.110.0/24 | AS20940 | AKAMAI-ASN1 | CZ |
| 23.215.9.137 | 23.215.9.0/24 | AS20940 | AKAMAI-ASN1 | US |
| 23.215.9.146 | 23.215.9.0/24 | AS20940 | AKAMAI-ASN1 | US |
| 23.50.131.153 | 23.50.131.0/24 | AS20940 | AKAMAI-ASN1 | DE |
| 23.50.131.155 | 23.50.131.0/24 | AS20940 | AKAMAI-ASN1 | DE |
| 23.53.42.232 | 23.53.40.0/22 | AS20940 | AKAMAI-ASN1 | DE |
| 23.53.43.57 | 23.53.40.0/22 | AS20940 | AKAMAI-ASN1 | DE |
| 95.100.146.32 | 95.100.146.0/24 | AS20940 | AKAMAI-ASN1 | CZ |
| 95.100.146.35 | 95.100.146.0/24 | AS20940 | AKAMAI-ASN1 | CZ |
WHOIS identity
- Registrar
- iana:470
- Organization
- domain admin
- Contact emails
Subdomains
42 observed subdomains of geopostuk.com.
Showing 25 of 42. View all subdomains →
Web-graph footprint
Distinct hostnames that link to or from geopostuk.com in the public web crawl.
8 sites link to this hostname.
Threat posture
History
Mail and authentication
MX records
SPF policy
3 SPF mechanisms authorising senders for geopostuk.com.
| Mechanism | Target |
|---|---|
| SPF_INCLUDE | _spf.dpdgroup.co.uk |
| SPF_INCLUDE | _spf.google.com |
| SPF_INCLUDE | _spf.salesforce.com |
Related pages
Pivot deeper into the graph from geopostuk.com.
Cypher and MCP
Reproduce the resolution chain directly against graph.whisper.security:
MATCH (h:HOSTNAME {name: "geopostuk.com"})-[:RESOLVES_TO]->(ip:IPV4)
-[:ANNOUNCED_BY]->(ap:ANNOUNCED_PREFIX)
-[:ROUTES]->(asn:ASN)-[:HAS_NAME]->(n:ASN_NAME)
RETURN ip.name AS ip, ap.name AS prefix, asn.name AS asn, n.name AS operator
LIMIT 20Or query Whisper from your own LLM workflow via the Whisper MCP server.