Alternatives to l4d.com
Matched automatically on description, category and technology. Only sites that pass our safety checks are shown. · Report a wrong match
l4d.com was registered with whois.verisign-grs.com on 29 Mar 2000 and is hosted on AS16625 Akamai Technologies Inc. in India. Its SSL certificate from Let's Encrypt expired on 6 Feb 2024, and the site does not support HTTP/3. WOT's community rates its safety excellent (96/100).
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.
330 similar domains registered in the last 90 days — possible typosquatting or phishing.
| Domain | Why it’s similar | Registered | Status | Report |
|---|---|---|---|---|
| 14d.space | Look-alike characters | 26 Sept 2026 | Checking… | Report → |
| 14d.homes | Look-alike characters | 29 Aug 2026 | Checking… | Report → |
| 14d.top | Look-alike characters | 22 Aug 2026 | Checking… | Report → |
| l4d.dev | Other extension | 16 Oct 2026 | Checking… | Report → |
| 4ld.casino | Typo | 6 Oct 2026 | Checking… | Report → |
From CubDomain's daily newly registered domains. Similar doesn't mean malicious.
Is l4d.com’s name taken on other extensions?
Estimated visitors and engagement.
| Top countries | Share | Visits | Desktop | Mobile |
|---|---|---|---|---|
| United States | 16.3% | — | — | — |
| Peru | 3.9% | — | — | — |
| Russia | 3.4% | — | — | — |
| United Kingdom | 3.2% | — | — | — |
| Türkiye | 3.1% | — | — | — |
Every IP address l4d.com resolves to, and where it's hosted.
| Host | IPv4 address | TTL |
|---|---|---|
| l4d.com | 23.58.1.148 | 17 |
| Host | Mail server | TTL |
|---|---|---|
| l4d.com | 10 us-smtp-inbound-1.mimecast.com | 10800 |
| l4d.com | 10 us-smtp-inbound-2.mimecast.com | 10800 |
| Host | Name server | TTL |
|---|---|---|
| l4d.com | a1-194.akam.net | 21600 |
| l4d.com | a2-64.akam.net | 21600 |
| l4d.com | a22-67.akam.net | 21600 |
| l4d.com | a24-64.akam.net | 21600 |
| l4d.com | a7-66.akam.net | 21600 |
| l4d.com | a9-66.akam.net | 21600 |
| Host | Text | TTL |
|---|---|---|
| l4d.com | "v=spf1 mx include:_netblocks.mimecast.com -all" | 10800 |
| Host | Policy | TTL |
|---|---|---|
| l4d.com | 0 iodef mailto:[email protected] | 10800 |
| l4d.com | 0 issue digicert.com | 10800 |
| l4d.com | 0 issue letsencrypt.org | 10800 |
| Host | Start of authority | TTL |
|---|---|---|
| l4d.com | ns1.valvesoftware.com admin-dns.valvesoftware.com 2022042700 3600 900 2419200 86400 | 10800 |
Other domains served from 23.58.1.148. Normal for shared hosting and CDNs.
No reviews yet. Used l4d.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.
WOT's community rates l4d.com excellent for safety (96/100). Its SSL certificate expired on 6 Feb 2024. See Security →
l4d.com is registered through whois.verisign-grs.com. See WHOIS →
The registration expired on 29 Mar 2025. See Overview →
l4d.com was registered on 29 Mar 2000, making it 26 years old. See Overview →
l4d.com is served from 1 IP address, mainly on AS16625 Akamai Technologies Inc. in India. See Hosting →
Raw registry data for l4d.com. May be redacted by privacy services.
{"objectClassName":"domain","handle":"23678124_DOMAIN_COM-VRSN","ldhName":"L4D.COM","links":[{"value":"https:\/\/rdap.verisign.com\/com\/v1\/domain\/L4D.COM","rel":"self","href":"https:\/\/rdap.verisign.com\/com\/v1\/domain\/L4D.COM","type":"application\/rdap+json"},{"value":"https:\/\/rdap.networksolutions.com\/rdap\/domain\/L4D.COM","rel":"related","href":"https:\/\/rdap.networksolutions.com\/rdap\/domain\/L4D.COM","type":"application\/rdap+json"}],"status":["active"],"entities":[{"objectClassName":"entity","handle":"2","roles":["registrar"],"publicIds":[{"type":"IANA Registrar ID","identifier":"2"}],"vcardArray":["vcard",[["version",{},"text","4.0"],["fn",{},"text","Network Solutions, LLC"]]],"entities":[{"objectClassName":"entity","roles":["abuse"],"vcardArray":["vcard",[["version",{},"text","4.0"],["fn",{},"text",""],["tel",{"type":"voice"},"uri","tel:+1.8777228662"],["email",{},"text","[email protected]"]]]}]}],"events":[{"eventAction":"registration","eventDate":"2000-03-29T19:49:00Z"},{"eventAction":"expiration","eventDate":"2025-03-29T18:49:00Z"},{"eventAction":"last changed","eventDate":"2022-01-28T09:09:35Z"},{"eventAction":"last update of RDAP database","eventDate":"2023-10-24T08:00:13Z"}],"secureDNS":{"delegationSigned":false},"nameservers":[{"objectClassName":"nameserver","ldhName":"A1-164.AKAM.NET"},{"objectClassName":"nameserver","ldhName":"A11-67.AKAM.NET"},{"objectClassName":"nameserver","ldhName":"A24-64.AKAM.NET"},{"objectClassName":"nameserver","ldhName":"A26-65.AKAM.NET"},{"objectClassName":"nameserver","ldhName":"A8-66.AKAM.NET"},{"objectClassName":"nameserver","ldhName":"A9-67.AKAM.NET"}],"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.l4d.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 l4d.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.