videking.com
Domain report: WHOIS, DNS, hosting, SSL and safety. Checked .
Online · 200Family DNS blockedSSL: 65 days left5 years old
50
videking.com was registered on 30 Nov 2020 via NameCheap, Inc. and the registry expiry is 30 Nov 2026. WHOIS data came from RDAP at https://rdap.verisign.com/com/v1/domain/videking.com.
videking.com publishes 2 nameservers. DNSSEC is not signed.
videking.com has 2 IPv4 addresses (188.114.96.4, 188.114.97.4) and 2 IPv6 addresses (2a06:98c1:3120::4, 2a06:98c1:3121::4). The geolocation database places 188.114.96.4 in Toronto, Canada.
The TLS certificate from WE1 is valid and has 65 days left (TLS 1.3). The homepage answered HTTP 200.
Tech detection named Cloudflare, HTTP/3, LiteSpeed, LiteSpeed Cache, Litespeed Cache, MySQL, PHP, Redis, Redis Object Cache, WordPress, jQuery, jQuery CDN and jsDelivr. The fingerprints ran on the homepage that was already downloaded.
Domain · RDAP/WHOIS
videking.com was registered on 30 Nov 2020 via NameCheap, Inc.. The registry returned 1 status value and 2 nameservers from https://rdap.verisign.com/com/v1/domain/videking.com.
| Registered | since 30 Nov 2020 |
|---|---|
| Created | 30 November 2020 |
| Updated | 30 November 2025 |
| Expires | 30 November 2026 |
| Registrar | NameCheap, Inc. |
| Status | client transfer prohibited |
| Nameservers | carol.ns.cloudflare.com, clint.ns.cloudflare.com |
| DNSSEC | no |
| Source | https://rdap.verisign.com/com/v1/domain/videking.com |
videking.com 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 carol.ns.cloudflare.com is published for videking.com in the registration record from https://rdap.verisign.com/com/v1/domain/videking.com.
Nameserver clint.ns.cloudflare.com is published for videking.com in the registration record from https://rdap.verisign.com/com/v1/domain/videking.com.
DNS
videking.com has 4 address records, 4 mail exchangers and 2 nameservers, measured at 1.1.1.1:53.
| A | 188.114.96.4, 188.114.97.4 |
|---|---|
| AAAA | 2a06:98c1:3120::4, 2a06:98c1:3121::4 |
| NS | carol.ns.cloudflare.com, clint.ns.cloudflare.com |
| MX | aspmx.l.google.com (1) 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 188.114.96.4 answers for videking.com at resolver 1.1.1.1:53.
IPv4 address 188.114.97.4 answers for videking.com at resolver 1.1.1.1:53.
IPv6 address 2a06:98c1:3120::4 answers for videking.com at resolver 1.1.1.1:53.
IPv6 address 2a06:98c1:3121::4 answers for videking.com at resolver 1.1.1.1:53.
Mail exchanger aspmx.l.google.com has preference 1. 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.com is placed in Toronto, Canada by the local geolocation database (db-ip).
| Address | 188.114.96.4 |
|---|---|
| Country | Canada |
| City | Toronto |
| Source | db-ip |
SSL/TLS
The certificate for videking.com is valid, with 65 days left and 2 subject alternative names. Source: tls:443.
| Issuer | WE1 |
|---|---|
| Subject | videking.com |
| Valid from | 8 October 2026 |
| Valid until | 6 January 2027 |
| Days left | 65 |
| SAN count | 2 |
| Protocol | TLS 1.3 |
| Source | tls:443 |
Subject alternative names: *.videking.com, videking.com.
Tech stack
Tech detection checked the fetched homepage and named 13 products. Source: wappalyzergo.
- Cloudflare · CDN
- HTTP/3 · Miscellaneous
- LiteSpeed · Web servers
- LiteSpeed Cache · Caching, WordPress plugins
- Litespeed Cache · Caching, WordPress plugins
- MySQL · Databases
- PHP · Programming languages
- Redis · Databases
- Redis Object Cache · Caching
- WordPress · CMS, Blogs
- jQuery · JavaScript libraries
- jQuery CDN · CDN
- jsDelivr · CDN
Cloudflare is filed under CDN.
HTTP/3 is filed under Miscellaneous.
LiteSpeed is filed under Web servers.
LiteSpeed Cache is filed under Caching, WordPress plugins.
Litespeed Cache is filed under Caching, WordPress plugins.
MySQL is filed under Databases.
PHP is filed under Programming languages.
Redis is filed under Databases.
Redis Object Cache is filed under Caching.
WordPress is filed under CMS, Blogs.
jQuery is filed under JavaScript libraries.
jQuery CDN is filed under CDN.
jsDelivr is filed under CDN.
On-page checks
The homepage returned HTTP 200 in 4682 ms. The target title is 47 characters and the page has 1 H1 heading.
| Status | 200 |
|---|---|
| TTFB | 4682 ms |
| Title length | 47 yes |
| Quoted title | "Videking - Best Erotic Unseen Indian Sex Videos" |
| Meta description | "Best 2025 Indian dehati, Pakistani sex videos. Watch our latest HD xxx clips and Adult porn movies! (Previously Videking.com)" yes |
| H1 count | 1 |
| HSTS | no no |
| CSP | no |
| X-Frame-Options | — |
| Robots meta | follow, index, max-snippet:-1, max-video-preview:-1, max-image-preview:large |
| Canonical | https://videking3.com/ |
| Language | en-US |
| Links | 69 |
| Images | 28 |
| 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 videking.com 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.com. 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 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.
Change history
- October 2026: dns a changed from 188.114.96.3,188.114.97.3 to 188.114.96.4,188.114.97.4.
- October 2026: dns aaaa changed from 2a06:98c1:3120::3,2a06:98c1:3121::3 to 2a06:98c1:3120::4,2a06:98c1:3121::4.
Questions
Is videking.com safe?
Cloudflare family DNS returned a block for videking.com. That resolver covers adult and malware names.
Who hosts videking.com?
videking.com is placed in Toronto, Canada.
When does videking.com expire?
videking.com expires on 30 November 2026 according to https://rdap.verisign.com/com/v1/domain/videking.com.
Who owns videking.com?
The registry did not return a person or a company for videking.com. RDAP often redacts the registrant. The registrar on file is NameCheap, Inc..
Sources
- RDAP source https://rdap.verisign.com/com/v1/domain/videking.com at 2026-10-30T14:18:57Z
- DNS source 1.1.1.1:53 at 2026-10-30T14:18:57Z
- TLS source tls:443 at 2026-10-30T14:18:57Z
- HTTP source https://videking.com/ at 2026-10-30T14:18:57Z
- Tech source wappalyzergo at 2026-10-30T14:18:57Z
- Geo source db-ip at 2026-10-30T14:18:57Z
- Safety source family DNS and local lists at 2026-10-30T14:18:57Z
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.