Hostname
fanbase.com.br
Last fetched
fanbase.com.br resolves to 12 IPv4 addresses operated by AMAZON-02 - Amazon.com, Inc. in SG.
Nutrition Label
Resolution chain
fanbase.com.br 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.158.213.108 | 108.158.208.0/21 | AS16509 | AMAZON-02 - Amazon.com, Inc. | SG |
| 108.158.213.116 | 108.158.208.0/21 | AS16509 | AMAZON-02 - Amazon.com, Inc. | SG |
| 108.158.213.127 | 108.158.208.0/21 | AS16509 | AMAZON-02 - Amazon.com, Inc. | SG |
| 108.158.213.89 | 108.158.208.0/21 | AS16509 | AMAZON-02 - Amazon.com, Inc. | SG |
| 13.35.20.110 | 13.35.16.0/21 | AS16509 | AMAZON-02 - Amazon.com, Inc. | IN |
| 13.35.20.2 | 13.35.16.0/21 | AS16509 | AMAZON-02 - Amazon.com, Inc. | IN |
| 13.35.20.3 | 13.35.16.0/21 | AS16509 | AMAZON-02 - Amazon.com, Inc. | IN |
| 13.35.20.30 | 13.35.16.0/21 | AS16509 | AMAZON-02 - Amazon.com, Inc. | IN |
| 3.160.150.100 | 3.160.148.0/22 | AS16509 | AMAZON-02 - Amazon.com, Inc. | DE |
| 3.160.150.113 | 3.160.148.0/22 | AS16509 | AMAZON-02 - Amazon.com, Inc. | DE |
| 3.160.150.55 | 3.160.148.0/22 | AS16509 | AMAZON-02 - Amazon.com, Inc. | DE |
| 3.160.150.87 | 3.160.148.0/22 | AS16509 | AMAZON-02 - Amazon.com, Inc. | DE |
WHOIS identity
- Registrar
- —
- Organization
- fanbase network tecnologia e servi?os
- Contact emails
Subdomains
34 observed subdomains of fanbase.com.br.
Showing 25 of 34. View all subdomains →
Web-graph footprint
Distinct hostnames that link to or from fanbase.com.br in the public web crawl.
10 sites link to this hostname.
Threat posture
History
Mail and authentication
MX records
SPF policy
5 SPF mechanisms authorising senders for fanbase.com.br.
| Mechanism | Target |
|---|---|
| SPF_A | fanbase.com.br |
| SPF_INCLUDE | _spf.google.com |
| SPF_INCLUDE | mxsmtp.sendpulse.com |
| SPF_INCLUDE | mxsspf.sendpulse.com |
| SPF_MX | fanbase.com.br |
Related pages
Pivot deeper into the graph from fanbase.com.br.
Cypher and MCP
Reproduce the resolution chain directly against graph.whisper.security:
MATCH (h:HOSTNAME {name: "fanbase.com.br"})-[: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.