lenticularfans.com is hosted on AS16509 in United States. Its SSL certificate from "GoDaddy.com expired on 17 May 2025, and the site does not support HTTP/3.
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.
No similar domains registered in the last 90 days.
From CubDomain's daily newly registered domains. Similar doesn't mean malicious.
Is lenticularfans.com’s name taken on other extensions?
Every IP address lenticularfans.com resolves to, and where it's hosted.
| Host | IPv4 address | TTL |
|---|---|---|
| lenticularfans.com | 15.197.148.33 | 600 |
| lenticularfans.com | 3.33.130.190 | 600 |
| Host | Name server | TTL |
|---|---|---|
| lenticularfans.com | ns23.domaincontrol.com | 3600 |
| lenticularfans.com | ns24.domaincontrol.com | 3600 |
| Host | Start of authority | TTL |
|---|---|---|
| lenticularfans.com | ns23.domaincontrol.com dns.jomax.net 2023091900 28800 7200 604800 600 | 3600 |
Other domains served from 15.197.148.33. Normal for shared hosting and CDNs.
No reviews yet. Used lenticularfans.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.
lenticularfans.com has no community safety rating yet. Its SSL certificate expired on 17 May 2025. See Security →
lenticularfans.com is served from 2 IP addresses, mainly on AS16509 in United States. See Hosting →
The first response from http://www.lenticularfans.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 lenticularfans.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.
When the site first appeared, and what has changed since.
We record what changes from the next time this report is refreshed.
Found in public certificate transparency logs.
Searching the certificate transparency logs… This can take up to a minute.