livehotty.com

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

Online · 200Family DNS blockedSSL: 49 days left19 years old

One re-check per domain each UTC day.

75

livehotty.com was registered on 22 Jun 2007 via GoDaddy.com, LLC and the registry expiry is 22 Jun 2027. WHOIS data came from RDAP at https://rdap.verisign.com/com/v1/domain/livehotty.com.

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

livehotty.com has 8 IPv4 addresses (207.246.147.189, 207.246.147.190, 207.246.147.193, 207.246.147.194, 207.246.147.247, 207.246.147.248, 207.246.147.249, 207.246.147.250). The geolocation database places 207.246.147.189 in New York, United States.

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

Tech detection named HSTS and Nginx. The fingerprints ran on the homepage that was already downloaded.

Domain · RDAP/WHOIS

livehotty.com was registered on 22 Jun 2007 via GoDaddy.com, LLC. The registry returned 4 status values and 2 nameservers from https://rdap.verisign.com/com/v1/domain/livehotty.com.

Registeredsince 22 Jun 2007
Created22 June 2007
Updated22 June 2025
Expires22 June 2027
RegistrarGoDaddy.com, LLC
Statusclient delete prohibited, client renew prohibited, client transfer prohibited, client update prohibited
Nameserversns1.flyingcroc.net, ns2.flyingcroc.net
DNSSECno
Sourcehttps://rdap.verisign.com/com/v1/domain/livehotty.com

livehotty.com carries the status "client delete prohibited". The registrar has asked the registry to refuse a delete. This is an EPP status on the domain object. It does not say the website is safe, and it does not name the person who registered it.

livehotty.com carries the status "client renew prohibited". The registrar has asked the registry to refuse a renewal. The expiry date still stands until a different status is set.

livehotty.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.

livehotty.com carries the status "client update prohibited". The registrar has asked the registry to refuse updates to the domain object. Contact and nameserver changes wait until the lock is lifted by the registrar of record.

Nameserver ns1.flyingcroc.net is published for livehotty.com in the registration record from https://rdap.verisign.com/com/v1/domain/livehotty.com.

Nameserver ns2.flyingcroc.net is published for livehotty.com in the registration record from https://rdap.verisign.com/com/v1/domain/livehotty.com.

DNS

livehotty.com has 8 address records, 1 mail exchanger and 2 nameservers, measured at 1.1.1.1:53.

A207.246.147.189, 207.246.147.190, 207.246.147.193, 207.246.147.194, 207.246.147.247, 207.246.147.248, 207.246.147.249, 207.246.147.250
AAAA—
NSns1.flyingcroc.net, ns2.flyingcroc.net
MXinbound.mail.naiadsystems.com (10)
SPFpresent
DMARCpresent
CAA—
Wildcardoff
DNSSECnot signed
Resolver1.1.1.1:53

The SPF text record at livehotty.com is "v=spf1 include:localspf.streamate.com include:liveperson.streamate.com include:amazonses.com include:_spf.google.com ip4:75.101.166.170/32 ~all".

The DMARC text record at _dmarc.livehotty.com is "v=DMARC1; p=quarantine; pct=100; rua=mailto:[email protected]; aspf=r; adkim=r; ruf=mailto:[email protected];".

IPv4 address 207.246.147.189 answers for livehotty.com at resolver 1.1.1.1:53.

IPv4 address 207.246.147.190 answers for livehotty.com at resolver 1.1.1.1:53.

IPv4 address 207.246.147.193 answers for livehotty.com at resolver 1.1.1.1:53.

IPv4 address 207.246.147.194 answers for livehotty.com at resolver 1.1.1.1:53.

IPv4 address 207.246.147.247 answers for livehotty.com at resolver 1.1.1.1:53.

IPv4 address 207.246.147.248 answers for livehotty.com at resolver 1.1.1.1:53.

IPv4 address 207.246.147.249 answers for livehotty.com at resolver 1.1.1.1:53.

IPv4 address 207.246.147.250 answers for livehotty.com at resolver 1.1.1.1:53.

Mail exchanger inbound.mail.naiadsystems.com has preference 10.

Hosting and geo

livehotty.com is placed in New York, United States by the local geolocation database (db-ip).

Address207.246.147.189
CountryUnited States
CityNew York
Sourcedb-ip

IP geolocation by DB-IP

SSL/TLS

The certificate for livehotty.com is valid, with 49 days left and 2 subject alternative names. Source: tls:443.

IssuerYR2
Subjectlivehotty.com
Valid from21 September 2026
Valid until20 December 2026
Days left49
SAN count2
ProtocolTLS 1.3
Sourcetls:443

Subject alternative names: livehotty.com, www.livehotty.com.

Tech stack

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

  • HSTS · Security
  • Nginx · Web servers, Reverse proxies

HSTS is filed under Security.

Nginx is filed under Web servers, Reverse proxies.

On-page checks

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

Status200
TTFB178 ms
Title length36 yes
Quoted title"livehotty.com - - Web Cam Video Chat"
Meta description"Experience the best live adult cams on LiveHotty. Chat with thousands of real models in stunning HD, explore free shows, or go private. Join free today!" yes
H1 count0
HSTSyes yes
CSPyes
X-Frame-Options—
Robots meta—
Canonicalhttps://livehotty.com
Language—
Links0
Images1
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 livehotty.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
HSTSyes
CSPyes

Cloudflare family DNS returned a block for livehotty.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 10 of 20. SPF, DMARC, CAA, and DNSSEC are five points each.

Security headers 15 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 New York.
  • October 2026: geo country changed from empty to United States.

Questions

Is livehotty.com safe?

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

Who hosts livehotty.com?

livehotty.com is placed in New York, United States.

When does livehotty.com expire?

livehotty.com expires on 22 June 2027 according to https://rdap.verisign.com/com/v1/domain/livehotty.com.

Who owns livehotty.com?

The registry did not return a person or a company for livehotty.com. RDAP often redacts the registrant. The registrar on file is GoDaddy.com, LLC.

Sources

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

Methodology

Related reports

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

.com GoDaddy.com, LLC

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.