Is lelivros.love a scam? Default Site | scam check & legit verdict

First scanned: June 2, 2026

91 /100
Safe
Registrar NAMECHEAP
Age 3,361 days
Country US
IP address 192.210.137.140

Is lelivros.love down?

lelivros.love is not loading right now.

Last updated: June 4, 2026, 12:21 am (just now)

HTTP
121 ms · cURL error 35: error:0A000458:SSL routines::tlsv1 unrecognized name
DNS
20 ms · 192.210.137.140
SSL
connect failed
Status
Down
just now
Multi-region check · availability from 7 locations

Is lelivros.love a scam?

Based on public data, lelivros.love looks legitimate — no major scam red flags so far.

Warning signs from public databases

How major reputation databases see this domain.

Google Safe Browsing safe
URLhaus Clean
Spamhaus DBL Not listed
AbuseIPDB 0% confidence
AlienVault OTX No pulses

Scam check summary

Plain-language read on what these signals mean for everyday users.

Is lelivros.love a scam? Maybe. While the site has a decent trust score and has not been flagged by security databases, its hidden ownership and lack of detail raise concerns for anyone considering a purchase or sign-up.

Several red flags are present with lelivros.love. The domain is relatively young, having been registered in 2017, which can be riskier for online shoppers. The WHOIS information is hidden behind a privacy service, making it difficult to verify who owns the site. Additionally, while the hosting company is established, the site lacks a professional setup, as indicated by its generic title and missing essential files like a sitemap or robots.txt.

On the positive side, the site has a good trust score of 91 out of 100, and it hasn’t been flagged by any virus or spam detection services. This suggests that, at least from a security standpoint, lelivros.love is currently safe to browse. However, the overall data is thin and doesn’t provide a strong foundation for trust.

What should you do? It’s best to proceed with caution if you’re thinking about buying from lelivros.love. Be wary of potential risks like fake products or phishing attempts, especially given the lack of transparency about the site’s ownership. Always prioritize your safety when shopping online.

Full technical report

WHOIS, DNS, hosting and SEO breakdown.

91/100
Verdict: Safe
Scanned 2026-06-02 22:17:57

Is lelivros.love Safe?

Yes — lelivros.love appears safe to visit based on our automated security checks.

Likely safe

Is lelivros.love Scam or legit?

No — based on our automated checks, lelivros.love does NOT show common scam signals and appears legitimate.

General information

Domain name lelivros.love
Registrar NAMECHEAP ↗ · IANA #1068
Registrar abuse contact [email protected] · +1.3102593259
Registration date2017-03-20T03:42:37.000Z
Expiration date 2028-03-20T23:59:59.000Z
Registrant country
WHOIS owner Hidden identity withheld via Cloudflare Privacy
Domain age 3361 days
IP address 192.210.137.140
Hosted in Marietta, US
Hosting provider RackNerd LLC
Tranco rank #2,604,052 Top 1M (as of 2026-06-01) · free Alexa-replacement from tranco-list.eu

Google search preview

lelivros.love
Default Site

Security & safety

Google Safe BrowsingSAFE
VirusTotal 0 / 0 engines flagged
URLhaus Not listed
Spamhaus DBL Not listed
AbuseIPDB confidence 0/100
AlienVault OTX 0 threat pulses

Abuse signals (AbuseIPDB)

0/100 confidence
Total reports (90 days)0
Distinct reporters0 (unique users — higher = stronger signal)
Usage typeData Center/Web Hosting/Transit

DNS records

A192.210.137.140 TTL 300
NStom.ns.cloudflare.com
NSdina.ns.cloudflare.com

SEO analysis

Title tag "Default Site" (12 chars)
Too short.
Meta description "" (0 chars)
Too short / missing.
H1 tagsCongratulations!
H2 tags
Site loading time0.08s
robots.txt Missing
sitemap.xml Missing
Favicon Missing
Broken links 0
Images 0 total, 0 missing ALT
Flash Not used
iFrames / frames0
Google AnalyticsNot detected
Google AdSense Not detected
CSS files1 files — 1 / 1 minified
JS files0 files
External links1
Internal links0

Most common keywords

started 2 nginx 2 proxy 2 manager 2 congratulations 1 successfully 1 seeing 1 site 1 then 1 trying 1