Alternatives to dragonknight.ru
Matched automatically on description, category and technology. Only sites that pass our safety checks are shown. · Report a wrong match
dragonknight.ru was registered with REGRU-RU on 11 Sept 2014 and is hosted on AS7979 Servers.com Inc. in Russian Federation. Its SSL certificate from Let's Encrypt expired on 18 Apr 2024, and the site does not support HTTP/3. WOT's community rates its safety excellent (80/100).
What security vendors and the WOT community say about this domain.
What loads and tracks visitors when the homepage opens.
Running a full browser scan of the homepage… This takes about a minute.
6 similar domains registered in the last 90 days — possible typosquatting or phishing.
| Domain | Why it’s similar | Registered | Status | Report |
|---|---|---|---|---|
| dragonknight.cloud | Other extension | 16 Oct 2026 | Checking… | Report → |
| dragonknights.link | Extra letter | 1 Oct 2026 | Checking… | Report → |
| dragonknights.world | Extra letter | 15 Sept 2026 | Checking… | Report → |
| flamedragonknights.cn | Keyword added | 19 Sept 2026 | Checking… | Report → |
| dragonknightcardmart.com | Keyword added | 25 Aug 2026 | Checking… | Report → |
From CubDomain's daily newly registered domains. Similar doesn't mean malicious.
Is dragonknight.ru’s name taken on other extensions?
Estimated visitors and engagement.
| Top countries | Share | Visits | Desktop | Mobile |
|---|---|---|---|---|
| Russia | 33.4% | — | — | — |
| Türkiye | 12.1% | — | — | — |
| United States | 8.5% | — | — | — |
| Belarus | 8.1% | — | — | — |
| Kazakhstan | 6.8% | — | — | — |
1 technology detected across 1 category.
Detected from headers, page source and DNS · Automatic and may be incomplete · Suggest a correction
Every IP address dragonknight.ru resolves to, and where it's hosted.
| Host | IPv4 address | TTL |
|---|---|---|
| dragonknight.ru | 164.138.99.254 | 3598 |
| Host | Mail server | TTL |
|---|---|---|
| dragonknight.ru | 10 mx.yandex.net | 3600 |
| Host | Name server | TTL |
|---|---|---|
| dragonknight.ru | dns1.yandex.net | 900 |
| dragonknight.ru | dns2.yandex.net | 900 |
| Host | Text | TTL |
|---|---|---|
| dragonknight.ru | "v=spf1 mx a include:_spf.yandex.net ip4:37.187.172.25/32 ip4:164.138.99.254/32 ~all" | 3600 |
| Host | Start of authority | TTL |
|---|---|---|
| dragonknight.ru | dns1.yandex.net dns-hosting.yandex.ru 88 900 90 86400 900 | 900 |
Other domains served from 164.138.99.254. Normal for shared hosting and CDNs.
No reviews yet. Used dragonknight.ru? Be the first to say how it went.
Reviews are from CubDomain users and are separate from the security verdicts above.
Common questions, answered from this report's data.
WOT's community rates dragonknight.ru excellent for safety (80/100). Its SSL certificate expired on 18 Apr 2024. See Security →
dragonknight.ru is registered through REGRU-RU. See WHOIS →
dragonknight.ru was registered on 11 Sept 2014, making it 12 years old. See Overview →
dragonknight.ru is served from 1 IP address, mainly on AS7979 Servers.com Inc. in Russian Federation. See Hosting →
We detected 1 technology, including jQuery. See Built with →
Raw registry data for dragonknight.ru. May be redacted by privacy services.
% TCI Whois Service. Terms of use: % https://tcinet.ru/documents/whois_ru_rf.pdf (in Russian) % https://tcinet.ru/documents/whois_su.pdf (in Russian) domain: DRAGONKNIGHT.RU nserver: dns1.yandex.net. nserver: dns2.yandex.net. state: REGISTERED, DELEGATED, VERIFIED person: Private Person registrar: REGRU-RU admin-contact: http://www.reg.ru/whois/admin_contact created: 2014-09-11T12:00:38Z paid-till: 2024-09-11T13:00:38Z free-date: 2024-10-12 source: TCI Last updated on 2024-02-16T02:56:30Z
The first response from http://www.dragonknight.ru, before any redirect: caching, server and policy headers.
Four timed TCP connections to port 443 from CubDomain's servers.
CubDomain is not affiliated with dragonknight.ru. Data is collected independently from public sources and some figures are estimates, provided for information only.
Spam and malware blocklists for the site's IP and mail servers.
Found in public certificate transparency logs.
Searching the certificate transparency logs… This can take up to a minute.
When the site first appeared, and what has changed since.
We record what changes from the next time this report is refreshed.