`telegram-verification.online`

DNSSEC	⚠️ Not signed
A	87.120.107.209^{🇮🇹 shinomiya87.120.107.0/24}
		PTR	`fl-13.hosted-by.shinomiya-hosting.com`
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}
			PTR	`ns1.reg.ru`
		A	176.99.13.13^{🇷🇺 AS-REGRU176.99.13.0/24 Reg.Ru}
			PTR	`ns1.reg.ru`
		A	176.99.13.15^{🇷🇺 AS-REGRU176.99.13.0/24 Reg.Ru}
			PTR	`ns1.reg.ru`
		A	176.99.13.17^{🇷🇺 AS-REGRU176.99.13.0/24 Reg.Ru}
			PTR	`ns1.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}
			PTR	`ns2.reg.ru`
		A	176.99.13.14^{🇷🇺 AS-REGRU176.99.13.0/24 Reg.Ru}
			PTR	`ns2.reg.ru`
		A	176.99.13.16^{🇷🇺 AS-REGRU176.99.13.0/24 Reg.Ru}
			PTR	`ns2.reg.ru`
		A	176.99.13.18^{🇷🇺 AS-REGRU176.99.13.0/24 Reg.Ru}
			PTR	`ns2.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`
SOA	`ns1.reg.ru`hostmaster@ns1.reg.ru serial=1779803135

`online`

	DNSSEC	🔒 Signed (DS record present)
	NS	`ns01.trs-dns.com` ⭐
	NS	`ns.trs-dns.com`
	NS	`ns01.trs-dns.net`
	NS	`ns10.trs-dns.info`
	NS	`ns10.trs-dns.org`
	SOA	`ns.trs-dns.com`trs-ops@tucows.com serial=1786463012

⚠️ On DNS blocklist: tif
⚠️ On DNS blocklist: spam-tlds

Same first word

telegram-verification.net

telegram-verification.org

telegram-verification.online

Similar names

verification-telegram.org

DNS History

3 records (3 active, 0 former)

●NSns1.reg.ru2026-07-27 → 2026-08-11 · 2 obs

● 2026-07-27 04:19:58
● 2026-08-11 15:49:16

●NSns2.reg.ru2026-07-27 → 2026-08-11 · 2 obs

● 2026-07-27 04:19:58
● 2026-08-11 15:49:16

●A87.120.107.2092026-07-27 → 2026-08-11 · 2 obs

● 2026-07-27 04:19:58
● 2026-08-11 15:49:16

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
online	ns01.trs-dns.com, ns01.trs-dns.net, ns10.trs-dns.org, ns10.trs-dns.info	8 records
telegram-verification.online	ns1.reg.ru, ns2.reg.ru	-

✅ Authoritative Response

Server:176.99.13.12

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

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for telegram-verification.online (unsigned zone)

⏱️ Timing

Total: 2318ms | Queries: -

📄 Records

Type	Count	Sample Data
A	1	`87.120.107.209`
NS	2	`ns1.reg.ru, ns2.reg.ru`
SOA	1	`ns1.reg.ru hostmaster.ns1.reg.ru`

📌 Glue Records Collected

Total: 8

Out-of-bailiwick: 8 (ns01.trs-dns.com, ns01.trs-dns.com, ns01.trs-dns.net...)

Analysis

IP Addresses

telegram-verification.online resolves to just one IP address, 87.120.107.209.

Two other host names, along with telegram-gov-service.online, telegram-gov-service.ru and telegram-account-access.click, also share IP numbers with telegram-verification.online.

Name Servers

telegram-verification.online uses two name servers for its delegation: ns1.reg.ru and ns2.reg.ru.

telegram-verification.online shares its NS records with other domains, for example 383servis.ru, traveltunisia.ru, pawno-crmp.ru and two others.

DNS names with 10 IP addresses:

Hostname ns1.reg.ru directs to 176.99.13.11, 176.99.13.13 and 176.99.13.15 along with 7 other IP addresses.

Hostname ns2.reg.ru directs to 176.99.13.12, 176.99.13.14 and 176.99.13.16 along with 7 other IP addresses.

telegram-verification.online - robtex.com