aisex.club
Domain report: WHOIS, DNS, hosting, SSL and safety. Checked .
Online · 200SafeSSL: 77 days leftUnder 1 year old
77
aisex.club was registered on 10 Dec 2025 via Dynadot Inc and the registry expiry is 10 Dec 2026. WHOIS data came from RDAP at https://rdap.nic.club/domain/aisex.club.
aisex.club publishes 2 nameservers. DNSSEC is not signed.
aisex.club has 1 IPv4 address (54.215.31.113). The geolocation database places 54.215.31.113 in San Jose, United States.
The TLS certificate from YR2 is valid and has 77 days left (TLS 1.3). The homepage answered HTTP 200.
Tech detection named HSTS and HTTP/3. The fingerprints ran on the homepage that was already downloaded.
No safety warning was recorded for aisex.club in the checks that ran.
Domain · RDAP/WHOIS
aisex.club was registered on 10 Dec 2025 via Dynadot Inc. The registry returned 1 status value and 2 nameservers from https://rdap.nic.club/domain/aisex.club.
| Registered | since 10 Dec 2025 |
|---|---|
| Created | 10 December 2025 |
| Updated | 21 April 2026 |
| Expires | 10 December 2026 |
| Registrar | Dynadot Inc |
| Status | client transfer prohibited |
| Nameservers | ns1.dyna-ns.net, ns2.dyna-ns.net |
| DNSSEC | no |
| Source | https://rdap.nic.club/domain/aisex.club |
aisex.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 ns1.dyna-ns.net is published for aisex.club in the registration record from https://rdap.nic.club/domain/aisex.club.
Nameserver ns2.dyna-ns.net is published for aisex.club in the registration record from https://rdap.nic.club/domain/aisex.club.
DNS
aisex.club has 1 address record, 0 mail exchangers and 2 nameservers, measured at 1.1.1.1:53.
| A | 54.215.31.113 |
|---|---|
| AAAA | — |
| NS | ns1.dyna-ns.net, ns2.dyna-ns.net |
| MX | — |
| SPF | absent |
| DMARC | absent |
| CAA | — |
| Wildcard | off |
| DNSSEC | not signed |
| Resolver | 1.1.1.1:53 |
IPv4 address 54.215.31.113 answers for aisex.club at resolver 1.1.1.1:53.
Hosting and geo
aisex.club is placed in San Jose, United States by the local geolocation database (db-ip).
| Address | 54.215.31.113 |
|---|---|
| Country | United States |
| City | San Jose |
| Source | db-ip |
SSL/TLS
The certificate for aisex.club is valid, with 77 days left and 2 subject alternative names. Source: tls:443.
| Issuer | YR2 |
|---|---|
| Subject | aisex.club |
| Valid from | 18 October 2026 |
| Valid until | 16 January 2027 |
| Days left | 77 |
| SAN count | 2 |
| Protocol | TLS 1.3 |
| Source | tls:443 |
Subject alternative names: *.aisex.club, aisex.club.
Tech stack
Tech detection checked the fetched homepage and named 2 products. Source: wappalyzergo.
- HSTS · Security
- HTTP/3 · Miscellaneous
HSTS is filed under Security.
HTTP/3 is filed under Miscellaneous.
On-page checks
The homepage returned HTTP 200 in 162 ms. The target title is 59 characters and the page has 0 H1 headings.
| Status | 200 |
|---|---|
| TTFB | 162 ms |
| Title length | 59 yes |
| Quoted title | "Mehmet BOZKUŞ (@memetbozkus) • Instagram photos and videos" |
| Meta description | "11K Followers, 513 Following, 48 Posts - Mehmet BOZKUŞ (@memetbozkus) on Instagram: "Domain Investor 📍Mardin - İstanbul . Kiripto Founder & Token Developer"" yes |
| H1 count | 0 |
| HSTS | yes yes |
| CSP | yes |
| X-Frame-Options | DENY |
| Robots meta | noarchive, noimageindex |
| Canonical | https://www.instagram.com/memetbozkus/ |
| Language | en |
| Links | 40 |
| Images | 16 |
| 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 aisex.club is clear, and URLhaus is clear. Source: family DNS and local lists.
| Family DNS | clear |
|---|---|
| URLhaus | clear |
| UT1 | — |
| Web Risk | not run |
| Source | family DNS and local lists |
| HSTS | yes |
| CSP | yes |
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 0 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 15 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: rdap created changed from empty to 2025-12-10T04:57:31Z.
- October 2026: rdap dnssec changed from empty to no.
- October 2026: rdap expires changed from empty to 2026-12-10T04:57:31Z.
- October 2026: rdap nameservers changed from empty to ns1.dyna-ns.net,ns2.dyna-ns.net.
- October 2026: rdap registered changed from unknown to yes.
- October 2026: rdap registrar changed from empty to Dynadot Inc.
- October 2026: rdap statuses changed from empty to client transfer prohibited.
- October 2026: rdap updated changed from empty to 2026-04-21T16:04:26Z.
- October 2026: geo city changed from empty to San Jose.
- October 2026: geo country changed from empty to United States.
Questions
Is aisex.club safe?
The checks that ran did not produce a safety warning, and a score is not a promise that the site is safe.
Who hosts aisex.club?
aisex.club is placed in San Jose, United States.
When does aisex.club expire?
aisex.club expires on 10 December 2026 according to https://rdap.nic.club/domain/aisex.club.
Who owns aisex.club?
The registry did not return a person or a company for aisex.club. RDAP often redacts the registrant. The registrar on file is Dynadot Inc.
Sources
- RDAP source https://rdap.nic.club/domain/aisex.club at 2026-10-30T13:36:46Z
- DNS source 1.1.1.1:53 at 2026-10-30T13:36:46Z
- TLS source tls:443 at 2026-10-30T13:36:46Z
- HTTP source https://aisex.club/ at 2026-10-30T13:36:46Z
- Tech source wappalyzergo at 2026-10-30T13:36:46Z
- Geo source db-ip at 2026-10-30T13:36:46Z
- Safety source family DNS and local lists at 2026-10-30T13:36:46Z
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.