diredesires.com
Domain report: WHOIS, DNS, hosting, SSL and safety. Checked .
Online · 200Family DNS blockedSSL: 49 days left8 years old
60
diredesires.com was registered on 22 Nov 2017 via Global Domains International, Inc. DBA DomainCostClub.com and the registry expiry is 22 Nov 2026. WHOIS data came from RDAP at https://rdap.verisign.com/com/v1/domain/diredesires.com.
diredesires.com publishes 2 nameservers. DNSSEC is not signed.
diredesires.com has 2 IPv4 addresses (104.21.76.10, 172.67.184.205) and 2 IPv6 addresses (2606:4700:3030::6815:4c0a, 2606:4700:3032::ac43:b8cd). The geolocation database places 104.21.76.10 in Toronto, Canada.
The TLS certificate from YE1 is valid and has 49 days left (TLS 1.3). The homepage answered HTTP 200.
Tech detection named C3.js, Cloudflare, Google Analytics, HTTP/3, Next.js, Node.js, React and Webpack. The fingerprints ran on the homepage that was already downloaded.
Domain · RDAP/WHOIS
diredesires.com was registered on 22 Nov 2017 via Global Domains International, Inc. DBA DomainCostClub.com. The registry returned 1 status value and 2 nameservers from https://rdap.verisign.com/com/v1/domain/diredesires.com.
| Registered | since 22 Nov 2017 |
|---|---|
| Created | 22 November 2017 |
| Updated | 25 May 2026 |
| Expires | 22 November 2026 |
| Registrar | Global Domains International, Inc. DBA DomainCostClub.com |
| Status | client transfer prohibited |
| Nameservers | alina.ns.cloudflare.com, tate.ns.cloudflare.com |
| DNSSEC | no |
| Source | https://rdap.verisign.com/com/v1/domain/diredesires.com |
diredesires.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 alina.ns.cloudflare.com is published for diredesires.com in the registration record from https://rdap.verisign.com/com/v1/domain/diredesires.com.
Nameserver tate.ns.cloudflare.com is published for diredesires.com in the registration record from https://rdap.verisign.com/com/v1/domain/diredesires.com.
DNS
diredesires.com has 4 address records, 1 mail exchanger and 2 nameservers, measured at 1.1.1.1:53.
| A | 104.21.76.10, 172.67.184.205 |
|---|---|
| AAAA | 2606:4700:3030::6815:4c0a, 2606:4700:3032::ac43:b8cd |
| NS | alina.ns.cloudflare.com, tate.ns.cloudflare.com |
| MX | mx.yourpaysitepartner.com (10) |
| SPF | present |
| DMARC | present |
| CAA | — |
| Wildcard | off |
| DNSSEC | not signed |
| Resolver | 1.1.1.1:53 |
The SPF text record at diredesires.com is "v=spf1 include:amazonses.com include:spf.privateemail.com include:_spf.westbill.com ip4:99.192.223.243 ip4:99.192.254.54 ip4:99.192.254.55 ip4:99.192.254.56 ip4:74.206.162.148 ~all".
The DMARC text record at _dmarc.diredesires.com is "v=DMARC1;p=quarantine; fo=1; rua=mailto:[email protected];ruf=mailto:[email protected]".
IPv4 address 104.21.76.10 answers for diredesires.com at resolver 1.1.1.1:53.
IPv4 address 172.67.184.205 answers for diredesires.com at resolver 1.1.1.1:53.
IPv6 address 2606:4700:3030::6815:4c0a answers for diredesires.com at resolver 1.1.1.1:53.
IPv6 address 2606:4700:3032::ac43:b8cd answers for diredesires.com at resolver 1.1.1.1:53.
Mail exchanger mx.yourpaysitepartner.com has preference 10.
Hosting and geo
diredesires.com is placed in Toronto, Canada by the local geolocation database (db-ip).
| Address | 104.21.76.10 |
|---|---|
| Country | Canada |
| City | Toronto |
| Source | db-ip |
SSL/TLS
The certificate for diredesires.com is valid, with 49 days left and 2 subject alternative names. Source: tls:443.
| Issuer | YE1 |
|---|---|
| Subject | diredesires.com |
| Valid from | 20 September 2026 |
| Valid until | 19 December 2026 |
| Days left | 49 |
| SAN count | 2 |
| Protocol | TLS 1.3 |
| Source | tls:443 |
Subject alternative names: *.diredesires.com, diredesires.com.
Tech stack
Tech detection checked the fetched homepage and named 8 products. Source: wappalyzergo.
- C3.js · JavaScript libraries
- Cloudflare · CDN
- Google Analytics · Analytics
- HTTP/3 · Miscellaneous
- Next.js · JavaScript frameworks, Web frameworks
- Node.js · Programming languages
- React · JavaScript frameworks
- Webpack · Miscellaneous
C3.js is filed under JavaScript libraries.
Cloudflare is filed under CDN.
Google Analytics is filed under Analytics.
HTTP/3 is filed under Miscellaneous.
Next.js is filed under JavaScript frameworks, Web frameworks.
Node.js is filed under Programming languages.
React is filed under JavaScript frameworks.
Webpack is filed under Miscellaneous.
On-page checks
The homepage returned HTTP 200 in 493 ms. The target title is 49 characters and the page has 1 H1 heading.
| Status | 200 |
|---|---|
| TTFB | 493 ms |
| Title length | 49 yes |
| Quoted title | "Ebony BBC Porn with Real Chemistry | Dire Desires" |
| Meta description | "Watch exclusive ebony and BBC scenes shot with real chemistry. New HD videos every week, plus models, series, and vault clips — join Dire Desires today." yes |
| H1 count | 1 |
| HSTS | no no |
| CSP | no |
| X-Frame-Options | — |
| Robots meta | — |
| Canonical | https://diredesires.com/ |
| Language | — |
| Links | 195 |
| Images | 56 |
| Favicon | yes |
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 diredesires.com is blocked, and URLhaus is clear. Source: family DNS and local lists.
| Family DNS | blocked |
|---|---|
| URLhaus | clear |
| UT1 | — |
| Web Risk | not run |
| Source | family DNS and local lists |
| HSTS | no |
| CSP | no |
Cloudflare family DNS returned a block for diredesires.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 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
First checked on 30 October 2026; changes will appear here.
Questions
Is diredesires.com safe?
Cloudflare family DNS returned a block for diredesires.com. That resolver covers adult and malware names.
Who hosts diredesires.com?
diredesires.com is placed in Toronto, Canada.
When does diredesires.com expire?
diredesires.com expires on 22 November 2026 according to https://rdap.verisign.com/com/v1/domain/diredesires.com.
Who owns diredesires.com?
The registry did not return a person or a company for diredesires.com. RDAP often redacts the registrant. The registrar on file is Global Domains International, Inc. DBA DomainCostClub.com.
Sources
- RDAP source https://rdap.verisign.com/com/v1/domain/diredesires.com at 2026-10-30T13:51:46Z
- DNS source 1.1.1.1:53 at 2026-10-30T13:51:46Z
- TLS source tls:443 at 2026-10-30T13:51:46Z
- HTTP source https://diredesires.com/ at 2026-10-30T13:51:46Z
- Tech source wappalyzergo at 2026-10-30T13:51:46Z
- Geo source db-ip at 2026-10-30T13:51:46Z
- Safety source family DNS and local lists at 2026-10-30T13:51:46Z
Related reports
No other indexable reports share this TLD, host, or registrar yet.
.com Global Domains International, Inc. DBA DomainCostClub.com
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.
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.