ticketing.su - dns.ninja
ticketing.su
su
| 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=650209943 | ||||||
Same first word
Similar names
DNS History
12 records (6 active, 6 former)
○NSns1.agava.net.ru2015-08-18 → 2016-09-08 · 4 obs
● 2016-09-08 12:29:58
○ 2017-05-30 06:59:02
○ 2026-07-23 17:19:54
●NSns1.reg.ru2017-05-30 → 2026-07-23 · 3 obs
● 2017-05-30 06:59:02
● 2026-07-23 17:19:54
○NSns2.agava.net.ru2015-08-18 → 2016-09-08 · 4 obs
● 2016-09-08 12:29:58
○ 2017-05-30 06:59:02
○ 2026-07-23 17:19:54
●NSns2.reg.ru2017-05-30 → 2026-07-23 · 3 obs
● 2017-05-30 06:59:02
● 2026-07-23 17:19:54
○MXcluster.relay.agava.net2015-08-18 → 2026-04-07 · 4 obs
● 2026-04-07 23:58:00
○ 2026-07-04 00:57:32
○ 2026-07-23 17:19:54
●MXmx1.hosting.reg.ru2026-07-04 → 2026-07-23 · 3 obs
● 2026-07-04 00:57:32
● 2026-07-23 17:19:54
●MXmx2.hosting.reg.ru2026-07-04 → 2026-07-23 · 3 obs
● 2026-07-04 00:57:32
● 2026-07-23 17:19:54
●A2a00:f940:2:2:1:4:0:952026-03-11 → 2026-07-23 · 3 obs
● 2026-03-11 11:24:02
● 2026-07-23 17:19:54
○A2a03:4900:0:6037:80:78:250:142015-08-18 → 2017-05-30 · 4 obs
● 2017-05-30 06:59:02
○ 2026-03-11 11:24:02
○ 2026-07-23 17:19:54
●A31.31.197.862026-07-04 → 2026-07-23 · 3 obs
● 2026-07-04 00:57:32
● 2026-07-23 17:19:54
○A31.31.198.1992026-03-11 → 2026-04-07 · 5 obs
● 2026-03-11 11:24:02
● 2026-04-07 23:58:00
○ 2026-07-04 00:57:32
○ 2026-07-23 17:19:54
○A80.78.250.142015-08-18 → 2017-05-30 · 4 obs
● 2017-05-30 06:59:02
○ 2026-03-11 11:24:02
○ 2026-07-23 17:19:54
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| su | a.dns.ripn.net, b.dns.ripn.net, d.dns.ripn.net, e.dns.ripn.net... | - |
| ticketing.su | ns2.reg.ru, ns1.reg.ru | - |
✅ Authoritative Response
Server:176.99.13.12
NS records: ns2.reg.ru, ns1.reg.ru
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for ticketing.su (unsigned zone)
⏱️ Timing
Total: 2081ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 1 | 31.31.197.86 |
| AAAA | 1 | 2a00:f940:2:2:1:4:0:95 |
| NS | 2 | ns1.reg.ru, ns2.reg.ru |
| MX | 2 | mx1.hosting.reg.ru (pri: 10), mx2.hosting.reg.ru (pri: 20) |
| TXT | 1 | v=spf1 ip4:80.78.250.14 ip4:31.31.197.86 |
| SOA | 1 | ns1.reg.ru hostmaster.ns1.reg.ru |
Analysis
IP Addresses
ticketing.su directs to two IP numbers, 31.31.197.86 and 2a00:f940:2:2:1:4:0:95
zato-lokomotivny.ru, artdefacto.ru, kolokolchik7-anapa.social-host.ru and two other host names share IP numbers with ticketing.su.
Name Servers
DNS delegation for ticketing.su points to two name servers: ns1.reg.ru and ns2.reg.ru.
ticketing.su uses the same name servers as several other domains — among them lazerom.ru, tracex.ru, nethouse.msk.su and two more.
Hostnames that resolve to 10 IP addresses:
ns1.reg.ru has IP addresses 176.99.13.11, 176.99.13.13 and 176.99.13.15, plus 7 other.
ns2.reg.ru has IP addresses 176.99.13.12, 176.99.13.14 and 176.99.13.16, plus 7 other.
Mail Servers
Mail for ticketing.su is handled by two mail servers — mx1.hosting.reg.ru and mx2.hosting.reg.ru.
ticketing.su uses an identical mail server configuration to several other domains — among them forauto24.com, xn--c1ajbfgrbfhip5n.xn--p1ai, biz-news.ru and two more.
ticketing.su has at least partial mail server overlap with other domains such as rosalliance.ru, sev-reu.ru, nasa-service.ru and two more.
This set of mail servers commonly appears together with the mail servers mx.yandex.net.
mx1.hosting.reg.ru resolves to 31.31.194.240 and 31.31.194.241; mx2.hosting.reg.ru resolves to the same two IP addresses: 31.31.194.240 and 31.31.194.241.
Host names pointing to 31.31.194.240 IP addresses: mx1.hosting.reg.ru and mx2.hosting.reg.ru.
Host names pointing to 31.31.194.241 IP addresses: mx1.hosting.reg.ru and mx2.hosting.reg.ru.