Hostname
beereaders.com
Last fetched
beereaders.com resolves to 12 IPv4 addresses operated by AMAZON-02 - Amazon.com, Inc. in US. WHOIS lists iana:146 as the registrar.
Nutrition Label
Resolution chain
beereaders.com resolves to 12 distinct IPv4 addresses via WhisperGraph DNS data. Each row links to the IP, prefix, and announcing ASN.
| IP | Prefix | ASN | Operator | Country |
|---|---|---|---|---|
| 108.139.47.10 | 108.139.44.0/22 | AS16509 | AMAZON-02 - Amazon.com, Inc. | US |
| 108.139.47.16 | 108.139.44.0/22 | AS16509 | AMAZON-02 - Amazon.com, Inc. | US |
| 108.139.47.25 | 108.139.44.0/22 | AS16509 | AMAZON-02 - Amazon.com, Inc. | US |
| 108.139.47.54 | 108.139.44.0/22 | AS16509 | AMAZON-02 - Amazon.com, Inc. | US |
| 52.222.136.112 | 52.222.136.0/21 | AS16509 | AMAZON-02 - Amazon.com, Inc. | DE |
| 52.222.136.25 | 52.222.136.0/21 | AS16509 | AMAZON-02 - Amazon.com, Inc. | DE |
| 52.222.136.42 | 52.222.136.0/21 | AS16509 | AMAZON-02 - Amazon.com, Inc. | DE |
| 52.222.136.65 | 52.222.136.0/21 | AS16509 | AMAZON-02 - Amazon.com, Inc. | DE |
| 65.9.175.103 | 65.9.174.0/23 | AS16509 | AMAZON-02 - Amazon.com, Inc. | DE |
| 65.9.175.106 | 65.9.174.0/23 | AS16509 | AMAZON-02 - Amazon.com, Inc. | DE |
| 65.9.175.57 | 65.9.174.0/23 | AS16509 | AMAZON-02 - Amazon.com, Inc. | DE |
| 65.9.175.83 | 65.9.174.0/23 | AS16509 | AMAZON-02 - Amazon.com, Inc. | DE |
WHOIS identity
- Registrar
- iana:146
- Organization
- christopher tinson
- Contact emails
Subdomains
30 observed subdomains of beereaders.com.
Showing 25 of 30. View all subdomains →
Web-graph footprint
Distinct hostnames that link to or from beereaders.com in the public web crawl.
64 sites link to this hostname.
Sample inbound links
Threat posture
History
Mail and authentication
MX records
SPF policy
2 SPF mechanisms authorising senders for beereaders.com.
| Mechanism | Target |
|---|---|
| SPF_INCLUDE | 6307526.spf10.hubspotemail.net |
| SPF_INCLUDE | _spf.google.com |
Related pages
Pivot deeper into the graph from beereaders.com.
Cypher and MCP
Reproduce the resolution chain directly against graph.whisper.security:
MATCH (h:HOSTNAME {name: "beereaders.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.