Hostname
lbeeu.com
Last fetched
lbeeu.com resolves to 8 IPv4 addresses operated by AMAZON-02 - Amazon.com, Inc. in KR. WHOIS lists iana:468 as the registrar.
Nutrition Label
Resolution chain
lbeeu.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 |
|---|---|---|---|---|
| 3.5.185.5 | 3.5.184.0/23 | AS16509 | AMAZON-02 - Amazon.com, Inc. | KR |
| 3.5.187.115 | 3.5.186.0/23 | AS16509 | AMAZON-02 - Amazon.com, Inc. | KR |
| 3.5.187.35 | 3.5.186.0/23 | AS16509 | AMAZON-02 - Amazon.com, Inc. | KR |
| 3.5.187.6 | 3.5.186.0/23 | AS16509 | AMAZON-02 - Amazon.com, Inc. | KR |
| 3.5.189.85 | 3.5.188.0/23 | AS16509 | AMAZON-02 - Amazon.com, Inc. | KR |
| 52.219.202.4 | 52.219.202.0/24 | AS16509 | AMAZON-02 - Amazon.com, Inc. | KR |
| 52.219.206.4 | 52.219.206.0/24 | AS16509 | AMAZON-02 - Amazon.com, Inc. | KR |
| 52.219.206.64 | 52.219.206.0/24 | AS16509 | AMAZON-02 - Amazon.com, Inc. | KR |
WHOIS identity
- Registrar
- iana:468
- Organization
- on behalf of lbeeu.com owner
- Contact emails
- 379fba47-49b3-4052-805e-fae658bc0135@identity-protect.org
- 5c18331b-2d45-452e-87ab-de21ee442d6c@identity-protect.org
- 70495816-5a9a-4c81-9109-9c0dc5b386c3@identity-protect.org
- 8ad4ecba-40fe-4323-a20b-5a7961f76520@identity-protect.org
- a2d4fbb9-e778-4a91-a83c-97ddda79339f@identity-protect.org
- e0236cd9-9c01-4f95-b902-7b3098396316@identity-protect.org
- faed222c-f521-4e25-bc93-4165f5dc3237@identity-protect.org
Subdomains
11 observed subdomains of lbeeu.com.
Threat posture
History
Related pages
Pivot deeper into the graph from lbeeu.com.
- IP · 3.5.185.5
- ASN · AS16509AMAZON-02 - Amazon.com, Inc.
- Registrar · iana:468
- Country · KR
- Email · 379fba47-49b3-4052-805e-fae658bc0135@identity-protect.org
- TLD · .com
- Browse hostnames · lb…
- 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: "lbeeu.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.