Alternatives to lockincomp.com
Matched automatically on description, category and technology. Only sites that pass our safety checks are shown. · Report a wrong match
lockincomp.com was registered with whois.verisign-grs.com on 23 Apr 2013. We couldn't read an SSL certificate for it when we last analysed it.
What security vendors and the WOT community say about this domain.
What loads and tracks visitors when the homepage opens.
Running a full browser scan of the homepage… This takes about a minute.
We couldn't read an SSL certificate on port 443 when we last analysed lockincomp.com. Refresh the analysis to check again.
1 similar domain registered in the last 90 days — possible typosquatting or phishing.
| Domain | Why it’s similar | Registered | Status | Report |
|---|---|---|---|---|
| lockincompanion.com | Keyword added | 17 Sept 2026 | Checking… | Report → |
From CubDomain's daily newly registered domains. Similar doesn't mean malicious.
Is lockincomp.com’s name taken on other extensions?
Estimated visitors and engagement.
| Top countries | Share | Visits | Desktop | Mobile |
|---|---|---|---|---|
| South Korea | 73.6% | — | — | — |
| Peru | 6.7% | — | — | — |
| Taiwan | 5.9% | — | — | — |
| China | 5.1% | — | — | — |
| Bangladesh | 4.9% | — | — | — |
| Host | Mail server | TTL |
|---|---|---|
| lockincomp.com | 0 lockincomp-com.mail.protection.outlook.com | 0 |
| Host | Name server | TTL |
|---|---|---|
| lockincomp.com | ns1.vidc.co.kr | 0 |
| lockincomp.com | ns2.vidc.co.kr | 0 |
| Host | Text | TTL |
|---|---|---|
| lockincomp.com | "brevo-code:cd4ee7bc98c019f5fc296057c14e4f91" | 0 |
| lockincomp.com | "google-site-verification=mI2C4_Cno-5d7yw8-P8b1gFI3b3ezGVBVM2EwrAxKhs" | 0 |
| lockincomp.com | "google-site-verification=vsz0ZxZvZfaBbTcAhlGc6xTCM88VYvJrKDx5F0t3ezc" | 0 |
| lockincomp.com | "google-site-verification=WniNueQ4HxDX7mTHPGMflNVEJ_Oo2PaHGCRGBt3Ag9A" | 0 |
| lockincomp.com | "v=spf1 include:spf.protection.outlook.com -all" | 0 |
| Host | Start of authority | TTL |
|---|---|---|
| lockincomp.com | ns1.vidc.co.kr sys.vidc.co.kr 2014090401 21600 1800 3600000 86400 | 0 |
No reviews yet. Used lockincomp.com? Be the first to say how it went.
Reviews are from CubDomain users and are separate from the security verdicts above.
Common questions, answered from this report's data.
lockincomp.com has no community safety rating yet. We couldn't read an SSL certificate on it when we last analysed it. See Security →
lockincomp.com is registered through whois.verisign-grs.com. See WHOIS →
The registration expires on 23 Apr 2027 — in 5 months. See Overview →
lockincomp.com was registered on 23 Apr 2013, making it 13 years old. See Overview →
Raw registry data for lockincomp.com. May be redacted by privacy services.
{"objectClassName":"domain","handle":"1795977096_DOMAIN_COM-VRSN","ldhName":"LOCKINCOMP.COM","links":[{"value":"https:\/\/rdap.verisign.com\/com\/v1\/domain\/LOCKINCOMP.COM","rel":"self","href":"https:\/\/rdap.verisign.com\/com\/v1\/domain\/LOCKINCOMP.COM","type":"application\/rdap+json"},{"value":"https:\/\/rdap.inames.co.kr\/rdap\/domain\/LOCKINCOMP.COM","rel":"related","href":"https:\/\/rdap.inames.co.kr\/rdap\/domain\/LOCKINCOMP.COM","type":"application\/rdap+json"}],"status":["active"],"entities":[{"objectClassName":"entity","handle":"444","roles":["registrar"],"publicIds":[{"type":"IANA Registrar ID","identifier":"444"}],"vcardArray":["vcard",[["version",{},"text","4.0"],["fn",{},"text","Inames Co., Ltd."]]],"entities":[{"objectClassName":"entity","roles":["abuse"],"vcardArray":["vcard",[["version",{},"text","4.0"],["fn",{},"text",""],["tel",{"type":"voice"},"uri","tel:08203180290423"],["email",{},"text","[email protected]"]]]}]}],"events":[{"eventAction":"registration","eventDate":"2013-04-23T07:08:17Z"},{"eventAction":"expiration","eventDate":"2027-04-23T07:08:17Z"},{"eventAction":"last changed","eventDate":"2021-04-14T08:26:21Z"},{"eventAction":"last update of RDAP database","eventDate":"2023-10-24T20:32:44Z"}],"secureDNS":{"delegationSigned":false},"nameservers":[{"objectClassName":"nameserver","ldhName":"NS1.VIDC.CO.KR"},{"objectClassName":"nameserver","ldhName":"NS2.VIDC.CO.KR"}],"rdapConformance":["rdap_level_0","icann_rdap_technical_implementation_guide_0","icann_rdap_response_profile_0"],"notices":[{"title":"Terms of Use","description":["Service subject to Terms of Use."],"links":[{"href":"https:\/\/www.verisign.com\/domain-names\/registration-data-access-protocol\/terms-service\/index.xhtml","type":"text\/html"}]},{"title":"Status Codes","description":["For more information on domain status codes, please visit https:\/\/icann.org\/epp"],"links":[{"href":"https:\/\/icann.org\/epp","type":"text\/html"}]},{"title":"RDDS Inaccuracy Complaint Form","description":["URL of the ICANN RDDS Inaccuracy Complaint Form: https:\/\/icann.org\/wicf"],"links":[{"href":"https:\/\/icann.org\/wicf","type":"text\/html"}]}]}The first response from http://www.lockincomp.com, before any redirect: caching, server and policy headers.
Four timed TCP connections to port 443 from CubDomain's servers.
CubDomain is not affiliated with lockincomp.com. Data is collected independently from public sources and some figures are estimates, provided for information only.
Spam and malware blocklists for the site's IP and mail servers.
Found in public certificate transparency logs.
Searching the certificate transparency logs… This can take up to a minute.
When the site first appeared, and what has changed since.
We record what changes from the next time this report is refreshed.