asiansexyshemales.com

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

OfflineFamily DNS blockedSSL: -1 days left23 years old

One re-check per domain each UTC day.

20

asiansexyshemales.com was registered on 23 Jan 2003 via Spaceship, Inc. and the registry expiry is 17 Jun 2027. WHOIS data came from RDAP at https://rdap.verisign.com/com/v1/domain/asiansexyshemales.com.

asiansexyshemales.com publishes 3 nameservers. DNSSEC is not signed.

asiansexyshemales.com has 1 IPv4 address (217.182.185.88). The geolocation database places 217.182.185.88 in Roubaix, France.

The TLS certificate from YR1 is not valid (TLS 1.3).

Domain · RDAP/WHOIS

asiansexyshemales.com was registered on 23 Jan 2003 via Spaceship, Inc.. The registry returned 1 status value and 3 nameservers from https://rdap.verisign.com/com/v1/domain/asiansexyshemales.com.

Registeredsince 23 Jan 2003
Created23 January 2003
Updated21 June 2026
Expires17 June 2027
RegistrarSpaceship, Inc.
Statusclient transfer prohibited
Nameserversns1.onlydomains.com, ns2.onlydomains.com, ns3.onlydomains.com
DNSSECno
Sourcehttps://rdap.verisign.com/com/v1/domain/asiansexyshemales.com

asiansexyshemales.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.onlydomains.com is published for asiansexyshemales.com in the registration record from https://rdap.verisign.com/com/v1/domain/asiansexyshemales.com.

Nameserver ns2.onlydomains.com is published for asiansexyshemales.com in the registration record from https://rdap.verisign.com/com/v1/domain/asiansexyshemales.com.

Nameserver ns3.onlydomains.com is published for asiansexyshemales.com in the registration record from https://rdap.verisign.com/com/v1/domain/asiansexyshemales.com.

DNS

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

A217.182.185.88
AAAA—
NSns1.onlydomains.com, ns2.onlydomains.com, ns3.onlydomains.com
MXmail.asiansexyshemales.com (10)
SPFpresent
DMARCabsent
CAA—
Wildcardoff
DNSSECnot signed
Resolver1.1.1.1:53

The SPF text record at asiansexyshemales.com is "v=spf1 include:spf.efwd.registrar-servers.com ~all".

IPv4 address 217.182.185.88 answers for asiansexyshemales.com at resolver 1.1.1.1:53.

Mail exchanger mail.asiansexyshemales.com has preference 10.

Hosting and geo

asiansexyshemales.com is placed in Roubaix, France by the local geolocation database (db-ip).

Address217.182.185.88
CountryFrance
CityRoubaix
Sourcedb-ip

IP geolocation by DB-IP

SSL/TLS

The certificate for asiansexyshemales.com is not valid, with -1 days left and 1 subject alternative name. Source: tls:443.

IssuerYR1
Subjectasiansexyshemales.com
Valid from31 July 2026
Valid until29 October 2026
Days left-1
SAN count1
ProtocolTLS 1.3
Sourcetls:443

Subject alternative names: asiansexyshemales.com.

Validation result: certificate did not validate

Tech stack

Tech detection did not run.

Checkedno
Sourcewappalyzergo

On-page checks

The homepage fetch did not return a status code.

Statusnone

Get "https://asiansexyshemales.com/": tls: failed to verify certificate: x509: certificate has expired or is not yet valid: current time 2026-10-30T13:45:27Z is after 2026-10-29T20:34:53Z

Security

Family DNS for asiansexyshemales.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 asiansexyshemales.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 10 of 25. DNS answer plus a homepage status in the 2xx or 3xx range.

TLS 0 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 Roubaix.
  • October 2026: geo country changed from empty to France.

Questions

Is asiansexyshemales.com safe?

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

Who hosts asiansexyshemales.com?

asiansexyshemales.com is placed in Roubaix, France.

When does asiansexyshemales.com expire?

asiansexyshemales.com expires on 17 June 2027 according to https://rdap.verisign.com/com/v1/domain/asiansexyshemales.com.

Who owns asiansexyshemales.com?

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

Sources

  • RDAP source https://rdap.verisign.com/com/v1/domain/asiansexyshemales.com at 2026-10-30T13:45:27Z
  • DNS source 1.1.1.1:53 at 2026-10-30T13:45:27Z
  • TLS source tls:443 at 2026-10-30T13:45:27Z
  • HTTP source https://asiansexyshemales.com/ at 2026-10-30T13:45:27Z
  • Tech source not available at 2026-10-30T13:45:27Z
  • Geo source db-ip at 2026-10-30T13:45:27Z
  • Safety source family DNS and local lists at 2026-10-30T13:45:27Z

Methodology

Related reports

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

.com Spaceship, 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.