t4ka.ru - robtex.com
t4ka.ru
| DNSSEC | ⚠️ Not signed | ||||||
| A | 185.215.4.54🇷🇺 DDOS-GUARD185.215.4.0/24 Tilda Publishing LLC | ||||||
| NS | dns1.yandex.net ⭐ | ||||||
| A | 2a02:6b8::213🇷🇺 TELETECH2a02:6b8::/32 Yandex network | ||||||
| PTR | dns1.yandex.net | ||||||
| A | 213.180.204.213🇷🇺 TELETECH213.180.192.0/19 Yandex network | ||||||
| PTR | dns1.yandex.net | ||||||
| NS | dns2.yandex.net | ||||||
| A | 2a02:6b8:0:1::213🇷🇺 TELETECH2a02:6b8::/32 Yandex network | ||||||
| PTR | dns2.yandex.net | ||||||
| A | 93.158.134.213🇷🇺 TELETECH93.158.128.0/18 Yandex enterprise network | ||||||
| PTR | dns2.yandex.net | ||||||
| MX | mx.yandex.net ⭐ | ||||||
| A | 2a02:6b8::311🇷🇺 TELETECH2a02:6b8::/32 Yandex network | ||||||
| PTR | mxfront.stable.qloud-b.yandex.net | ||||||
| A | 77.88.21.249🇷🇺 TELETECH77.88.0.0/18 Yandex enterprise network | ||||||
| PTR | mxfront.stable.qloud-b.yandex.net | ||||||
| TXT | v=spf1 include:_spf.yandex.net include:_spf.dashasender.ru ~all | ||||||
| SOA | dns1.yandex.netdns-hosting@yandex.ru serial=24 | ||||||
ru
| DNSSEC | 🔒 Signed (DS record present) | ||||||
| NS | a.dns.ripn.net ⭐ | ||||||
| NS | b.dns.ripn.net | ||||||
| NS | d.dns.ripn.net | ||||||
| NS | e.dns.ripn.net | ||||||
| NS | f.dns.ripn.net | ||||||
| SOA | a.dns.ripn.nethostmaster@ripn.net serial=4068511 | ||||||
Same first word
Similar names
DNS History
8 records (4 active, 4 former)
●NSdns1.yandex.net2026-03-01 → 2026-04-14 · 3 obs
● 2026-03-01 19:38:34
● 2026-04-14 11:46:38
●NSdns2.yandex.net2026-03-01 → 2026-04-14 · 3 obs
● 2026-03-01 19:38:34
● 2026-04-14 11:46:38
○NSns1.digitalocean.com2015-05-29 → 2017-03-27 · 4 obs
● 2017-03-27 18:18:56
○ 2026-03-01 19:38:34
○ 2026-04-14 11:46:38
○NSns2.digitalocean.com2015-05-29 → 2017-03-27 · 4 obs
● 2017-03-27 18:18:56
○ 2026-03-01 19:38:34
○ 2026-04-14 11:46:38
○NSns3.digitalocean.com2015-05-29 → 2017-03-27 · 4 obs
● 2017-03-27 18:18:56
○ 2026-03-01 19:38:34
○ 2026-04-14 11:46:38
●MXmx.yandex.net2015-10-15 → 2026-04-14 · 2 obs
● 2026-04-14 11:46:38
●A185.215.4.542026-03-01 → 2026-04-14 · 3 obs
● 2026-03-01 19:38:34
● 2026-04-14 11:46:38
○A188.166.98.2102015-05-29 → 2017-03-27 · 4 obs
● 2017-03-27 18:18:56
○ 2026-03-01 19:38:34
○ 2026-04-14 11:46:38
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| ru | b.dns.ripn.net, e.dns.ripn.net, a.dns.ripn.net, d.dns.ripn.net... | - |
| t4ka.ru | dns1.yandex.net, dns2.yandex.net | - |
✅ Authoritative Response
Server:213.180.204.213
NS records: dns1.yandex.net, dns2.yandex.net
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for t4ka.ru (unsigned zone)
⏱️ Timing
Total: 1317ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 1 | 185.215.4.54 |
| NS | 2 | dns1.yandex.net, dns2.yandex.net |
| MX | 1 | mx.yandex.net (pri: 10) |
| TXT | 1 | v=spf1 include:_spf.yandex.net include:_ |
| SOA | 1 | dns1.yandex.net dns-hosting.yandex.ru |
Analysis
IP Addresses
t4ka.ru resolves to a single IP: 185.215.4.54.
Other host names, for instance sicentr.ru, 3598.ru, fbukcsm.ru, mospsyholog.ru and xn--c1acmh2a4g.xn--p1acf share IP numbers with t4ka.ru.
Name Servers
t4ka.ru has two name servers: dns1.yandex.net and dns2.yandex.net.
t4ka.ru shares the same name server setup as other domains, for example bluda.ru, clublexus.ru, lst.gr, doyoskills.ru and yefyapi.com.tr.
t4ka.ru shares some name servers with other domains, for example 6220662.ru, blago1.ru, osipov.me, regionplus.az and lavrova.ru.
These name servers are commonly used together with dns1.yandex.ru and dns2.yandex.ru.
Host names with two IP numbers:
dns1.yandex.net points to: 2a02:6b8::213 and 213.180.204.213; dns2.yandex.net points to: 2a02:6b8:0:1::213 and 93.158.134.213.
Mail Servers
t4ka.ru is handled by a single mail server, mx.yandex.net.
t4ka.ru shares the mail server setup with other domains, for example kupluposudu.ru, genpm.ru, marmaraymm.com, anmiles.net and savosko.com.ua.
t4ka.ru shares some mail servers with other domains, at least partially; for instance vekzhiv.ru, en-ua.com, san-tec.ru, nasosregion.net and gorsred.ru.
mx.yandex.net resolves to two IPs: 2a02:6b8::311 and 77.88.21.249.