lusthive.com

Domain report: WHOIS, DNS, hosting, SSL and safety. Checked .

Online · 200Family DNS blockedSSL: 62 days left6 years old

One re-check per domain each UTC day.

55

lusthive.com was registered on 2 Jun 2020 via NameCheap, Inc. and the registry expiry is 2 Jun 2027. WHOIS data came from RDAP at https://rdap.verisign.com/com/v1/domain/lusthive.com.

lusthive.com publishes 2 nameservers. DNSSEC is not signed.

lusthive.com has 1 IPv4 address (23.80.82.107). The geolocation database places 23.80.82.107 in Los Angeles (Westlake), United States.

The TLS certificate from YE2 is valid and has 62 days left (TLS 1.3). The homepage answered HTTP 200.

Tech detection named Apache HTTP Server and PHP. The fingerprints ran on the homepage that was already downloaded.

Domain · RDAP/WHOIS

lusthive.com was registered on 2 Jun 2020 via NameCheap, Inc.. The registry returned 1 status value and 2 nameservers from https://rdap.verisign.com/com/v1/domain/lusthive.com.

Registeredsince 2 Jun 2020
Created2 June 2020
Updated6 June 2026
Expires2 June 2027
RegistrarNameCheap, Inc.
Statusclient transfer prohibited
Nameserversns1.vs6794.jethostvps.com, ns2.vs6794.jethostvps.com
DNSSECno
Sourcehttps://rdap.verisign.com/com/v1/domain/lusthive.com

lusthive.com carries the status "client transfer prohibited". The registrar has asked the registry to refuse a transfer to another registrar. The status is a lock on the domain object. It is not evidence about the content of the site.

Nameserver ns1.vs6794.jethostvps.com is published for lusthive.com in the registration record from https://rdap.verisign.com/com/v1/domain/lusthive.com.

Nameserver ns2.vs6794.jethostvps.com is published for lusthive.com in the registration record from https://rdap.verisign.com/com/v1/domain/lusthive.com.

DNS

lusthive.com has 1 address record, 1 mail exchanger and 2 nameservers, measured at 1.1.1.1:53.

A23.80.82.107
AAAA—
NSns1.amerinoc.com, ns2.amerinoc.com
MXmail.lusthive.com (10)
SPFpresent
DMARCabsent
CAA—
Wildcardoff
DNSSECnot signed
Resolver1.1.1.1:53

The SPF text record at lusthive.com is "v=spf1 a mx ip4:23.80.82.107 ~all".

IPv4 address 23.80.82.107 answers for lusthive.com at resolver 1.1.1.1:53.

Mail exchanger mail.lusthive.com has preference 10.

Hosting and geo

lusthive.com is placed in Los Angeles (Westlake), United States by the local geolocation database (db-ip).

Address23.80.82.107
CountryUnited States
CityLos Angeles (Westlake)
Sourcedb-ip

IP geolocation by DB-IP

SSL/TLS

The certificate for lusthive.com is valid, with 62 days left and 6 subject alternative names. Source: tls:443.

IssuerYE2
Subjectlusthive.com
Valid from4 October 2026
Valid until2 January 2027
Days left62
SAN count6
ProtocolTLS 1.3
Sourcetls:443

Subject alternative names: ftp.lusthive.com, lusthive.com, mail.lusthive.com, pop.lusthive.com, smtp.lusthive.com, www.lusthive.com.

Tech stack

Tech detection checked the fetched homepage and named 2 products. Source: wappalyzergo.

  • Apache HTTP Server · Web servers
  • PHP · Programming languages

Apache HTTP Server is filed under Web servers.

PHP is filed under Programming languages.

On-page checks

The homepage returned HTTP 200 in 159 ms. The target title is 16 characters and the page has 0 H1 headings.

Status200
TTFB159 ms
Title length16 yes
Quoted title"Redgifs Trending"
Meta descriptionnone no
H1 count0
HSTSno no
CSPno
X-Frame-Options—
Robots meta—
Canonical—
Language—
Links222
Images0
Faviconyes

The quoted title and meta description are measurements of the other site. They are not this page's title or description.

Security

Family DNS for lusthive.com is blocked, and URLhaus is clear. Source: family DNS and local lists.

Family DNSblocked
URLhausclear
UT1—
Web Risknot run
Sourcefamily DNS and local lists
HSTSno
CSPno

Cloudflare family DNS returned a block for lusthive.com. That resolver covers adult and malware names.

Google Web Risk did not run. No API key is configured, and this report does not invent a clean result from that service.

Score breakdown

Availability 25 of 25. DNS answer plus a homepage status in the 2xx or 3xx range.

TLS 20 of 20. A valid certificate, with extra points when it has at least 14 days left.

DNS hygiene 5 of 20. SPF, DMARC, CAA, and DNSSEC are five points each.

Security headers 0 of 15. HSTS, CSP, and X-Frame-Options or CSP frame-ancestors.

Safety lists 0 of 15. Points only when the checks ran and came back clean. Unknown is not clean.

Domain age 5 of 5. Five points at one year, two points at 30 days.

Change history

  • October 2026: geo city changed from empty to Los Angeles (Westlake).
  • October 2026: geo country changed from empty to United States.

Questions

Is lusthive.com safe?

Cloudflare family DNS returned a block for lusthive.com. That resolver covers adult and malware names.

Who hosts lusthive.com?

lusthive.com is placed in Los Angeles (Westlake), United States.

When does lusthive.com expire?

lusthive.com expires on 2 June 2027 according to https://rdap.verisign.com/com/v1/domain/lusthive.com.

Who owns lusthive.com?

The registry did not return a person or a company for lusthive.com. RDAP often redacts the registrant. The registrar on file is NameCheap, Inc..

Sources

  • RDAP source https://rdap.verisign.com/com/v1/domain/lusthive.com at 2026-10-30T14:02:20Z
  • DNS source 1.1.1.1:53 at 2026-10-30T14:02:20Z
  • TLS source tls:443 at 2026-10-30T14:02:20Z
  • HTTP source https://lusthive.com/ at 2026-10-30T14:02:20Z
  • Tech source wappalyzergo at 2026-10-30T14:02:20Z
  • Geo source db-ip at 2026-10-30T14:02:20Z
  • Safety source family DNS and local lists at 2026-10-30T14:02:20Z

Methodology

Related reports

No other indexable reports share this TLD, host, or registrar yet.

.com NameCheap, Inc.

Owner of this site?

Ask for a correction or for the report to be removed from search. Public DNS facts stay on the page. An optional badge is not inserted for you.

Removal policy

How to read this report

The sentences under each heading are filled from the latest snapshot. If a collector had nothing to say, that sentence is left out. The target site's own title and meta description, when shown, are quoted as measurements. They are not this page's title. Change history only lists a difference between two snapshots, so the first check starts the clock and later edits are the history. A malware blocklist is the only reason the homepage body is skipped. That fact stays on the report. It does not by itself drop the page from the sitemap or from related-report links.