Hostname
locknlock.vn
Last fetched
locknlock.vn resolves to 104.18.39.56, announced in 104.18.39.0/24 by CLOUDFLARENET - Cloudflare, Inc. in CA. locknlock.vn is not listed on any threat feed indexed by WhisperGraph; reconciled level NONE.
Threat posture
0threat score (procedure-native scale)
NONENo threats observed.
- Threat feeds listing this
- 0
- Verdict coverage
- known-clean
Nutrition Label
Resolution chain
- 104.18.39.56
104.18.39.0/24 · CLOUDFLARENET - Cloudflare, Inc. · Toronto, CA
- 172.64.148.200
172.64.148.0/24 · CLOUDFLARENET - Cloudflare, Inc. · Toronto, CA
IPv6 resolution
No AAAA record for locknlock.vn is recorded in WhisperGraph.
Attribution
Cloudflare
cdn · ORIGIN_AS, CDN
WHOIS identity
WhisperGraph holds no WHOIS registrar, registrant organisation or contact email for locknlock.vn. WHOIS is recorded against the registrable domain, so a subdomain such as a www. host carries none of its own — check the registrable domain for this name.
Subdomains
| Subdomain |
|---|
| asc.locknlock.vn |
| click.locknlock.vn |
| cloud.locknlock.vn |
| demo.locknlock.vn |
| event.locknlock.vn |
| image.locknlock.vn |
| pos.locknlock.vn |
| view.locknlock.vn |
| www.locknlock.vn |
Showing 9 of 9 subdomains (9 per page).
Web-graph footprint
Sampled `LINKS_TO` edges. The hyperlink layer is a pilot sample, not a web-scale crawl, so these are illustrative.
Sample inbound links
Mail and authentication
Nameservers
- ns.gabia.co.kr
- ns1.gabia.co.kr
- ns1.cloudflare.net
- ns2.cloudflare.net
- ns3.cloudflare.net
- ns4.cloudflare.net
- ns5.cloudflare.net
- ns.gabia.net
MX records
- reply.s13.exacttarget.com
- mail9077.maychuemail.com
- mx9077.maychuemail.net
SPF policy
- include: cust-spf.exacttarget.com
- include: spf.maychuemail.com
- a: development.ap01.locknlock.demandware.net
- a: production.ap01.locknlock.demandware.net
- a: staging.ap01.locknlock.demandware.net
Threat-feed evidence
History
Related pages
Pivot from locknlock.vn into the addresses, networks and registries it depends on.
Cypher and MCP
Reproduce this hostname's resolution chain against graph.whisper.security:
MATCH (h:HOSTNAME {name: "locknlock.vn"})-[:RESOLVES_TO]->(ip:IPV4)
-[:ANNOUNCED_BY]->(ap:ANNOUNCED_PREFIX)-[:ROUTES]->(a:ASN)
OPTIONAL MATCH (a)-[:HAS_NAME]->(n:ASN_NAME)
RETURN ip.name AS ip, ap.name AS prefix, a.name AS asn, n.name AS network
LIMIT 20Or query Whisper from your own LLM workflow via the Whisper MCP server.