chicktok.app
Domain report: WHOIS, DNS, hosting, SSL and safety. Checked .
67
Domain report: WHOIS, DNS, hosting, SSL and safety. Checked .
67
chicktok.app was registered on 12 Mar 2026 via PDR Ltd. d/b/a PublicDomainRegistry.com and the registry expiry is 12 Mar 2027. WHOIS data came from RDAP at https://pubapi.registry.google/rdap/domain/chicktok.app.
chicktok.app publishes 4 nameservers. DNSSEC is not signed.
chicktok.app has 2 IPv4 addresses (35.157.26.135, 63.176.8.218). The geolocation database places 35.157.26.135 in Frankfurt am Main, Germany.
The TLS certificate from YE2 is valid and has 36 days left (TLS 1.3). The homepage answered HTTP 200.
Tech detection named Clicky, HSTS and Netlify. The fingerprints ran on the homepage that was already downloaded.
No safety warning was recorded for chicktok.app in the checks that ran.
chicktok.app was registered on 12 Mar 2026 via PDR Ltd. d/b/a PublicDomainRegistry.com. The registry returned 1 status value and 4 nameservers from https://pubapi.registry.google/rdap/domain/chicktok.app.
| Registered | since 12 Mar 2026 |
|---|---|
| Created | 12 March 2026 |
| Updated | 17 March 2026 |
| Expires | 12 March 2027 |
| Registrar | PDR Ltd. d/b/a PublicDomainRegistry.com |
| Status | client transfer prohibited |
| Nameservers | dns1.p03.nsone.net, dns2.p03.nsone.net, dns3.p03.nsone.net, dns4.p03.nsone.net |
| DNSSEC | no |
| Source | https://pubapi.registry.google/rdap/domain/chicktok.app |
chicktok.app 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 dns1.p03.nsone.net is published for chicktok.app in the registration record from https://pubapi.registry.google/rdap/domain/chicktok.app.
Nameserver dns2.p03.nsone.net is published for chicktok.app in the registration record from https://pubapi.registry.google/rdap/domain/chicktok.app.
Nameserver dns3.p03.nsone.net is published for chicktok.app in the registration record from https://pubapi.registry.google/rdap/domain/chicktok.app.
Nameserver dns4.p03.nsone.net is published for chicktok.app in the registration record from https://pubapi.registry.google/rdap/domain/chicktok.app.
chicktok.app has 2 address records, 0 mail exchangers and 4 nameservers, measured at 1.1.1.1:53.
| A | 35.157.26.135, 63.176.8.218 |
|---|---|
| AAAA | — |
| NS | dns1.p03.nsone.net, dns2.p03.nsone.net, dns3.p03.nsone.net, dns4.p03.nsone.net |
| MX | — |
| SPF | absent |
| DMARC | absent |
| CAA | — |
| Wildcard | off |
| DNSSEC | not signed |
| Resolver | 1.1.1.1:53 |
IPv4 address 35.157.26.135 answers for chicktok.app at resolver 1.1.1.1:53.
IPv4 address 63.176.8.218 answers for chicktok.app at resolver 1.1.1.1:53.
chicktok.app is placed in Frankfurt am Main, Germany by the local geolocation database (db-ip).
| Address | 35.157.26.135 |
|---|---|
| Country | Germany |
| City | Frankfurt am Main |
| Source | db-ip |
The certificate for chicktok.app is valid, with 36 days left and 2 subject alternative names. Source: tls:443.
| Issuer | YE2 |
|---|---|
| Subject | chicktok.app |
| Valid from | 8 September 2026 |
| Valid until | 7 December 2026 |
| Days left | 36 |
| SAN count | 2 |
| Protocol | TLS 1.3 |
| Source | tls:443 |
Subject alternative names: *.chicktok.app, chicktok.app.
Tech detection checked the fetched homepage and named 3 products. Source: wappalyzergo.
Clicky is filed under Analytics.
HSTS is filed under Security.
Netlify is filed under PaaS, CDN.
The homepage returned HTTP 200 in 261 ms. The target title is 63 characters and the page has 1 H1 heading.
| Status | 200 |
|---|---|
| TTFB | 261 ms |
| Title length | 63 no |
| Quoted title | "Chicktok — Hookup App & Personals | Find Women Near You Tonight" |
| Meta description | "Chicktok is the fastest growing hookup app and personals platform. Browse real ads from women in New York, Los Angeles, Chicago, Houston and 100+ cities. Free to join." yes |
| H1 count | 1 |
| HSTS | yes yes |
| CSP | no |
| X-Frame-Options | — |
| Robots meta | — |
| Canonical | https://chicktok.app/ |
| Language | en |
| Links | 124 |
| Images | 33 |
| Favicon | yes |
The quoted title and meta description are measurements of the other site. They are not this page's title or description.
Family DNS for chicktok.app 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 | no |
Google Web Risk did not run. No API key is configured, and this report does not invent a clean result from that service.
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 5 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.
The checks that ran did not produce a safety warning, and a score is not a promise that the site is safe.
chicktok.app is placed in Frankfurt am Main, Germany.
chicktok.app expires on 12 March 2027 according to https://pubapi.registry.google/rdap/domain/chicktok.app.
The registry did not return a person or a company for chicktok.app. RDAP often redacts the registrant. The registrar on file is PDR Ltd. d/b/a PublicDomainRegistry.com.
No other indexable reports share this TLD, host, or registrar yet.
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.
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.