Hostname
levesaude.com.br
Last fetched
levesaude.com.br resolves to 12 IPv4 addresses operated by AMAZON-AES - Amazon.com, Inc. in US.
Nutrition Label
Resolution chain
levesaude.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 |
|---|---|---|---|---|
| 100.51.33.172 | 100.48.0.0/12 | AS14618 | AMAZON-AES - Amazon.com, Inc. | US |
| 13.216.13.209 | 13.216.0.0/13 | AS14618 | AMAZON-AES - Amazon.com, Inc. | US |
| 184.73.17.78 | 184.73.0.0/16 | AS14618 | AMAZON-AES - Amazon.com, Inc. | US |
| 23.20.122.154 | 23.20.0.0/15 | AS14618 | AMAZON-AES - Amazon.com, Inc. | US |
| 3.219.252.57 | 3.208.0.0/12 | AS14618 | AMAZON-AES - Amazon.com, Inc. | US |
| 3.220.0.159 | 3.208.0.0/12 | AS14618 | AMAZON-AES - Amazon.com, Inc. | US |
| 34.239.19.254 | 34.224.0.0/12 | AS14618 | AMAZON-AES - Amazon.com, Inc. | US |
| 44.195.131.49 | 44.192.0.0/11 | AS14618 | AMAZON-AES - Amazon.com, Inc. | US |
| 44.215.49.21 | 44.192.0.0/11 | AS14618 | AMAZON-AES - Amazon.com, Inc. | US |
| 54.159.122.7 | 54.156.0.0/14 | AS14618 | AMAZON-AES - Amazon.com, Inc. | US |
| 98.90.148.247 | 98.88.0.0/13 | AS14618 | AMAZON-AES - Amazon.com, Inc. | US |
| 98.94.142.207 | 98.88.0.0/13 | AS14618 | AMAZON-AES - Amazon.com, Inc. | US |
WHOIS identity
- Registrar
- —
- Organization
- leve saude operadora de planos de saude ltda
- Contact emails
Subdomains
16 observed subdomains of levesaude.com.br.
Showing 13 of 16. View all subdomains →
Web-graph footprint
Distinct hostnames that link to or from levesaude.com.br in the public web crawl.
39 sites link to this hostname.
71 sites linked to from this hostname.
Sample inbound links
Threat posture
History
Mail and authentication
MX records
SPF policy
2 SPF mechanisms authorising senders for levesaude.com.br.
| Mechanism | Target |
|---|---|
| SPF_INCLUDE | _spf.aremail.com.br |
| SPF_INCLUDE | _spf.google.com |
Related pages
Pivot deeper into the graph from levesaude.com.br.
Cypher and MCP
Reproduce the resolution chain directly against graph.whisper.security:
MATCH (h:HOSTNAME {name: "levesaude.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.