Hostname
chefsmakingwaves.com
Last fetched
chefsmakingwaves.com resolves to 10 IPv4 addresses operated by AMAZON-AES - Amazon.com, Inc. in US. WHOIS lists iana:291 as the registrar.
Nutrition Label
Resolution chain
chefsmakingwaves.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.31.217.136 | 100.24.0.0/13 | AS14618 | AMAZON-AES - Amazon.com, Inc. | US |
| 100.51.80.120 | 100.48.0.0/12 | AS14618 | AMAZON-AES - Amazon.com, Inc. | US |
| 3.212.230.89 | 3.208.0.0/12 | AS14618 | AMAZON-AES - Amazon.com, Inc. | US |
| 3.217.22.203 | 3.208.0.0/12 | AS14618 | AMAZON-AES - Amazon.com, Inc. | US |
| 44.217.71.44 | 44.192.0.0/11 | AS14618 | AMAZON-AES - Amazon.com, Inc. | US |
| 52.0.12.151 | 52.0.0.0/15 | AS14618 | AMAZON-AES - Amazon.com, Inc. | US |
| 52.201.80.230 | 52.200.0.0/13 | AS14618 | AMAZON-AES - Amazon.com, Inc. | US |
| 54.84.216.134 | 54.84.0.0/15 | AS14618 | AMAZON-AES - Amazon.com, Inc. | US |
| 98.86.23.67 | 98.80.0.0/13 | AS14618 | AMAZON-AES - Amazon.com, Inc. | US |
| 98.95.101.185 | 98.88.0.0/13 | AS14618 | AMAZON-AES - Amazon.com, Inc. | US |
WHOIS identity
- Registrar
- iana:291
- Organization
- jewella privacy - 377b4
- Contact emails
Subdomains
9 observed subdomains of chefsmakingwaves.com.
Web-graph footprint
Distinct hostnames that link to or from chefsmakingwaves.com in the public web crawl.
57 sites link to this hostname.
60 sites linked to from this hostname.
Sample inbound links
Threat posture
History
Related pages
Pivot deeper into the graph from chefsmakingwaves.com.
- IP · 100.31.217.136
- ASN · AS14618AMAZON-AES - Amazon.com, Inc.
- Registrar · iana:291
- Country · US
- Email · chefsmakingwaves.com@dnic.jewellaprivacy.com
- TLD · .com
- Browse hostnames · ch…
- 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: "chefsmakingwaves.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.