superriki.yt
Domain report: WHOIS, DNS, hosting, SSL and safety. Checked .
50
Domain report: WHOIS, DNS, hosting, SSL and safety. Checked .
50
superriki.yt was registered on 15 Nov 2019 via TLD Registrar Solutions Ltd and the registry expiry is 15 Nov 2026. WHOIS data came from RDAP at https://rdap.nic.yt/domain/superriki.yt.
superriki.yt publishes 2 nameservers. DNSSEC is not signed.
superriki.yt has 2 IPv4 addresses (104.21.80.218, 172.67.187.71) and 2 IPv6 addresses (2606:4700:3030::6815:50da, 2606:4700:3034::ac43:bb47). The geolocation database places 104.21.80.218 in Toronto, Canada.
The TLS certificate from WE1 is valid and has 47 days left (TLS 1.3). The homepage answered HTTP 200.
Tech detection named Apache HTTP Server, Cloudflare, DataLife Engine, Google Analytics, HTTP/3, Liveinternet, OneSignal, PHP and jQuery. The fingerprints ran on the homepage that was already downloaded.
superriki.yt was registered on 15 Nov 2019 via TLD Registrar Solutions Ltd. The registry returned 1 status value and 2 nameservers from https://rdap.nic.yt/domain/superriki.yt.
| Registered | since 15 Nov 2019 |
|---|---|
| Created | 15 November 2019 |
| Updated | 20 November 2025 |
| Expires | 15 November 2026 |
| Registrar | TLD Registrar Solutions Ltd |
| Status | active |
| Nameservers | anastasia.ns.cloudflare.com, yevgen.ns.cloudflare.com |
| DNSSEC | unknown |
| Source | https://rdap.nic.yt/domain/superriki.yt |
Nameserver anastasia.ns.cloudflare.com is published for superriki.yt in the registration record from https://rdap.nic.yt/domain/superriki.yt.
Nameserver yevgen.ns.cloudflare.com is published for superriki.yt in the registration record from https://rdap.nic.yt/domain/superriki.yt.
superriki.yt has 4 address records, 0 mail exchangers and 2 nameservers, measured at 1.1.1.1:53.
| A | 104.21.80.218, 172.67.187.71 |
|---|---|
| AAAA | 2606:4700:3030::6815:50da, 2606:4700:3034::ac43:bb47 |
| NS | anastasia.ns.cloudflare.com, yevgen.ns.cloudflare.com |
| MX | — |
| SPF | absent |
| DMARC | absent |
| CAA | — |
| Wildcard | off |
| DNSSEC | not signed |
| Resolver | 1.1.1.1:53 |
IPv4 address 104.21.80.218 answers for superriki.yt at resolver 1.1.1.1:53.
IPv4 address 172.67.187.71 answers for superriki.yt at resolver 1.1.1.1:53.
IPv6 address 2606:4700:3030::6815:50da answers for superriki.yt at resolver 1.1.1.1:53.
IPv6 address 2606:4700:3034::ac43:bb47 answers for superriki.yt at resolver 1.1.1.1:53.
superriki.yt is placed in Toronto, Canada by the local geolocation database (db-ip).
| Address | 104.21.80.218 |
|---|---|
| Country | Canada |
| City | Toronto |
| Source | db-ip |
The certificate for superriki.yt is valid, with 47 days left and 2 subject alternative names. Source: tls:443.
| Issuer | WE1 |
|---|---|
| Subject | superriki.yt |
| Valid from | 18 September 2026 |
| Valid until | 17 December 2026 |
| Days left | 47 |
| SAN count | 2 |
| Protocol | TLS 1.3 |
| Source | tls:443 |
Subject alternative names: *.superriki.yt, superriki.yt.
Tech detection checked the fetched homepage and named 9 products. Source: wappalyzergo.
Apache HTTP Server is filed under Web servers.
Cloudflare is filed under CDN.
DataLife Engine is filed under CMS.
Google Analytics is filed under Analytics.
HTTP/3 is filed under Miscellaneous.
Liveinternet is filed under Analytics.
OneSignal is filed under Marketing automation, A/B Testing.
PHP is filed under Programming languages.
jQuery is filed under JavaScript libraries.
The homepage returned HTTP 200 in 62 ms. The target title is 18 characters and the page has 1 H1 heading.
| Status | 200 |
|---|---|
| TTFB | 62 ms |
| Title length | 18 yes |
| Quoted title | "❤️Turkish Series❤️" |
| Meta description | "❤️Best turkish serials with english subtitles" yes |
| H1 count | 1 |
| HSTS | no no |
| CSP | no |
| X-Frame-Options | — |
| Robots meta | — |
| Canonical | — |
| Language | en |
| Links | 143 |
| Images | 31 |
| 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 superriki.yt 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 superriki.yt. 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.
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 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.
First checked on 30 October 2026; changes will appear here.
Cloudflare family DNS returned a block for superriki.yt. That resolver covers adult and malware names.
superriki.yt is placed in Toronto, Canada.
superriki.yt expires on 15 November 2026 according to https://rdap.nic.yt/domain/superriki.yt.
The registry did not return a person or a company for superriki.yt. RDAP often redacts the registrant. The registrar on file is TLD Registrar Solutions Ltd.
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.