`windows-chrome.ru`

DNSSEC	⚠️ Not signed
A	37.187.83.72^{🇫🇷 OVH37.187.0.0/16}
		PTR	`dns1.ru-tld.ru`
A	176.31.179.191^{🇫🇷 OVH176.31.0.0/16 ISP Paris, France}
NS	`dns1.ru-tld.ru` ⭐
		A	37.187.83.72^{🇫🇷 OVH37.187.0.0/16}
			PTR	`dns1.ru-tld.ru`
NS	`dns.ru-tld.ru`
		A	185.108.84.20^{🇺🇸 LEASEWEB-NL-AMS-01185.108.84.0/23 MTND}
			PTR	`dns.ru-tld.ru`
NS	`dns2.ru-tld.ru`
		A	176.31.179.191^{🇫🇷 OVH176.31.0.0/16 ISP Paris, France}
			PTR	`dns2.ru-tld.ru`
TXT	`eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJEb21haW5TaG9wIiwic3ViIjoiNTU1...`
TXT	`v=spf1 ip4:127.0.0.1 -all`
TXT	`v=DMARC1; p=reject; pct=100; sp=reject; adkim=s; aspf=s; fo=1;`
SOA	`dns.ru-tld.ru`support@ru-tld.ru 2014-03-22 #28

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

⚠️ On DNS blocklist: tif

Same first word

windows-chrome.ru

DNS History

8 records (5 active, 3 former)

●NSdns.ru-tld.ru2026-03-20 → 2026-05-12 · 3 obs

○ 2026-03-13 05:23:56
● 2026-03-20 08:33:48
● 2026-05-12 05:45:30

●NSdns1.ru-tld.ru2026-03-13 → 2026-05-12 · 3 obs

○ 2019-04-12 13:32:40
● 2026-03-13 05:23:56
● 2026-05-12 05:45:30

●NSdns2.ru-tld.ru2026-03-13 → 2026-05-12 · 3 obs

○ 2019-04-12 13:32:40
● 2026-03-13 05:23:56
● 2026-05-12 05:45:30

○NSns1.reg.ru2019-04-12 → 2019-04-12 · 3 obs

● 2019-04-12 13:32:40
○ 2026-03-13 05:23:56
○ 2026-05-12 05:45:30

○NSns2.reg.ru2019-04-12 → 2019-04-12 · 3 obs

● 2019-04-12 13:32:40
○ 2026-03-13 05:23:56
○ 2026-05-12 05:45:30

●A176.31.179.1912026-03-20 → 2026-05-12 · 3 obs

○ 2026-03-13 05:23:56
● 2026-03-20 08:33:48
● 2026-05-12 05:45:30

●A37.187.83.722026-03-20 → 2026-05-12 · 3 obs

○ 2026-03-13 05:23:56
● 2026-03-20 08:33:48
● 2026-05-12 05:45:30

○A93.179.69.872019-04-12 → 2019-04-12 · 3 obs

● 2019-04-12 13:32:40
○ 2026-03-13 05:23:56
○ 2026-05-12 05:45:30

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
ru	b.dns.ripn.net, d.dns.ripn.net, e.dns.ripn.net, f.dns.ripn.net...	-
windows-chrome.ru	dns2.ru-tld.ru, dns1.ru-tld.ru	-

✅ Authoritative Response

Server:176.31.179.191

NS records: dns2.ru-tld.ru, dns1.ru-tld.ru

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for windows-chrome.ru (unsigned zone)

⏱️ Timing

Total: 4673ms | Queries: -

📄 Records

Type	Count	Sample Data
A	2	`176.31.179.191, 37.187.83.72`
NS	2	`dns1.ru-tld.ru, dns2.ru-tld.ru`
TXT	3	`v=DMARC1; p=reject; pct=100; sp=reject; , eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJ...`
SOA	1	`dns.ru-tld.ru support.ru-tld.ru`

Analysis

IP Addresses

windows-chrome.ru points to two IP numbers: 37.187.83.72 and 176.31.179.191.

Other host names such as eskhosting.ru, beig.ru, darknet.su, celox.ru and messenger.su share IP numbers with windows-chrome.ru.

Name Servers

windows-chrome.ru is delegated to three name servers: dns1.ru-tld.ru, dns2.ru-tld.ru and dns.ru-tld.ru.

At least part of the name servers for windows-chrome.ru are shared with other domains, for instance rf.su, drevil.ru, xn--j1ain.xn--p1ai, youanime.ru and stuka.ladoga-spb.ru.

These name servers are often used together with dns1.ru-ltd.ru, dns2.ru-ltd.ru and parking.ru-tld.ru.

Host names with a single IP:

dns1.ru-tld.ru points to: 37.187.83.72

dns2.ru-tld.ru points to: 176.31.179.191

dns.ru-tld.ru points to: 185.108.84.20

windows-chrome.ru - robtex.com