insign.su - dns.ninja
insign.su
| DNSSEC | ⚠️ Not signed | ||||||
| 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 redirect=_spf.yandex.net | ||||||
| SOA | dns1.yandex.netdns-hosting@yandex.ru serial=6 | ||||||
su
| DNSSEC | 🔒 Signed (DS record present) | ||||||
| NS | a.dns.ripn.net ⭐ | ||||||
| NS | b.dns.ripn.net | ||||||
| NS | c.tld-servers.ru ⚠️ Not in parent delegation | ||||||
| NS | d.dns.ripn.net | ||||||
| NS | e.dns.ripn.net | ||||||
| NS | f.dns.ripn.net | ||||||
| SOA | a.dns.ripn.nethostmaster@ripn.net serial=650209989 | ||||||
Same first word
Similar names
DNS History
3 records (3 active, 0 former)
●NSdns1.yandex.net2015-07-25 → 2026-07-27 · 2 obs
● 2026-07-27 14:02:50
●NSdns2.yandex.net2015-07-25 → 2026-07-27 · 2 obs
● 2026-07-27 14:02:50
●MXmx.yandex.net2015-07-25 → 2026-07-27 · 2 obs
● 2026-07-27 14:02:50
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| su | e.dns.ripn.net, a.dns.ripn.net, b.dns.ripn.net, d.dns.ripn.net... | - |
| insign.su | 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 insign.su (unsigned zone)
⏱️ Timing
Total: 978ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| NS | 2 | dns2.yandex.net, dns1.yandex.net |
| TXT | 1 | v=spf1 redirect=_spf.yandex.net |
| SOA | 1 | dns1.yandex.net dns-hosting.yandex.ru |
Analysis
Name Servers
insign.su is served by two delegated name servers, dns1.yandex.net and dns2.yandex.net.
insign.su has the same name server delegation as a number of other domains, such as seismic.ru, hostlight.info, svsmail.ru and two more.
insign.su has at least partial name server overlap with other domains, such as kemalaydin.com.tr, amazing-club.ru, snick.ru and two others.
These name servers tend to appear together with the name servers dns1.yandex.ru, dns2.yandex.ru and ns1.webegiris.com.
Each of the two host names carries two IP addresses: dns1.yandex.net points to 213.180.204.213 and 2a02:6b8::213, and dns2.yandex.net points to 93.158.134.213 and 2a02:6b8:0:1::213.
Mail Servers
insign.su routes its mail through a single mail server, mx.yandex.net.
insign.su has the same mail server arrangement as a number of other domains, for example smtp-mail.outlook.com.intileo-com-1935292.yaconnect.com, ofaclan.com, vuachungkhoan.com and two more.
insign.su shares at least some of its mail servers with other domains — for example tcse-cms.com, xturk.com, wantbaby.ru and two more.
mx.yandex.net has two IP addresses: 77.88.21.249 and 2a02:6b8::311.