Hostname
lafleureclose.com
Last fetched
lafleureclose.com resolves to 8 IPv4 addresses operated by AMAZON-02 - Amazon.com, Inc. in FR. WHOIS lists iana:303 as the registrar.
Nutrition Label
Resolution chain
lafleureclose.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 |
|---|---|---|---|---|
| 18.245.199.113 | 18.245.196.0/22 | AS16509 | AMAZON-02 - Amazon.com, Inc. | FR |
| 18.245.199.127 | 18.245.196.0/22 | AS16509 | AMAZON-02 - Amazon.com, Inc. | FR |
| 18.245.199.26 | 18.245.196.0/22 | AS16509 | AMAZON-02 - Amazon.com, Inc. | FR |
| 18.245.199.31 | 18.245.196.0/22 | AS16509 | AMAZON-02 - Amazon.com, Inc. | FR |
| 18.67.76.129 | 18.67.76.0/22 | AS16509 | AMAZON-02 - Amazon.com, Inc. | US |
| 18.67.76.21 | 18.67.76.0/22 | AS16509 | AMAZON-02 - Amazon.com, Inc. | US |
| 18.67.76.56 | 18.67.76.0/22 | AS16509 | AMAZON-02 - Amazon.com, Inc. | US |
| 18.67.76.73 | 18.67.76.0/22 | AS16509 | AMAZON-02 - Amazon.com, Inc. | US |
WHOIS identity
- Registrar
- iana:303
- Organization
- alina ostapenko
- Contact emails
Subdomains
3 observed subdomains of lafleureclose.com.
Web-graph footprint
Distinct hostnames that link to or from lafleureclose.com in the public web crawl.
Threat posture
History
Mail and authentication
MX records
SPF policy
5 SPF mechanisms authorising senders for lafleureclose.com.
| Mechanism | Target |
|---|---|
| SPF_A | lafleureclose.com |
| SPF_INCLUDE | mktomail.com |
| SPF_INCLUDE | spf.mandrillapp.com |
| SPF_INCLUDE | spf.protection.outlook.com |
| SPF_MX | lafleureclose.com |
Related pages
Pivot deeper into the graph from lafleureclose.com.
- IP · 18.245.199.113
- ASN · AS16509AMAZON-02 - Amazon.com, Inc.
- Registrar · iana:303
- Country · FR
- Email · alinaostapenko90@gmail.com
- TLD · .com
- Browse hostnames · la…
- 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: "lafleureclose.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.