Alternatives to cynteka.ru
Matched automatically on description, category and technology. Only sites that pass our safety checks are shown. · Report a wrong match
cynteka.ru was registered with REGRU-RU on 21 Jul 2013 and is hosted on AS49505 OOO Network of Data-Centers Selectel in Russian Federation. Its SSL certificate from GlobalSign nv-sa expired on 24 Jan 2025, and the site does not support HTTP/3.
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.
8 similar domains registered in the last 90 days — possible typosquatting or phishing.
| Domain | Why it’s similar | Registered | Status | Report |
|---|---|---|---|---|
| cyntek.es | Typo | 9 Oct 2026 | Checking… | Report → |
| synteka.ru | Typo | 26 Aug 2026 | Checking… | Report → |
| cynteka22.ru | Keyword added | 23 Oct 2026 | Checking… | Report → |
| zynteka.com | Typo | 10 Oct 2026 | Checking… | Report → |
| cyntera.com.br | Typo | 26 Sept 2026 | Checking… | Report → |
From CubDomain's daily newly registered domains. Similar doesn't mean malicious.
Is cynteka.ru’s name taken on other extensions?
Estimated visitors and engagement.
| Top countries | Share | Visits | Desktop | Mobile |
|---|---|---|---|---|
| Russia | 99.7% | — | — | — |
| Sweden | 0.2% | — | — | — |
| Luxembourg | 0.1% | — | — | — |
| United Kingdom | 0.1% | — | — | — |
3 technologies detected across 3 categories.
Detected from headers, page source and DNS · Automatic and may be incomplete · Suggest a correction
Every IP address cynteka.ru resolves to, and where it's hosted.
| Host | IPv4 address | TTL |
|---|---|---|
| cynteka.ru | 95.213.156.189 | 3600 |
| Host | Mail server | TTL |
|---|---|---|
| cynteka.ru | 10 mx.yandex.ru | 3600 |
| Host | Name server | TTL |
|---|---|---|
| cynteka.ru | ns1.reg.ru | 3600 |
| cynteka.ru | ns2.reg.ru | 3600 |
| Host | Text | TTL |
|---|---|---|
| cynteka.ru | "mailru-domain: eaaebgQYCzCHEQK8" | 3600 |
| cynteka.ru | "mailru-verification: fc268b61837ef9aa" | 3600 |
| cynteka.ru | "v=spf1 include:mxsmtp.sendpulse.com include:mxsspf.sendpulse.com include:_spf.yandex.net +a +mx include:_spf.dashasender.ru ~all" | 3600 |
| cynteka.ru | "yandex-verification: aa6e0895f8d454e2" | 3600 |
| Host | Start of authority | TTL |
|---|---|---|
| cynteka.ru | ns1.reg.ru hostmaster.ns1.reg.ru 1707809029 14400 3600 604800 300 | 3600 |
No reviews yet. Used cynteka.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.
cynteka.ru has no community safety rating yet. Its SSL certificate expired on 24 Jan 2025. See Security →
cynteka.ru is registered through REGRU-RU. See WHOIS →
cynteka.ru was registered on 21 Jul 2013, making it 13 years old. See Overview →
cynteka.ru is served from 1 IP address, mainly on AS49505 OOO Network of Data-Centers Selectel in Russian Federation. See Hosting →
We detected 3 technologies, including Google Analytics, WordPress and jQuery. See Built with →
Raw registry data for cynteka.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: CYNTEKA.RU nserver: ns1.reg.ru. nserver: ns2.reg.ru. state: REGISTERED, DELEGATED, UNVERIFIED org: Cynteka, LLC taxpayer-id: 7813582855 registrar: REGRU-RU admin-contact: http://www.reg.ru/whois/admin_contact created: 2013-07-21T18:34:24Z paid-till: 2024-07-21T19:34:24Z free-date: 2024-08-21 source: TCI Last updated on 2024-02-15T07:21:30Z
The first response from http://www.cynteka.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 cynteka.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.
When the site first appeared, and what has changed since.
We record what changes from the next time this report is refreshed.
Found in public certificate transparency logs.
Searching the certificate transparency logs… This can take up to a minute.