`bridge-telecom.ru`

DNSSEC	⚠️ Not signed
A	178.210.72.200^{🇷🇺 RU-CENTER178.210.64.0/20 -HOSTING}
		PTR	`sma.nichost.ru`
NS	`ns3-l2.nic.ru` ⭐
		A	193.232.146.1^{🇷🇺 RU-CENTER193.232.146.0/24 -NETWORK}
			PTR	`ns3-l2.nic.ru`
NS	`ns4-cloud.nic.ru`
		A	89.104.93.30^{🇷🇺 ANYCAST-AS89.104.93.0/24 Ru-Center route}
		A	89.104.93.33^{🇷🇺 ANYCAST-AS89.104.93.0/24 Ru-Center route}
		A	89.104.93.34^{🇷🇺 ANYCAST-AS89.104.93.0/24 Ru-Center route}
		A	89.104.95.30^{🇷🇺 ANYCAST-AS89.104.95.0/24 Ru-Center route}
		A	89.104.95.33^{🇷🇺 ANYCAST-AS89.104.95.0/24 Ru-Center route}
		A	89.104.95.34^{🇷🇺 ANYCAST-AS89.104.95.0/24 Ru-Center route}
NS	`ns4-l2.nic.ru`
		A	91.217.20.20^{🇷🇺 RU-CENTER91.217.20.0/24}
			PTR	`ns4-l2.nic.ru`
NS	`ns8-cloud.nic.ru`
		A	89.104.93.31^{🇷🇺 ANYCAST-AS89.104.93.0/24 Ru-Center route}
		A	89.104.93.35^{🇷🇺 ANYCAST-AS89.104.93.0/24 Ru-Center route}
		A	89.104.93.36^{🇷🇺 ANYCAST-AS89.104.93.0/24 Ru-Center route}
		A	89.104.95.31^{🇷🇺 ANYCAST-AS89.104.95.0/24 Ru-Center route}
		A	89.104.95.35^{🇷🇺 ANYCAST-AS89.104.95.0/24 Ru-Center route}
		A	89.104.95.36^{🇷🇺 ANYCAST-AS89.104.95.0/24 Ru-Center route}
NS	`ns8-l2.nic.ru`
		A	91.217.21.20^{🇷🇺 RU-CENTER-AS91.217.21.0/24 RU-CENTER}
			PTR	`ns8-l2.nic.ru`
MX	`mx02.nicmail.ru` ⭐
		A	91.189.116.13^{🇷🇺 RU-CENTER91.189.116.0/22 RU-NIC-HOSTING}
			PTR	`mx01.nicmail.ru`
		A	91.189.116.14^{🇷🇺 RU-CENTER91.189.116.0/22 RU-NIC-HOSTING}
			PTR	`mx01.nicmail.ru`
		A	91.189.116.15^{🇷🇺 RU-CENTER91.189.116.0/22 RU-NIC-HOSTING}
			PTR	`mx01.nicmail.ru`
		A	91.189.116.16^{🇷🇺 RU-CENTER91.189.116.0/22 RU-NIC-HOSTING}
			PTR	`mx01.nicmail.ru`
MX	`mx01.nicmail.ru`⁽¹⁰⁾
		A	91.189.116.13^{🇷🇺 RU-CENTER91.189.116.0/22 RU-NIC-HOSTING}
			PTR	`mx01.nicmail.ru`
		A	91.189.116.14^{🇷🇺 RU-CENTER91.189.116.0/22 RU-NIC-HOSTING}
			PTR	`mx01.nicmail.ru`
		A	91.189.116.15^{🇷🇺 RU-CENTER91.189.116.0/22 RU-NIC-HOSTING}
			PTR	`mx01.nicmail.ru`
		A	91.189.116.16^{🇷🇺 RU-CENTER91.189.116.0/22 RU-NIC-HOSTING}
			PTR	`mx01.nicmail.ru`
MX	`mx03.nicmail.ru`⁽²⁰⁾
		A	91.189.116.16^{🇷🇺 RU-CENTER91.189.116.0/22 RU-NIC-HOSTING}
			PTR	`mx01.nicmail.ru`
TXT	`v=spf1 redirect=nicmail.ru`
TXT	`2018110215121824l18z80c03h0gc6yz1uir63qje7yoairj5r7lktdxd1x3bf5f`
TXT	`201904250755051vzpgmrfbge7bp735jzbodagkd060kk4xk76cz88cfbi1rdr40`
TXT	`202003242131042h3yfib4dl1i3acr14xgya754k0f3nnra0z9un2wdijdo3jus4`
TXT	`202105082127046dl4uvwirj71n35smkvlcf1xr3k9pqw0ktm0rgkc187x2m587a`
TXT	`globalsign-domain-verification=eb3C1ARNmFOR8Nm8pTNlpFnxt4nPbjhq3eExLWe30-`
TXT	`globalsign-domain-verification=wsdB-MAx9_j4deoUTr8YijJ_2HZBXvMF-DwkQc95W8`
TXT	`_globalsign-domain-verification=1wf4MdziyP6h2wXK5jAxqwkvNmfddw1F2Yyjv6iSME`
TXT	`_globalsign-domain-verification=2kWYBfqB5yEM404_elazBQV5s4YdbeSYxo2EYDR5nD`
TXT	`_globalsign-domain-verification=49UhSBnyAkfzAaCNskXFSk5IiDQclRARYAivqw5p21`
TXT	`_globalsign-domain-verification=7NtmqqOSifp58vt-OrZtub-0gewVs11CVZblVFTFHJ`
TXT	`_globalsign-domain-verification=AjszYelgvQDVDFHZWAveheJFCRdphWnAn1tnfxANQB`
TXT	`_globalsign-domain-verification=QacIiUbqQoWNdKIA26ww_uKav21aqWvFcE_49IXH0k`
TXT	`_globalsign-domain-verification=U28qCBQavucE5wyDe4agpHN2ipEO4jD3kKm1Elt4Ve`
TXT	`_globalsign-domain-verification=XfJX1RIVoab90j-2jw6Ips99T9adQyVNMJjMEETRwI`
TXT	`_globalsign-domain-verification=dLAZfuhDQVsbRWfYIP2xWIJDxMs9bgPjHY45ntHJTW`
TXT	`_globalsign-domain-verification=rvpPH5b0PGYRH6U9mlDhJrzlIGg6p3HB5nSQAcY77A`
SOA	`ns3-l2.nic.ru`support@nic.ru 2020-05-15 #35

`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=4068497

Same first word

bridge-telecom.net

bridge-telecom.ru

DNS History

15 records (9 active, 6 former)

○NSns1.digitalocean.com2016-09-23 → 2016-09-23 · 4 obs

○ 2016-03-26 21:16:32
● 2016-09-23 02:59:14
○ 2019-02-18 07:02:24
○ 2026-04-13 07:31:36

○NSns2.digitalocean.com2016-09-23 → 2016-09-23 · 4 obs

○ 2016-03-26 21:16:32
● 2016-09-23 02:59:14
○ 2019-02-18 07:02:24
○ 2026-04-13 07:31:36

●NSns3-l2.nic.ru2015-08-21 → 2026-04-13 · 5 obs

● 2015-08-21 17:37:32
● 2016-03-26 21:16:32
○ 2016-09-23 02:59:14
● 2019-02-18 07:02:24
● 2026-04-13 07:31:36

○NSns3.digitalocean.com2016-09-23 → 2016-09-23 · 4 obs

○ 2016-03-26 21:16:32
● 2016-09-23 02:59:14
○ 2019-02-18 07:02:24
○ 2026-04-13 07:31:36

●NSns4-cloud.nic.ru2015-08-21 → 2026-04-13 · 5 obs

● 2015-08-21 17:37:32
● 2016-03-26 21:16:32
○ 2016-09-23 02:59:14
● 2019-02-18 07:02:24
● 2026-04-13 07:31:36

●NSns4-l2.nic.ru2015-08-21 → 2026-04-13 · 5 obs

● 2015-08-21 17:37:32
● 2016-03-26 21:16:32
○ 2016-09-23 02:59:14
● 2019-02-18 07:02:24
● 2026-04-13 07:31:36

●NSns8-cloud.nic.ru2015-08-21 → 2026-04-13 · 5 obs

● 2015-08-21 17:37:32
● 2016-03-26 21:16:32
○ 2016-09-23 02:59:14
● 2019-02-18 07:02:24
● 2026-04-13 07:31:36

●NSns8-l2.nic.ru2015-08-21 → 2026-04-13 · 5 obs

● 2015-08-21 17:37:32
● 2016-03-26 21:16:32
○ 2016-09-23 02:59:14
● 2019-02-18 07:02:24
● 2026-04-13 07:31:36

●MXmx01.nicmail.ru2015-08-21 → 2026-04-13 · 2 obs

● 2015-08-21 17:37:32
● 2026-04-13 07:31:36

●MXmx02.nicmail.ru2015-08-21 → 2026-04-13 · 2 obs

● 2015-08-21 17:37:32
● 2026-04-13 07:31:36

●MXmx03.nicmail.ru2015-08-21 → 2026-04-13 · 2 obs

● 2015-08-21 17:37:32
● 2026-04-13 07:31:36

○A128.199.189.2242016-09-23 → 2016-09-23 · 4 obs

○ 2016-03-26 21:16:32
● 2016-09-23 02:59:14
○ 2019-02-18 07:02:24
○ 2026-04-13 07:31:36

●A178.210.72.2002026-03-27 → 2026-04-13 · 3 obs

○ 2019-02-18 07:02:24
● 2026-03-27 13:08:58
● 2026-04-13 07:31:36

○A195.208.1.1162015-08-21 → 2016-03-26 · 4 obs

● 2015-08-21 17:37:32
● 2016-03-26 21:16:32
○ 2016-09-23 02:59:14
○ 2026-04-13 07:31:36

○A212.193.249.982019-02-18 → 2019-02-18 · 4 obs

○ 2016-09-23 02:59:14
● 2019-02-18 07:02:24
○ 2026-03-27 13:08:58
○ 2026-04-13 07:31:36

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
ru	f.dns.ripn.net, e.dns.ripn.net, d.dns.ripn.net, b.dns.ripn.net...	-
bridge-telecom.ru	ns8-l2.nic.ru, ns3-l2.nic.ru, ns4-cloud.nic.ru, ns8-cloud.nic.ru...	19 records

✅ Authoritative Response

Server:91.217.21.20

NS records: ns8-l2.nic.ru, ns3-l2.nic.ru, ns4-cloud.nic.ru, ns8-cloud.nic.ru, ns4-l2.nic.ru

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for bridge-telecom.ru (unsigned zone)

⏱️ Timing

Total: 1048ms | Queries: -

📄 Records

Type	Count	Sample Data
A	1	`178.210.72.200`
NS	5	`ns3-l2.nic.ru, ns4-l2.nic.ru...`
MX	3	`mx02.nicmail.ru (pri: 5), mx01.nicmail.ru (pri: 10)...`
TXT	17	`v=spf1 redirect=nicmail.ru, 2018110215121824l18z80c03h0gc6yz1uir63qj...`
SOA	1	`ns3-l2.nic.ru support.nic.ru`

📌 Glue Records Collected

Total: 19

Out-of-bailiwick: 19 (ns8-cloud.nic.ru, ns8-cloud.nic.ru, ns8-cloud.nic.ru...)

Analysis

IP Addresses

bridge-telecom.ru points to a single IP address: 178.210.72.200.

Name Servers

bridge-telecom.ru is delegated to five name servers: ns3-l2.nic.ru, ns4-cloud.nic.ru, ns4-l2.nic.ru, ns8-cloud.nic.ru and ns8-l2.nic.ru.

At least part of the name servers for bridge-telecom.ru are shared with other domains, for instance don-plaza.ru, untsoft.com, ns-studio.org, 1edi.ru and adm-eg.ru.

These name servers are often used together with ns3.nic.ru, dns1.yandex.net and dns2.yandex.net.

Host names by IP count:

Six IP numbers:

- ns4-cloud.nic.ru points to: 89.104.93.30, 89.104.93.33, 89.104.93.34, 89.104.95.30, 89.104.95.33 and 89.104.95.34

- ns8-cloud.nic.ru points to: 89.104.93.31, 89.104.93.35, 89.104.93.36, 89.104.95.31, 89.104.95.35 and 89.104.95.36

One IP number:

- ns3-l2.nic.ru points to: 193.232.146.1

- ns4-l2.nic.ru points to: 91.217.20.20

- ns8-l2.nic.ru points to: 91.217.21.20

Mail Servers

Three mail servers handle bridge-telecom.ru: mx01.nicmail.ru, mx02.nicmail.ru and mx03.nicmail.ru.

bridge-telecom.ru shares at least some mail servers with other domains, for example h003302160.nichost.ru, megaflag.ru, dsbb.ru, itword.net and ae69.ru.