Hostname
silvermanbaer.com
Last fetched
silvermanbaer.com resolves to 8 IPv4 addresses operated by AMAZON-02 - Amazon.com, Inc. in KR. WHOIS lists iana:468 as the registrar.
Nutrition Label
Resolution chain
silvermanbaer.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.225.134.14 | 13.225.128.0/21 | AS16509 | AMAZON-02 - Amazon.com, Inc. | KR |
| 13.225.134.28 | 13.225.128.0/21 | AS16509 | AMAZON-02 - Amazon.com, Inc. | KR |
| 13.225.134.31 | 13.225.128.0/21 | AS16509 | AMAZON-02 - Amazon.com, Inc. | KR |
| 13.225.134.9 | 13.225.128.0/21 | AS16509 | AMAZON-02 - Amazon.com, Inc. | KR |
| 18.161.125.104 | 18.161.120.0/21 | AS16509 | AMAZON-02 - Amazon.com, Inc. | IN |
| 18.161.125.122 | 18.161.120.0/21 | AS16509 | AMAZON-02 - Amazon.com, Inc. | IN |
| 18.161.125.26 | 18.161.120.0/21 | AS16509 | AMAZON-02 - Amazon.com, Inc. | IN |
| 18.161.125.62 | 18.161.120.0/21 | AS16509 | AMAZON-02 - Amazon.com, Inc. | IN |
WHOIS identity
- Registrar
- iana:468
- Organization
- on behalf of silvermanbaer.com owner
- Contact emails
Subdomains
2 observed subdomains of silvermanbaer.com.
Web-graph footprint
Distinct hostnames that link to or from silvermanbaer.com in the public web crawl.
Sample inbound links
Threat posture
History
Mail and authentication
SPF policy
3 SPF mechanisms authorising senders for silvermanbaer.com.
| Mechanism | Target |
|---|---|
| SPF_INCLUDE | 26129887.spf06.hubspotemail.net |
| SPF_INCLUDE | spf.protection.outlook.com |
| SPF_MX | silvermanbaer.com |
Related pages
Pivot deeper into the graph from silvermanbaer.com.
- IP · 13.225.134.14
- ASN · AS16509AMAZON-02 - Amazon.com, Inc.
- Registrar · iana:468
- Country · KR
- Email · info@crowneleven.com
- TLD · .com
- Browse hostnames · si…
- 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: "silvermanbaer.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.