`rumorsmonitoring.com`

DNSSEC	⚠️ Not signed
A	20.49.97.14^{🇺🇸 Microsoft20.48.0.0/12}
NS	`dns1.yandex.net` ⭐
		A	2a02:6b8::213^{🇷🇺 TELETECH2a02:6b8::/32 Yandex network}
			PTR	`dns1.yandex.net`
		A	213.180.204.213^{🇷🇺 TELETECH213.180.192.0/19 Yandex network}
			PTR	`dns1.yandex.net`
NS	`dns2.yandex.net`
		A	2a02:6b8:0:1::213^{🇷🇺 TELETECH2a02:6b8::/32 Yandex network}
			PTR	`dns2.yandex.net`
		A	93.158.134.213^{🇷🇺 TELETECH93.158.128.0/18 Yandex enterprise network}
			PTR	`dns2.yandex.net`
MX	`aspmx.l.google.com` ⭐
		A	2607:f8b0:4023:c03::1a^{🇺🇸 Google2607:f8b0::/32}
			PTR	`dy-in-f26.1e100.net`
		A	142.250.141.26^{🇺🇸 Google142.250.141.0/24}
			PTR	`dd-in-f26.1e100.net`
MX	`alt1.aspmx.l.google.com`⁽⁵⁾
		A	2a00:1450:4025:402::1b^{🇳🇱 Google2a00:1450:4025::/48}
			PTR	`rb-in-f27.1e100.net`
		A	142.250.102.27^{🇺🇸 Google142.250.102.0/24}
			PTR	`rb-in-f27.1e100.net`
MX	`alt2.aspmx.l.google.com`⁽⁵⁾
		A	2a00:1450:4013:c1e::1a^{🇳🇱 Google2a00:1450:4013::/48}
			PTR	`yugrqzs-in-f26.1e100.net`
		A	192.178.213.26^{🇺🇸 Google192.178.213.0/24}
			PTR	`yugrqzs-in-f26.1e100.net`
MX	`alt3.aspmx.l.google.com`⁽¹⁰⁾
		A	2a00:1450:4001:c21::1b^{🇩🇪 Google2a00:1450:4001::/48}
			PTR	`lcfrai-in-f27.1e100.net`
		A	142.251.127.27^{🇺🇸 Google142.251.127.0/24}
			PTR	`lcfrai-in-f27.1e100.net`
MX	`alt4.aspmx.l.google.com`⁽¹⁰⁾
		A	2a00:1450:4025:c01::1a^{🇵🇱 Google2a00:1450:4025::/48}
			PTR	`rd-in-f26.1e100.net`
		A	142.250.147.27^{🇺🇸 Google142.250.147.0/24}
			PTR	`rd-in-f27.1e100.net`
TXT	`61lgg5etorvrft3iv4d4i5c985`
TXT	`google-site-verification=iQz3DF9zoFZDUhgFPICDf5r9nzgN-UerDbaXWsntWec`
TXT	`MS=ms55545204`
TXT	`4jev047aatsiu98j5hosdip7es`
TXT	`google-site-verification=jdDkGragJipbETwzuXrRIy-nfNN6KBgo2UVG_WXk0ls`
TXT	`v=spf1 include:mailgun.org include:_spf.google.com -all`
TXT	`rumorsmonitoringlanding-eus2.azurewebsites.net`
TXT	`cdme2i5cdtoihnqakf94on95dg`
SOA	`dns1.yandex.net`dns-hosting@yandex.ru serial=76

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

Subdomains

www.rumorsmonitoring.com

Same first word

rumorsmonitoring.com

DNS History

10 records (8 active, 2 former)

●NSdns1.yandex.net2016-12-16 → 2026-04-06 · 2 obs

● 2016-12-16 22:34:54
● 2026-04-06 20:52:44

●NSdns2.yandex.net2016-12-16 → 2026-04-06 · 2 obs

● 2016-12-16 22:34:54
● 2026-04-06 20:52:44

●MXalt1.aspmx.l.google.com2026-04-01 → 2026-04-06 · 3 obs

○ 2016-12-16 22:34:54
● 2026-04-01 00:47:32
● 2026-04-06 20:52:44

●MXalt2.aspmx.l.google.com2026-04-01 → 2026-04-06 · 3 obs

○ 2016-12-16 22:34:54
● 2026-04-01 00:47:32
● 2026-04-06 20:52:44

●MXalt3.aspmx.l.google.com2026-04-01 → 2026-04-06 · 3 obs

○ 2016-12-16 22:34:54
● 2026-04-01 00:47:32
● 2026-04-06 20:52:44

●MXalt4.aspmx.l.google.com2026-04-01 → 2026-04-06 · 3 obs

○ 2016-12-16 22:34:54
● 2026-04-01 00:47:32
● 2026-04-06 20:52:44

●MXaspmx.l.google.com2026-04-01 → 2026-04-06 · 3 obs

○ 2016-12-16 22:34:54
● 2026-04-01 00:47:32
● 2026-04-06 20:52:44

○MXmx.yandex.net2016-12-16 → 2016-12-16 · 3 obs

● 2016-12-16 22:34:54
○ 2026-04-01 00:47:32
○ 2026-04-06 20:52:44

○A13.80.16.662016-12-16 → 2016-12-16 · 3 obs

● 2016-12-16 22:34:54
○ 2026-04-01 00:47:32
○ 2026-04-06 20:52:44

●A20.49.97.142026-04-01 → 2026-04-06 · 3 obs

○ 2016-12-16 22:34:54
● 2026-04-01 00:47:32
● 2026-04-06 20:52:44

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	a.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net...	-
rumorsmonitoring.com	dns1.yandex.net, dns2.yandex.net	-

✅ Authoritative Response

Server:213.180.204.213

NS records: dns1.yandex.net, dns2.yandex.net

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for rumorsmonitoring.com (unsigned zone)

⏱️ Timing

Total: 961ms | Queries: -

📄 Records

Type	Count	Sample Data
A	1	`20.49.97.14`
NS	2	`dns2.yandex.net, dns1.yandex.net`
MX	5	`aspmx.l.google.com (pri: 1), alt2.aspmx.l.google.com (pri: 5)...`
TXT	8	`61lgg5etorvrft3iv4d4i5c985, google-site-verification=iQz3DF9zoFZDUhg...`
SOA	1	`dns1.yandex.net dns-hosting.yandex.ru`

Analysis

Hierarchy

www.rumorsmonitoring.com has rumorsmonitoring.com as its parent.

IP Addresses

rumorsmonitoring.com maps to IP address 20.49.97.14.

Other host names, for instance ns2a.promodel.com, ns1.promodel.com, promodel.com, waws-prod-bn1-101-a2b8.eastus2.cloudapp.azure.com and ns2.promodel.com share IP numbers with rumorsmonitoring.com.

Name Servers

Two name servers dns1.yandex.net and dns2.yandex.net are delegated to rumorsmonitoring.com.

rumorsmonitoring.com uses the same name server configuration as other domains, such as oknabnw.ru, gadget-device.ru, xn--80ahdmgknde2b.su, forte-it.ru and tzargrad.ru.

rumorsmonitoring.com at least partially shares name servers with other domains such as agaming.ru, xn--24-6kcxll5b.xn--p1ai, inshaker.ru, dnlv.ru and abyhan.ru.