Hostname
delazucar.com
Last fetched
delazucar.com resolves to 10 IPv4 addresses operated by AMAZON-AES - Amazon.com, Inc. in US. WHOIS lists iana:146 as the registrar.
Nutrition Label
Resolution chain
delazucar.com resolves to 10 distinct IPv4 addresses via WhisperGraph DNS data. Each row links to the IP, prefix, and announcing ASN.
| IP | Prefix | ASN | Operator | Country |
|---|---|---|---|---|
| 100.49.227.156 | 100.48.0.0/12 | AS14618 | AMAZON-AES - Amazon.com, Inc. | US |
| 18.233.127.215 | 18.232.0.0/14 | AS14618 | AMAZON-AES - Amazon.com, Inc. | US |
| 3.219.109.222 | 3.208.0.0/12 | AS14618 | AMAZON-AES - Amazon.com, Inc. | US |
| 34.197.189.96 | 34.192.0.0/12 | AS14618 | AMAZON-AES - Amazon.com, Inc. | US |
| 34.228.252.12 | 34.224.0.0/12 | AS14618 | AMAZON-AES - Amazon.com, Inc. | US |
| 34.236.6.138 | 34.224.0.0/12 | AS14618 | AMAZON-AES - Amazon.com, Inc. | US |
| 52.200.237.24 | 52.200.0.0/13 | AS14618 | AMAZON-AES - Amazon.com, Inc. | US |
| 54.221.97.210 | 54.221.0.0/16 | AS14618 | AMAZON-AES - Amazon.com, Inc. | US |
| 54.81.166.63 | 54.80.0.0/14 | AS14618 | AMAZON-AES - Amazon.com, Inc. | US |
| 32.193.23.212 | 32.192.0.0/14 | AS14618 | AMAZON-AES - Amazon.com, Inc. | US |
WHOIS identity
- Registrar
- iana:146
- Organization
- domains by proxy,
- Contact emails
Subdomains
1 observed subdomain of delazucar.com.
| Subdomain |
|---|
| www.delazucar.com |
Threat posture
History
Mail and authentication
SPF policy
3 SPF mechanisms authorising senders for delazucar.com.
| Mechanism | Target |
|---|---|
| SPF_A | delazucar.com |
| SPF_IP | 18.209.207.213 |
| SPF_MX | delazucar.com |
Related pages
Pivot deeper into the graph from delazucar.com.
- IP · 100.49.227.156
- ASN · AS14618AMAZON-AES - Amazon.com, Inc.
- Registrar · iana:146
- Country · US
- Email · javierlozanogarza2@gmail.com
- TLD · .com
- Browse hostnames · de…
- 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: "delazucar.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.