videking.cc
Domain report: WHOIS, DNS, hosting, SSL and safety. Checked .
OfflineFamily DNS blockedSSL: 53 days left2 years old
35
videking.cc was registered on 8 Mar 2024 via NameSilo, LLC and the registry expiry is 8 Mar 2027. WHOIS data came from RDAP at https://tld-rdap.verisign.com/cc/v1/domain/videking.cc.
videking.cc publishes 2 nameservers. DNSSEC is not signed.
videking.cc has 2 IPv4 addresses (104.21.94.236, 172.67.141.155) and 2 IPv6 addresses (2606:4700:3030::6815:5eec, 2606:4700:3036::ac43:8d9b). The geolocation database places 104.21.94.236 in Toronto, Canada.
The TLS certificate from WE1 is valid and has 53 days left (TLS 1.3).
Domain · RDAP/WHOIS
videking.cc was registered on 8 Mar 2024 via NameSilo, LLC. The registry returned 1 status value and 2 nameservers from https://tld-rdap.verisign.com/cc/v1/domain/videking.cc.
| Registered | since 8 Mar 2024 |
|---|---|
| Created | 8 March 2024 |
| Updated | 11 March 2026 |
| Expires | 8 March 2027 |
| Registrar | NameSilo, LLC |
| Status | client transfer prohibited |
| Nameservers | kara.ns.cloudflare.com, vick.ns.cloudflare.com |
| DNSSEC | no |
| Source | https://tld-rdap.verisign.com/cc/v1/domain/videking.cc |
videking.cc 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 kara.ns.cloudflare.com is published for videking.cc in the registration record from https://tld-rdap.verisign.com/cc/v1/domain/videking.cc.
Nameserver vick.ns.cloudflare.com is published for videking.cc in the registration record from https://tld-rdap.verisign.com/cc/v1/domain/videking.cc.
DNS
videking.cc has 4 address records, 5 mail exchangers and 2 nameservers, measured at 1.1.1.1:53.
| A | 104.21.94.236, 172.67.141.155 |
|---|---|
| AAAA | 2606:4700:3030::6815:5eec, 2606:4700:3036::ac43:8d9b |
| NS | kara.ns.cloudflare.com, vick.ns.cloudflare.com |
| MX | aspmx.l.google.com (1) Google, alt1.aspmx.l.google.com (5) Google, alt2.aspmx.l.google.com (5) Google, alt3.aspmx.l.google.com (10) Google, alt4.aspmx.l.google.com (10) Google |
| SPF | absent |
| DMARC | absent |
| CAA | — |
| Wildcard | off |
| DNSSEC | not signed |
| Resolver | 1.1.1.1:53 |
IPv4 address 104.21.94.236 answers for videking.cc at resolver 1.1.1.1:53.
IPv4 address 172.67.141.155 answers for videking.cc at resolver 1.1.1.1:53.
IPv6 address 2606:4700:3030::6815:5eec answers for videking.cc at resolver 1.1.1.1:53.
IPv6 address 2606:4700:3036::ac43:8d9b answers for videking.cc at resolver 1.1.1.1:53.
Mail exchanger aspmx.l.google.com has preference 1. The host is recognised as Google.
Mail exchanger alt1.aspmx.l.google.com has preference 5. The host is recognised as Google.
Mail exchanger alt2.aspmx.l.google.com has preference 5. The host is recognised as Google.
Mail exchanger alt3.aspmx.l.google.com has preference 10. The host is recognised as Google.
Mail exchanger alt4.aspmx.l.google.com has preference 10. The host is recognised as Google.
Hosting and geo
videking.cc is placed in Toronto, Canada by the local geolocation database (db-ip).
| Address | 104.21.94.236 |
|---|---|
| Country | Canada |
| City | Toronto |
| Source | db-ip |
SSL/TLS
The certificate for videking.cc is valid, with 53 days left and 2 subject alternative names. Source: tls:443.
| Issuer | WE1 |
|---|---|
| Subject | videking.cc |
| Valid from | 25 September 2026 |
| Valid until | 24 December 2026 |
| Days left | 53 |
| SAN count | 2 |
| Protocol | TLS 1.3 |
| Source | tls:443 |
Subject alternative names: *.videking.cc, videking.cc.
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 |
|---|
context deadline exceeded
Security
Family DNS for videking.cc 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 videking.cc. 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 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.
Change history
First checked on 30 October 2026; changes will appear here.
Questions
Is videking.cc safe?
Cloudflare family DNS returned a block for videking.cc. That resolver covers adult and malware names.
Who hosts videking.cc?
videking.cc is placed in Toronto, Canada.
When does videking.cc expire?
videking.cc expires on 8 March 2027 according to https://tld-rdap.verisign.com/cc/v1/domain/videking.cc.
Who owns videking.cc?
The registry did not return a person or a company for videking.cc. RDAP often redacts the registrant. The registrar on file is NameSilo, LLC.
Sources
- RDAP source https://tld-rdap.verisign.com/cc/v1/domain/videking.cc at 2026-10-30T13:35:47Z
- DNS source 1.1.1.1:53 at 2026-10-30T13:35:47Z
- TLS source tls:443 at 2026-10-30T13:35:47Z
- HTTP source https://videking.cc/ at 2026-10-30T13:35:47Z
- Tech source not available at 2026-10-30T13:35:47Z
- Geo source db-ip at 2026-10-30T13:35:47Z
- Safety source family DNS and local lists at 2026-10-30T13:35:47Z
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.