link4.cn was registered with 成都西维数码科技有限公司 on 16 Sept 2026 and is hosted on AS138415 in Hong Kong. Its SSL certificate from Let's Encrypt is valid until 15 Dec 2026, and the site does not support HTTP/3.
What security vendors and the WOT community say about this domain.
0 of 5 protections set up
No SPF record: any server can send mail that claims to come from this domain.
—No key at the 12 common selectors we checked. A custom selector can’t be found from DNS alone.
—No DMARC policy: receivers aren’t told what to do with mail that fails SPF and DKIM.
—Forces encrypted delivery between mail servers.
—Shows the brand logo in supporting inboxes. Optional; needs DMARC enforcement.
—Read from the domain's public DNS records.
What loads and tracks visitors when the homepage opens.
Running a full browser scan of the homepage… This takes about a minute.
Internet standards that make a site faster and safer.
The path from a typed address to the final page.
478 similar domains registered in the last 90 days — possible typosquatting or phishing.
| Domain | Why it’s similar | Registered | Status | Report |
|---|---|---|---|---|
| link4.fun | Other extension | 8 Oct 2026 | Active website | Report → |
| link4.fans | Other extension | 25 Sept 2026 | No website | Report → |
| lin4k.com | Typo | 10 Sept 2026 | Active website | Report → |
| link4.social | Other extension | 8 Sept 2026 | RedirectsRedirects to link4.bio | Report → |
| link.town | Typo | 30 Oct 2026 | Active website | Report → |
From CubDomain's daily newly registered domains. Similar doesn't mean malicious.
Is link4.cn’s name taken on other extensions?
Every IP address link4.cn resolves to, and where it's hosted.
| Host | IPv4 address | TTL |
|---|---|---|
| link4.cn | 156.234.199.108 | 13 |
| link4.cn | 156.234.199.109 | 13 |
| link4.cn | 156.234.199.110 | 13 |
| link4.cn | 156.234.199.111 | 13 |
| link4.cn | 156.234.199.112 | 13 |
| link4.cn | 156.234.199.113 | 13 |
| link4.cn | 156.234.199.114 | 13 |
| link4.cn | 156.234.199.115 | 13 |
| link4.cn | 156.234.225.79 | 13 |
| link4.cn | 156.234.225.80 | 13 |
| link4.cn | 156.234.225.81 | 13 |
| link4.cn | 156.234.225.82 | 13 |
| link4.cn | 156.234.225.83 | 13 |
| Host | Name server | TTL |
|---|---|---|
| link4.cn | meg.ns.cloudflare.com | 86400 |
| link4.cn | noel.ns.cloudflare.com | 86400 |
| Host | Start of authority | TTL |
|---|---|---|
| link4.cn | meg.ns.cloudflare.com dns.cloudflare.com 2415224207 10000 2400 604800 1800 | 1800 |
Other domains served from 156.234.199.111. Normal for shared hosting and CDNs.
No reviews yet. Used link4.cn? 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.
link4.cn has no community safety rating yet. Its SSL certificate is valid until 15 Dec 2026. See Security →
link4.cn is registered through 成都西维数码科技有限公司. The public WHOIS record shows the registrant’s details. See WHOIS →
The registration expires on 16 Sept 2027 — in 10 months. See Overview →
link4.cn was registered on 16 Sept 2026, making it 1 month old. See Overview →
link4.cn is served from 13 IP addresses, mainly on AS138415 in Hong Kong. See Hosting →
Raw registry data for link4.cn. May be redacted by privacy services.
Domain Name: link4.cn ROID: 20260916s10001s76473031-cn Domain Status: ok Registrant: 贺洪志 Registrant Contact Email: [email protected] Sponsoring Registrar: 成都西维数码科技有限公司 Name Server: meg.ns.cloudflare.com Name Server: noel.ns.cloudflare.com Registration Time: 2026-09-16 16:00:16 Expiration Time: 2027-09-16 16:00:16 DNSSEC: unsigned
The first response from http://www.link4.cn, before any redirect: caching, server and policy headers.
Four timed TCP connections to port 443 from CubDomain's servers.
CubDomain is not affiliated with link4.cn. 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.
When the site first appeared, and what has changed since.
No changes seen since we started recording on 1 Nov 2026.
Found in public certificate transparency logs.
Searching the certificate transparency logs… This can take up to a minute.