lego-titanik.ru was registered with whois.tcinet.ru on 7 Apr 1994 and is hosted on AS9123 TimeWeb Ltd. in Russian Federation. We couldn't read an SSL certificate for it when we last analysed it.
What security vendors and the WOT community say about this domain.
We couldn't read an SSL certificate on port 443 when we last analysed lego-titanik.ru. Refresh the analysis to check again.
Is lego-titanik.ru’s name taken on other extensions?
1 technology detected across 1 category.
Detected from headers, page source and DNS · Automatic and may be incomplete · Suggest a correction
Every IP address lego-titanik.ru resolves to, and where it's hosted.
| Host | IPv4 address | TTL |
|---|---|---|
| lego-titanik.ru | 92.53.96.149 | 600 |
| Host | IPv6 address | TTL |
|---|---|---|
| lego-titanik.ru | 2a03:6f00:1::5c35:6095 | 600 |
| Host | Mail server | TTL |
|---|---|---|
| lego-titanik.ru | 10 mx1.timeweb.ru | 600 |
| lego-titanik.ru | 20 mx2.timeweb.ru | 600 |
| Host | Name server | TTL |
|---|---|---|
| lego-titanik.ru | ns1.timeweb.ru | 600 |
| lego-titanik.ru | ns2.timeweb.ru | 600 |
| lego-titanik.ru | ns3.timeweb.org | 600 |
| lego-titanik.ru | ns4.timeweb.org | 600 |
| Host | Text | TTL |
|---|---|---|
| lego-titanik.ru | "v=spf1 include:_spf.timeweb.ru ~all" | 600 |
| Host | Start of authority | TTL |
|---|---|---|
| lego-titanik.ru | ns1.timeweb.ru dns.timeweb.ru 1 28800 7200 259200 300 | 600 |
| Host | Value | TTL |
|---|---|---|
| lego-titanik.ru | 257 3 13 SlvSDZDSl+hlP449AzG3K/zSTtZDucjap1ISkL+zTwiaXCVC7I1oo4AzoJoD2VLbyh27ZjXu/J+dj1oIGzGvVg== | 300 |
Other domains served from 92.53.96.149. Normal for shared hosting and CDNs.
No reviews yet. Used lego-titanik.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.
lego-titanik.ru has no community safety rating yet. We couldn't read an SSL certificate on it when we last analysed it. See Security →
lego-titanik.ru is registered through whois.tcinet.ru. See WHOIS →
lego-titanik.ru was registered on 7 Apr 1994, making it 32 years old. See Overview →
lego-titanik.ru is served from 1 IP address, mainly on AS9123 TimeWeb Ltd. in Russian Federation. See Hosting →
We detected 1 technology, including jQuery. See Built with →
Raw registry data for lego-titanik.ru. May be redacted by privacy services.
% IANA WHOIS server % for more information on IANA, visit http://www.iana.org % This query returned 1 object refer: whois.tcinet.ru domain: RU organisation: Coordination Center for TLD RU address: 8 Marta street 1, bld 12 address: Moscow 127083 address: Russian Federation (the) contact: administrative name: .RU domain Administrative group organisation: Coordination Center for TLD RU address: 8 Marta street 1, bld 12 address: Moscow 127083 address: Russian Federation (the) phone: +7 495 730 29 71 fax-no: +7 495 730 29 68 e-mail: [email protected] contact: technical name: Technical Center of Internet organisation: Technical Center of Internet address: 8 Marta street 1, bld 12 address: Moscow 127083 address: Russian Federation (the) phone: +7 495 730 29 69 fax-no: +7 495 730 29 68 e-mail: [email protected] nserver: A.DNS.RIPN.NET 193.232.128.6 2001:678:17:0:193:232:128:6 nserver: B.DNS.RIPN.NET 194.85.252.62 2001:678:16:0:194:85:252:62 nserver: D.DNS.RIPN.NET 194.190.124.17 2001:678:18:0:194:190:124:17 nserver: E.DNS.RIPN.NET 193.232.142.17 2001:678:15:0:193:232:142:17 nserver: F.DNS.RIPN.NET 193.232.156.17 2001:678:14:0:193:232:156:17 ds-rdata: 18274 8 2 ab35d17d3f39eb42cee14c6273247938d33eeeaa9f5caa70b3858dbf4bd3e87b whois: whois.tcinet.ru status: ACTIVE remarks: Registration information: http://www.cctld.ru/en created: 1994-04-07 changed: 2023-03-03 source: IANA
The first response from http://www.lego-titanik.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 lego-titanik.ru. Data is collected independently from public sources and some figures are estimates, provided for information only.
Found in public certificate transparency logs.
Searching the certificate transparency logs… This can take up to a minute.