`zip-go.com`

DNSSEC	⚠️ Not signed
A	176.57.64.35^{🇧🇦 DDOS-GUARD176.57.64.0/23}
NS	`ns3-l2.nic.ru` ⭐
		A	193.232.146.1^{🇷🇺 RU-CENTER193.232.146.0/24 -NETWORK}
			PTR	`ns3-l2.nic.ru`
NS	`ns3.nic.ru`
		A	194.85.61.20^{🇷🇺 RU-CENTER194.85.61.0/24 RUNIC}
			PTR	`ns3.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	`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`
TXT	`yandex-verification: 351cb5e8d165f3a1`
SOA	`ns3.nic.ru`support@nic.ru 2022-02-01 #25

`com`

	DNSSEC	🔒 Signed (DS record present)
	NS	`a.gtld-servers.net` ⭐
	NS	`b.gtld-servers.net`
	NS	`c.gtld-servers.net`
	NS	`d.gtld-servers.net`
	NS	`e.gtld-servers.net`
	NS	`f.gtld-servers.net`
	NS	`g.gtld-servers.net`
	NS	`h.gtld-servers.net`
	NS	`i.gtld-servers.net`
	NS	`j.gtld-servers.net`
	NS	`k.gtld-servers.net`
	NS	`l.gtld-servers.net`
	NS	`m.gtld-servers.net`
	SOA	`a.gtld-servers.net`nstld@verisign-grs.com serial=1774576962

Same first word

zip-go.com

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	a.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net...	-
zip-go.com	ns8-l2.nic.ru, ns4-l2.nic.ru, ns3-l2.nic.ru, ns8-cloud.nic.ru...	-

✅ Authoritative Response

Server:91.217.20.20

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

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for zip-go.com (unsigned zone)

⏱️ Timing

Total: 979ms | Queries: -

📄 Records

Type	Count	Sample Data
A	1	`176.57.64.35`
NS	5	`ns3-l2.nic.ru, ns4-l2.nic.ru...`
MX	1	`mx.yandex.net (pri: 10)`
TXT	2	`v=spf1 redirect=_spf.yandex.net, yandex-verification: 351cb5e8d165f3a1`
SOA	1	`ns3.nic.ru support.nic.ru`

Analysis

IP Addresses

zip-go.com points to a single IP number: 176.57.64.35.

other host names for instance www.ezda.ru, studiomarideco.ru, superotziv.ru, ezda.ru and stefa55.ru share IP numbers with zip-go.com.

Name Servers

zip-go.com is delegated to six name servers: ns3-l2.nic.ru, ns3.nic.ru, ns4-cloud.nic.ru, ns4-l2.nic.ru, ns8-cloud.nic.ru and ns8-l2.nic.ru.

zip-go.com at least partially shares name servers with other domains, for instance h213128099.nichost.ru, rusjet.ru, goodgate.ru, nakano.ru and niiosp.ru.