sexdiary.club
Domain report: WHOIS, DNS, hosting, SSL and safety. Checked .
OfflineFamily DNS blockedUnder 1 year old
12
sexdiary.club was registered on 21 Aug 2026 via Sav.com, LLC - 12 and the registry expiry is 21 Aug 2027. WHOIS data came from RDAP at https://rdap.nic.club/domain/sexdiary.club.
sexdiary.club publishes 2 nameservers. DNSSEC is not signed.
sexdiary.club has 5 IPv4 addresses (139.162.174.209, 139.162.181.76, 172.104.149.86, 172.104.203.186, 172.104.251.198) and 5 IPv6 addresses (2a01:7e01::2000:dff:fec1:5cdb, 2a01:7e01::f03c:95ff:fe00:2692, 2a01:7e01::f03c:95ff:fe91:5d91, 2a01:7e01::f03c:95ff:feeb:9d4b, 2a01:7e01::f03c:95ff:feed:783e). The geolocation database places 139.162.174.209 in Frankfurt am Main, Germany.
Domain · RDAP/WHOIS
sexdiary.club was registered on 21 Aug 2026 via Sav.com, LLC - 12. The registry returned 1 status value and 2 nameservers from https://rdap.nic.club/domain/sexdiary.club.
| Registered | since 21 Aug 2026 |
|---|---|
| Created | 21 August 2026 |
| Updated | 20 October 2026 |
| Expires | 21 August 2027 |
| Registrar | Sav.com, LLC - 12 |
| Status | client transfer prohibited |
| Nameservers | yangyang.ns.giantpanda.com, lunlun.ns.giantpanda.com |
| DNSSEC | no |
| Source | https://rdap.nic.club/domain/sexdiary.club |
sexdiary.club 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 yangyang.ns.giantpanda.com is published for sexdiary.club in the registration record from https://rdap.nic.club/domain/sexdiary.club.
Nameserver lunlun.ns.giantpanda.com is published for sexdiary.club in the registration record from https://rdap.nic.club/domain/sexdiary.club.
DNS
sexdiary.club has 10 address records, 0 mail exchangers and 2 nameservers, measured at 1.1.1.1:53.
| A | 139.162.174.209, 139.162.181.76, 172.104.149.86, 172.104.203.186, 172.104.251.198 |
|---|---|
| AAAA | 2a01:7e01::2000:dff:fec1:5cdb, 2a01:7e01::f03c:95ff:fe00:2692, 2a01:7e01::f03c:95ff:fe91:5d91, 2a01:7e01::f03c:95ff:feeb:9d4b, 2a01:7e01::f03c:95ff:feed:783e |
| NS | jiajia.ns.giantpanda.com, meisheng.ns.giantpanda.com |
| MX | — |
| SPF | absent |
| DMARC | absent |
| CAA | — |
| Wildcard | on |
| DNSSEC | not signed |
| Resolver | 1.1.1.1:53 |
IPv4 address 139.162.174.209 answers for sexdiary.club at resolver 1.1.1.1:53.
IPv4 address 139.162.181.76 answers for sexdiary.club at resolver 1.1.1.1:53.
IPv4 address 172.104.149.86 answers for sexdiary.club at resolver 1.1.1.1:53.
IPv4 address 172.104.203.186 answers for sexdiary.club at resolver 1.1.1.1:53.
IPv4 address 172.104.251.198 answers for sexdiary.club at resolver 1.1.1.1:53.
IPv6 address 2a01:7e01::2000:dff:fec1:5cdb answers for sexdiary.club at resolver 1.1.1.1:53.
IPv6 address 2a01:7e01::f03c:95ff:fe00:2692 answers for sexdiary.club at resolver 1.1.1.1:53.
IPv6 address 2a01:7e01::f03c:95ff:fe91:5d91 answers for sexdiary.club at resolver 1.1.1.1:53.
IPv6 address 2a01:7e01::f03c:95ff:feeb:9d4b answers for sexdiary.club at resolver 1.1.1.1:53.
IPv6 address 2a01:7e01::f03c:95ff:feed:783e answers for sexdiary.club at resolver 1.1.1.1:53.
A random label under sexdiary.club also resolved, which means wildcard DNS is on.
Hosting and geo
sexdiary.club is placed in Frankfurt am Main, Germany by the local geolocation database (db-ip).
| Address | 139.162.174.209 |
|---|---|
| Country | Germany |
| City | Frankfurt am Main |
| Source | db-ip |
SSL/TLS
No TLS certificate was read for sexdiary.club on port 443.
| Available | no |
|---|---|
| Source | tls:443 |
remote error: tls: internal error
Tech stack
Tech detection did not run.
| Checked | no |
|---|---|
| Source | wappalyzergo |
On-page checks
The homepage fetch did not return a status code.
| Status | none |
|---|
Get "https://sexdiary.club/": tls: failed to verify certificate: x509: certificate signed by unknown authority
Security
Family DNS for sexdiary.club 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 sexdiary.club. 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 0 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 2 of 5. Five points at one year, two points at 30 days.
Change history
- October 2026: geo city changed from empty to Frankfurt am Main.
- October 2026: geo country changed from empty to Germany.
Questions
Is sexdiary.club safe?
Cloudflare family DNS returned a block for sexdiary.club. That resolver covers adult and malware names.
Who hosts sexdiary.club?
sexdiary.club is placed in Frankfurt am Main, Germany.
When does sexdiary.club expire?
sexdiary.club expires on 21 August 2027 according to https://rdap.nic.club/domain/sexdiary.club.
Who owns sexdiary.club?
The registry did not return a person or a company for sexdiary.club. RDAP often redacts the registrant. The registrar on file is Sav.com, LLC - 12.
Sources
- RDAP source https://rdap.nic.club/domain/sexdiary.club at 2026-10-30T13:37:27Z
- DNS source 1.1.1.1:53 at 2026-10-30T13:37:27Z
- TLS source tls:443 at 2026-10-30T13:37:27Z
- HTTP source https://sexdiary.club/ at 2026-10-30T13:37:27Z
- Tech source not available at 2026-10-30T13:37:27Z
- Geo source db-ip at 2026-10-30T13:37:27Z
- Safety source family DNS and local lists at 2026-10-30T13:37:27Z
Related reports
No other indexable reports share this TLD, host, or registrar yet.
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.