Hostname
baeme.com
Last fetched
baeme.com resolves to 8 IPv4 addresses operated by AMAZON-02 - Amazon.com, Inc. in US. WHOIS lists iana:468 as the registrar.
Nutrition Label
Resolution chain
baeme.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 |
|---|---|---|---|---|
| 18.164.124.21 | 18.164.132.0/23 | AS16509 | AMAZON-02 - Amazon.com, Inc. | US |
| 18.164.124.52 | 18.164.132.0/23 | AS16509 | AMAZON-02 - Amazon.com, Inc. | US |
| 18.164.124.79 | 18.164.132.0/23 | AS16509 | AMAZON-02 - Amazon.com, Inc. | US |
| 18.164.124.95 | 18.164.132.0/23 | AS16509 | AMAZON-02 - Amazon.com, Inc. | US |
| 18.239.225.21 | 18.239.230.0/24 | AS16509 | AMAZON-02 - Amazon.com, Inc. | US |
| 18.239.225.28 | 18.239.230.0/24 | AS16509 | AMAZON-02 - Amazon.com, Inc. | US |
| 18.239.225.38 | 18.239.230.0/24 | AS16509 | AMAZON-02 - Amazon.com, Inc. | US |
| 18.239.225.96 | 18.239.230.0/24 | AS16509 | AMAZON-02 - Amazon.com, Inc. | US |
WHOIS identity
- Registrar
- iana:468
- Organization
- on behalf of baeme.com owner
- Contact emails
- baeme.com@registrantprivacy.com
- pauldavid.song@gmail.com
- 13eef801-cf44-4b16-978d-bf5d7531e798@identity-protect.org
- 21706598-e1af-47de-87ae-79466319989c@identity-protect.org
- 68df4343-ab44-46cf-b9ea-6e424e3aed5d@identity-protect.org
- 698b7732-ceb3-452a-898b-1b0148761ec9@identity-protect.org
- 9442e1cd-8f54-45fc-a959-7005ac130c7b@identity-protect.org
Subdomains
3 observed subdomains of baeme.com.
Threat posture
History
Mail and authentication
MX records
Related pages
Pivot deeper into the graph from baeme.com.
- IP · 18.164.124.21
- ASN · AS16509AMAZON-02 - Amazon.com, Inc.
- Registrar · iana:468
- Country · US
- Email · baeme.com@registrantprivacy.com
- TLD · .com
- Browse hostnames · ba…
- 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: "baeme.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.