lwlcom.net was registered with whois.verisign-grs.com on 28 Aug 2000 and is hosted on AS50629 LWLcom GmbH in Germany. Its SSL certificate from Let's Encrypt expired on 20 Feb 2024, and the site does not support HTTP/3. WOT's community rates its safety good (61/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.
4 similar domains registered in the last 90 days — possible typosquatting or phishing.
| Domain | Why it’s similar | Registered | Status | Report |
|---|---|---|---|---|
| owlcom.net | Typo | 27 Aug 2026 | Checking… | Report → |
| lalcom.ir | Typo | 7 Oct 2026 | Checking… | Report → |
| llcom.top | Typo | 31 Oct 2026 | Checking… | Report → |
| lywlcom.top | Extra letter | 10 Sept 2026 | Checking… | Report → |
From CubDomain's daily newly registered domains. Similar doesn't mean malicious.
Is lwlcom.net’s name taken on other extensions?
Estimated visitors and engagement.
| Top countries | Share | Visits | Desktop | Mobile |
|---|---|---|---|---|
| Germany | 30.5% | — | — | — |
| United States | 11.4% | — | — | — |
| Vietnam | 11% | — | — | — |
| Czechia | 9% | — | — | — |
| Spain | 8.6% | — | — | — |
Every IP address lwlcom.net resolves to, and where it's hosted.
| Host | IPv4 address | TTL |
|---|---|---|
| lwlcom.net | 31.209.92.5 | 298 |
| Host | Mail server | TTL |
|---|---|---|
| lwlcom.net | 0 lwlcom-net.mail.protection.outlook.com | 3600 |
| Host | Name server | TTL |
|---|---|---|
| lwlcom.net | ns01.lwldns.de | 3600 |
| lwlcom.net | ns02.lwldns.de | 3600 |
| lwlcom.net | ns03.lwldns.de | 3600 |
| lwlcom.net | ns04.lwldns.com | 3600 |
| lwlcom.net | ns05.lwldns.com | 3600 |
| Host | Text | TTL |
|---|---|---|
| lwlcom.net | "atlassian-domain-verification=/sSbzjXmmSWiRV35Uwj5soKUruasgamoUI3nFYtQJH77JhaCTSRb3tvhpAluiXeF" | 60 |
| lwlcom.net | "atlassian-sending-domain-verification=43962073-ff4e-4f33-8231-095382997ef4" | 60 |
| lwlcom.net | "facebook-domain-verification=6ow2wkmwo1vt2mn0thuhl5o5pru2w4" | 60 |
| lwlcom.net | "google-site-verification=iRgyyZuSD0cwErXTsiPQxMf6Eao3OKZXzq9AlErRjZs" | 60 |
| lwlcom.net | "have-i-been-pwned-verification=dweb_pq2ki78ro3tnva4h9y1clx87" | 60 |
| lwlcom.net | "MS=ms92963420" | 60 |
| lwlcom.net | "v=spf1 a mx ip4:31.209.92.137/32 ip4:31.209.92.133/32 ip4:31.209.92.153/32 ip4:31.209.95.17/32 include:spf.protection.outlook.com -all" | 60 |
| Host | Start of authority | TTL |
|---|---|---|
| lwlcom.net | ns01.lwldns.de noc.lwlcom.net 2017013000 28800 7200 604800 86400 | 3600 |
No reviews yet. Used lwlcom.net? 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 lwlcom.net good for safety (61/100). Its SSL certificate expired on 20 Feb 2024. See Security →
lwlcom.net is registered through whois.verisign-grs.com. See WHOIS →
The registration expired on 28 Aug 2024. See Overview →
lwlcom.net was registered on 28 Aug 2000, making it 26 years old. See Overview →
lwlcom.net is served from 1 IP address, mainly on AS50629 LWLcom GmbH in Germany. See Hosting →
Raw registry data for lwlcom.net. May be redacted by privacy services.
{"objectClassName":"domain","handle":"33653458_DOMAIN_NET-VRSN","ldhName":"LWLCOM.NET","links":[{"value":"https:\/\/rdap.verisign.com\/net\/v1\/domain\/LWLCOM.NET","rel":"self","href":"https:\/\/rdap.verisign.com\/net\/v1\/domain\/LWLCOM.NET","type":"application\/rdap+json"},{"value":"https:\/\/rdap.your-server.de\/domain\/LWLCOM.NET","rel":"related","href":"https:\/\/rdap.your-server.de\/domain\/LWLCOM.NET","type":"application\/rdap+json"}],"status":["client transfer prohibited"],"entities":[{"objectClassName":"entity","handle":"828","roles":["registrar"],"publicIds":[{"type":"IANA Registrar ID","identifier":"828"}],"vcardArray":["vcard",[["version",{},"text","4.0"],["fn",{},"text","Hetzner Online GmbH"]]],"entities":[{"objectClassName":"entity","roles":["abuse"],"vcardArray":["vcard",[["version",{},"text","4.0"],["fn",{},"text",""],["tel",{"type":"voice"},"uri","tel:+49 9831 5050"],["email",{},"text","[email protected]"]]]}]}],"events":[{"eventAction":"registration","eventDate":"2000-08-28T17:13:12Z"},{"eventAction":"expiration","eventDate":"2024-08-28T17:13:12Z"},{"eventAction":"last changed","eventDate":"2023-10-04T08:20:58Z"},{"eventAction":"last update of RDAP database","eventDate":"2023-10-25T06:07:14Z"}],"secureDNS":{"delegationSigned":false},"nameservers":[{"objectClassName":"nameserver","ldhName":"NS01.LWLDNS.DE"},{"objectClassName":"nameserver","ldhName":"NS02.LWLDNS.DE"},{"objectClassName":"nameserver","ldhName":"NS03.LWLDNS.DE"},{"objectClassName":"nameserver","ldhName":"NS04.LWLDNS.COM"},{"objectClassName":"nameserver","ldhName":"NS05.LWLDNS.COM"}],"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.lwlcom.net, before any redirect: caching, server and policy headers.
Four timed TCP connections to port 443 from CubDomain's servers.
CubDomain is not affiliated with lwlcom.net. 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.