Hostname
boldham.com
Last fetched
boldham.com resolves to 8 IPv4 addresses operated by AMAZON-02 - Amazon.com, Inc. in MX. WHOIS lists iana:468 as the registrar.
Nutrition Label
Resolution chain
boldham.com resolves to 8 distinct IPv4 addresses via WhisperGraph DNS data. Each row links to the IP, prefix, and announcing ASN.
| IP | Prefix | ASN | Operator | Country |
|---|---|---|---|---|
| 3.161.4.116 | 3.161.4.0/22 | AS16509 | AMAZON-02 - Amazon.com, Inc. | MX |
| 3.161.4.22 | 3.161.4.0/22 | AS16509 | AMAZON-02 - Amazon.com, Inc. | MX |
| 3.161.4.68 | 3.161.4.0/22 | AS16509 | AMAZON-02 - Amazon.com, Inc. | MX |
| 3.161.4.93 | 3.161.4.0/22 | AS16509 | AMAZON-02 - Amazon.com, Inc. | MX |
| 99.84.234.106 | 99.84.232.0/22 | AS16509 | AMAZON-02 - Amazon.com, Inc. | US |
| 99.84.234.122 | 99.84.232.0/22 | AS16509 | AMAZON-02 - Amazon.com, Inc. | US |
| 99.84.234.32 | 99.84.232.0/22 | AS16509 | AMAZON-02 - Amazon.com, Inc. | US |
| 99.84.234.35 | 99.84.232.0/22 | AS16509 | AMAZON-02 - Amazon.com, Inc. | US |
WHOIS identity
- Registrar
- iana:468
- Organization
- on behalf of boldham.com owner
- Contact emails
- gdpr-masking@gdpr-masked.com
- 154c9fe9-8d6c-4897-bc01-58d485aa08ee@identity-protect.org
- 1a64e45f-5d91-4ec3-b1f5-1a39881b1a19@identity-protect.org
- 1b65f614-1862-4037-bac9-2d6d643242fb@identity-protect.org
- 36f67f40-663f-447e-a9bb-a3ab09f4aafe@identity-protect.org
- 89d081c1-97ef-4409-a751-39bb4953c981@identity-protect.org
- eb3cc78e-27b3-4fb7-97da-9784eb7b99af@identity-protect.org
Subdomains
1 observed subdomain of boldham.com.
| Subdomain |
|---|
| www.boldham.com |
Threat posture
History
Related pages
Pivot deeper into the graph from boldham.com.
- IP · 3.161.4.116
- ASN · AS16509AMAZON-02 - Amazon.com, Inc.
- Registrar · iana:468
- Country · MX
- Email · gdpr-masking@gdpr-masked.com
- TLD · .com
- Browse hostnames · bo…
- Glossary · What is a hostname?
- Whisper Internet Directory — home
- Live MOAS conflicts feed
- Threat feed · Spamhaus DROP
- United States internet infrastructure
Cypher and MCP
Reproduce the resolution chain directly against graph.whisper.security:
MATCH (h:HOSTNAME {name: "boldham.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.