`telegramcraft.ru`

DNSSEC	⚠️ Not signed
A	109.172.101.197^{🇩🇪 RU-JSCIOT109.172.100.0/23}
		PTR	`mail.telegramcraft.ru`
NS	`ns1.reg.ru` ⭐
		A	2a00:f940:9::1:1^{🇷🇺 AS-REGRU2a00:f940:9::/48 Reg.Ru Hosting}
		A	2a00:f940:9::2:1^{🇷🇺 AS-REGRU2a00:f940:9::/48 Reg.Ru Hosting}
		A	176.99.13.11^{🇷🇺 AS-REGRU176.99.13.0/24 Reg.Ru}
		A	176.99.13.13^{🇷🇺 AS-REGRU176.99.13.0/24 Reg.Ru}
		A	176.99.13.15^{🇷🇺 AS-REGRU176.99.13.0/24 Reg.Ru}
		A	176.99.13.17^{🇷🇺 AS-REGRU176.99.13.0/24 Reg.Ru}
		A	194.58.117.11^{🇷🇺 AS-REGRU194.58.117.0/24 Reg.Ru}
			PTR	`ns1.reg.ru`
		A	194.58.117.13^{🇷🇺 AS-REGRU194.58.117.0/24 Reg.Ru}
			PTR	`ns1.reg.ru`
		A	194.58.117.15^{🇷🇺 AS-REGRU194.58.117.0/24 Reg.Ru}
			PTR	`ns1.reg.ru`
		A	194.58.117.17^{🇷🇺 AS-REGRU194.58.117.0/24 Reg.Ru}
			PTR	`ns1.reg.ru`
NS	`ns2.reg.ru`
		A	2a00:f940:9::1:2^{🇷🇺 AS-REGRU2a00:f940:9::/48 Reg.Ru Hosting}
		A	2a00:f940:9::2:2^{🇷🇺 AS-REGRU2a00:f940:9::/48 Reg.Ru Hosting}
		A	176.99.13.12^{🇷🇺 AS-REGRU176.99.13.0/24 Reg.Ru}
		A	176.99.13.14^{🇷🇺 AS-REGRU176.99.13.0/24 Reg.Ru}
		A	176.99.13.16^{🇷🇺 AS-REGRU176.99.13.0/24 Reg.Ru}
		A	176.99.13.18^{🇷🇺 AS-REGRU176.99.13.0/24 Reg.Ru}
		A	194.58.117.12^{🇷🇺 AS-REGRU194.58.117.0/24 Reg.Ru}
			PTR	`ns2.reg.ru`
		A	194.58.117.14^{🇷🇺 AS-REGRU194.58.117.0/24 Reg.Ru}
			PTR	`ns2.reg.ru`
		A	194.58.117.16^{🇷🇺 AS-REGRU194.58.117.0/24 Reg.Ru}
			PTR	`ns2.reg.ru`
		A	194.58.117.18^{🇷🇺 AS-REGRU194.58.117.0/24 Reg.Ru}
			PTR	`ns2.reg.ru`
MX	`mail.telegramcraft.ru` ⭐
		A	109.172.101.197^{🇩🇪 RU-JSCIOT109.172.100.0/23}
			PTR	`mail.telegramcraft.ru`
TXT	`v=spf1 mx a ip4:109.172.101.197 ~all`
SOA	`ns1.reg.ru`hostmaster@ns1.reg.ru serial=1772634805

`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.net`hostmaster@ripn.net serial=4069504

Same first word

telegramcraft.ru

DNS History

4 records (4 active, 0 former)

●NSns1.reg.ru2026-03-26 → 2026-07-05 · 2 obs

● 2026-03-26 16:26:00
● 2026-07-05 13:42:58

●NSns2.reg.ru2026-03-26 → 2026-07-05 · 2 obs

● 2026-03-26 16:26:00
● 2026-07-05 13:42:58

●MXmail.telegramcraft.ru2026-03-26 → 2026-07-05 · 2 obs

● 2026-03-26 16:26:00
● 2026-07-05 13:42:58

●A109.172.101.1972026-03-26 → 2026-07-05 · 2 obs

● 2026-03-26 16:26:00
● 2026-07-05 13:42:58

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
ru	a.dns.ripn.net, b.dns.ripn.net, d.dns.ripn.net, e.dns.ripn.net...	-
telegramcraft.ru	ns1.reg.ru, ns2.reg.ru	20 records

✅ Authoritative Response

Server:176.99.13.11

NS records: ns1.reg.ru, ns2.reg.ru

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for telegramcraft.ru (unsigned zone)

⏱️ Timing

Total: 819ms | Queries: -

📄 Records

Type	Count	Sample Data
A	1	`109.172.101.197`
NS	2	`ns1.reg.ru, ns2.reg.ru`
MX	1	`mail.telegramcraft.ru (pri: 10)`
TXT	1	`v=spf1 mx a ip4:109.172.101.197 ~all`
SOA	1	`ns1.reg.ru hostmaster.ns1.reg.ru`

📌 Glue Records Collected

Total: 20

Out-of-bailiwick: 20 (ns1.reg.ru, ns1.reg.ru, ns1.reg.ru...)

Analysis

IP Addresses

telegramcraft.ru directs to one IP number, which is 109.172.101.197.

Name Servers

DNS delegation for telegramcraft.ru points to two name servers: ns1.reg.ru and ns2.reg.ru.

telegramcraft.ru has the same name server delegation as a number of other domains, such as otlichka.ru, vanmo.ru, vimix.online and two more.

telegramcraft.ru has partial name server overlap with other domains, including otlichnyk.ru.

Host names resolving to 10 IP numbers:

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

telegramcraft.ru routes its mail through a single mail server, mail.telegramcraft.ru.

mail.telegramcraft.ru has exactly one IP number: 109.172.101.197.

telegramcraft.ru - robtex.com