Hostname
lexus.com.br
Last fetched
lexus.com.br resolves to 12 IPv4 addresses operated by AMAZON-02 - Amazon.com, Inc. in US.
Nutrition Label
Resolution chain
lexus.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 |
|---|---|---|---|---|
| 16.58.120.253 | 16.58.0.0/17 | AS16509 | AMAZON-02 - Amazon.com, Inc. | US |
| 18.116.174.124 | 18.116.0.0/14 | AS16509 | AMAZON-02 - Amazon.com, Inc. | US |
| 18.218.190.19 | 18.216.0.0/14 | AS16509 | AMAZON-02 - Amazon.com, Inc. | US |
| 3.130.100.117 | 3.130.0.0/16 | AS16509 | AMAZON-02 - Amazon.com, Inc. | US |
| 3.139.130.187 | 3.136.0.0/13 | AS16509 | AMAZON-02 - Amazon.com, Inc. | US |
| 3.141.232.185 | 3.136.0.0/13 | AS16509 | AMAZON-02 - Amazon.com, Inc. | US |
| 3.151.215.236 | 3.144.0.0/13 | AS16509 | AMAZON-02 - Amazon.com, Inc. | US |
| 3.151.244.152 | 3.144.0.0/13 | AS16509 | AMAZON-02 - Amazon.com, Inc. | US |
| 3.151.7.179 | 3.144.0.0/13 | AS16509 | AMAZON-02 - Amazon.com, Inc. | US |
| 3.19.136.244 | 3.16.0.0/14 | AS16509 | AMAZON-02 - Amazon.com, Inc. | US |
| 16.58.137.21 | 16.58.128.0/17 | AS16509 | AMAZON-02 - Amazon.com, Inc. | US |
| 3.147.225.103 | 3.144.0.0/13 | AS16509 | AMAZON-02 - Amazon.com, Inc. | US |
WHOIS identity
- Registrar
- —
- Organization
- kdd - dom adm
- Contact emails
Subdomains
4 observed subdomains of lexus.com.br.
Web-graph footprint
Distinct hostnames that link to or from lexus.com.br in the public web crawl.
58 sites link to this hostname.
18 sites linked to from this hostname.
Sample inbound links
Threat posture
History
Mail and authentication
SPF policy
7 SPF mechanisms authorising senders for lexus.com.br.
| Mechanism | Target |
|---|---|
| SPF_INCLUDE | spf.protection.outlook.com |
| SPF_IP | 200.218.11.42 |
| SPF_IP | 200.218.11.43 |
| SPF_IP | 200.218.11.44 |
| SPF_IP | 200.218.11.45 |
| SPF_MX | mail2.toyota.com.br |
| SPF_MX | mail3.toyota.com.br |
Related pages
Pivot deeper into the graph from lexus.com.br.
Cypher and MCP
Reproduce the resolution chain directly against graph.whisper.security:
MATCH (h:HOSTNAME {name: "lexus.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.