Hostname
lasikmd.com
Last fetched
lasikmd.com resolves to 6 IPv4 addresses operated by AMAZON-02 - Amazon.com, Inc. in CA. WHOIS lists iana:65 as the registrar.
Nutrition Label
Resolution chain
lasikmd.com resolves to 6 distinct IPv4 addresses via WhisperGraph DNS data. Each row links to the IP, prefix, and announcing ASN.
| IP | Prefix | ASN | Operator | Country |
|---|---|---|---|---|
| 15.156.160.197 | 15.156.0.0/15 | AS16509 | AMAZON-02 - Amazon.com, Inc. | CA |
| 15.157.165.247 | 15.156.0.0/15 | AS16509 | AMAZON-02 - Amazon.com, Inc. | CA |
| 15.157.18.208 | 15.156.0.0/15 | AS16509 | AMAZON-02 - Amazon.com, Inc. | CA |
| 16.52.183.194 | 16.52.0.0/16 | AS16509 | AMAZON-02 - Amazon.com, Inc. | CA |
| 35.182.90.16 | 35.182.0.0/15 | AS16509 | AMAZON-02 - Amazon.com, Inc. | CA |
| 99.79.147.121 | 99.79.0.0/16 | AS16509 | AMAZON-02 - Amazon.com, Inc. | CA |
WHOIS identity
- Registrar
- iana:65
- Organization
- arthur fargeon
- Contact emails
Subdomains
13 observed subdomains of lasikmd.com.
Web-graph footprint
Distinct hostnames that link to or from lasikmd.com in the public web crawl.
162 sites link to this hostname.
Threat posture
History
Mail and authentication
MX records
SPF policy
12 SPF mechanisms authorising senders for lasikmd.com.
| Mechanism | Target |
|---|---|
| SPF_INCLUDE | spf.protection.outlook.com |
| SPF_IP | 160.34.236.14/32 |
| SPF_IP | 160.34.236.57 |
| SPF_IP | 170.146.93.56 |
| SPF_IP | 184.107.95.181 |
| SPF_IP | 35.182.143.42 |
| SPF_IP | 50.56.130.220 |
| SPF_IP | 52.60.178.208 |
| SPF_IP | 52.60.239.76 |
| SPF_IP | 52.60.69.74 |
| SPF_IP | 65.55.93.60 |
| SPF_IP | 72.21.92.157 |
Related pages
Pivot deeper into the graph from lasikmd.com.
- IP · 15.156.160.197
- ASN · AS16509AMAZON-02 - Amazon.com, Inc.
- Registrar · iana:65
- Country · CA
- Email · digitalmarketing@lasikmd.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: "lasikmd.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.