Hostname
leadfinery.com
Last fetched
leadfinery.com resolves to 12 IPv4 addresses operated by AMAZON-02 - Amazon.com, Inc. in US. WHOIS lists iana:1068 as the registrar.
Nutrition Label
Resolution chain
leadfinery.com 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 |
|---|---|---|---|---|
| 13.226.209.53 | 13.226.216.0/21 | AS16509 | AMAZON-02 - Amazon.com, Inc. | US |
| 13.226.209.60 | 13.226.216.0/21 | AS16509 | AMAZON-02 - Amazon.com, Inc. | US |
| 13.226.209.76 | 13.226.216.0/21 | AS16509 | AMAZON-02 - Amazon.com, Inc. | US |
| 13.226.209.92 | 13.226.216.0/21 | AS16509 | AMAZON-02 - Amazon.com, Inc. | US |
| 13.227.192.36 | 13.227.208.0/24 | AS16509 | AMAZON-02 - Amazon.com, Inc. | CZ |
| 13.227.192.63 | 13.227.208.0/24 | AS16509 | AMAZON-02 - Amazon.com, Inc. | CZ |
| 13.227.192.66 | 13.227.208.0/24 | AS16509 | AMAZON-02 - Amazon.com, Inc. | CZ |
| 13.227.192.95 | 13.227.208.0/24 | AS16509 | AMAZON-02 - Amazon.com, Inc. | CZ |
| 13.35.20.10 | 13.35.30.0/23 | AS16509 | AMAZON-02 - Amazon.com, Inc. | IN |
| 13.35.20.46 | 13.35.30.0/23 | AS16509 | AMAZON-02 - Amazon.com, Inc. | IN |
| 13.35.20.57 | 13.35.30.0/23 | AS16509 | AMAZON-02 - Amazon.com, Inc. | IN |
| 13.35.20.60 | 13.35.30.0/23 | AS16509 | AMAZON-02 - Amazon.com, Inc. | IN |
WHOIS identity
- Registrar
- iana:1068
- Organization
- web2 user
- Contact emails
Subdomains
30 observed subdomains of leadfinery.com.
Showing 23 of 30. View all subdomains →
Threat posture
History
Mail and authentication
MX records
Related pages
Pivot deeper into the graph from leadfinery.com.
- IP · 13.226.209.53
- ASN · AS16509AMAZON-02 - Amazon.com, Inc.
- Registrar · iana:1068
- Country · US
- Email · davem0469@aol.com
- TLD · .com
- Browse hostnames · le…
- 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: "leadfinery.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.