Hostname
chefsteps.com
Last fetched
chefsteps.com resolves to 8 IPv4 addresses operated by AMAZON-02 - Amazon.com, Inc. in DE. WHOIS lists iana:299 as the registrar.
Nutrition Label
Resolution chain
chefsteps.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 |
|---|---|---|---|---|
| 13.226.244.112 | 13.226.244.0/22 | AS16509 | AMAZON-02 - Amazon.com, Inc. | DE |
| 13.226.244.119 | 13.226.244.0/22 | AS16509 | AMAZON-02 - Amazon.com, Inc. | DE |
| 13.226.244.35 | 13.226.244.0/22 | AS16509 | AMAZON-02 - Amazon.com, Inc. | DE |
| 13.226.244.80 | 13.226.244.0/22 | AS16509 | AMAZON-02 - Amazon.com, Inc. | DE |
| 3.161.44.109 | 3.161.44.0/23 | AS16509 | AMAZON-02 - Amazon.com, Inc. | MX |
| 3.161.44.116 | 3.161.44.0/23 | AS16509 | AMAZON-02 - Amazon.com, Inc. | MX |
| 3.161.44.4 | 3.161.44.0/23 | AS16509 | AMAZON-02 - Amazon.com, Inc. | MX |
| 3.161.44.40 | 3.161.44.0/23 | AS16509 | AMAZON-02 - Amazon.com, Inc. | MX |
WHOIS identity
- Registrar
- iana:299
- Organization
- breville pty
- Contact emails
Subdomains
52 observed subdomains of chefsteps.com.
Showing 25 of 52. View all subdomains →
Web-graph footprint
Distinct hostnames that link to or from chefsteps.com in the public web crawl.
Sample inbound links
Threat posture
History
Mail and authentication
SPF policy
3 SPF mechanisms authorising senders for chefsteps.com.
| Mechanism | Target |
|---|---|
| SPF_INCLUDE | amazonses.com |
| SPF_INCLUDE | sendgrid.net |
| SPF_INCLUDE | spf.protection.outlook.com |
Related pages
Pivot deeper into the graph from chefsteps.com.
- IP · 13.226.244.112
- ASN · AS16509AMAZON-02 - Amazon.com, Inc.
- Registrar · iana:299
- Country · DE
- Email · webdomains@breville.com.au
- 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: "chefsteps.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.