wmidbot.com - dns.ninja

`wmidbot.com`

DNSSEC	⚠️ Not signed
A	2a0b:6903:fdb:c425:c:e628:fd27:4478^{🇷🇺 GalaxyData2a0b:6903:fdb::/48}
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	`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`
SOA	`dns1.yandex.net`dns-hosting@yandex.ru serial=8

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

WOT: SAFE (50/100)

Same first word

wmidbot.com

DNS History

17 records (4 active, 13 former)

○NSbob.ns.cloudflare.com2015-07-08 → 2017-05-15 · 4 obs

● 2015-07-08 09:50:28
● 2017-05-15 17:09:50
○ 2026-03-05 19:07:10
○ 2026-08-07 03:22:18

●NSdns1.yandex.net2026-03-09 → 2026-08-07 · 3 obs

○ 2026-03-05 19:07:10
● 2026-03-09 15:20:08
● 2026-08-07 03:22:18

●NSdns2.yandex.net2026-03-09 → 2026-08-07 · 3 obs

○ 2026-03-05 19:07:10
● 2026-03-09 15:20:08
● 2026-08-07 03:22:18

○NSdora.ns.cloudflare.com2015-07-08 → 2017-05-15 · 4 obs

● 2015-07-08 09:50:28
● 2017-05-15 17:09:50
○ 2026-03-05 19:07:10
○ 2026-08-07 03:22:18

○NSns1.ua-hosting.company2026-03-05 → 2026-03-05 · 4 obs

○ 2017-05-15 17:09:50
● 2026-03-05 19:07:10
○ 2026-03-09 15:20:08
○ 2026-08-07 03:22:18

○NSns2.ua-hosting.company2026-03-05 → 2026-03-05 · 4 obs

○ 2017-05-15 17:09:50
● 2026-03-05 19:07:10
○ 2026-03-09 15:20:08
○ 2026-08-07 03:22:18

○MXdc-06ece19cbd69.wmidbot.com2017-05-15 → 2017-05-15 · 4 obs

○ 2016-06-18 02:23:38
● 2017-05-15 17:09:50
○ 2026-03-05 19:07:10
○ 2026-08-07 03:22:18

○MXdc-bfb5f580-mail.wmidbot.com2016-06-18 → 2016-06-18 · 4 obs

○ 2016-02-12 07:51:14
● 2016-06-18 02:23:38
○ 2017-05-15 17:09:50
○ 2026-08-07 03:22:18

○MXmail.imena.com.ua2015-07-08 → 2016-02-12 · 4 obs

● 2015-07-08 09:50:28
● 2016-02-12 07:51:14
○ 2016-06-18 02:23:38
○ 2026-08-07 03:22:18

●MXmx.yandex.net2026-03-05 → 2026-08-07 · 3 obs

○ 2017-05-15 17:09:50
● 2026-03-05 19:07:10
● 2026-08-07 03:22:18

○A104.18.48.502017-05-15 → 2017-05-15 · 4 obs

○ 2016-06-18 02:23:38
● 2017-05-15 17:09:50
○ 2026-03-05 19:07:10
○ 2026-08-07 03:22:18

○A104.18.49.502017-05-15 → 2017-05-15 · 4 obs

○ 2016-06-18 02:23:38
● 2017-05-15 17:09:50
○ 2026-03-05 19:07:10
○ 2026-08-07 03:22:18

○A185.197.160.322026-03-05 → 2026-03-05 · 4 obs

○ 2017-05-15 17:09:50
● 2026-03-05 19:07:10
○ 2026-03-09 15:20:08
○ 2026-08-07 03:22:18

○A185.31.210.472015-07-08 → 2016-06-18 · 4 obs

● 2015-07-08 09:50:28
● 2016-06-18 02:23:38
○ 2017-05-15 17:09:50
○ 2026-08-07 03:22:18

○A2400:cb00:2048:1::6812:30322017-05-15 → 2017-05-15 · 4 obs

○ 2016-06-18 02:23:38
● 2017-05-15 17:09:50
○ 2026-03-05 19:07:10
○ 2026-08-07 03:22:18

○A2400:cb00:2048:1::6812:31322017-05-15 → 2017-05-15 · 4 obs

○ 2016-06-18 02:23:38
● 2017-05-15 17:09:50
○ 2026-03-05 19:07:10
○ 2026-08-07 03:22:18

●A2a0b:6903:fdb:c425:c:e628:fd27:44782026-03-09 → 2026-08-07 · 3 obs

○ 2026-03-05 19:07:10
● 2026-03-09 15:20:08
● 2026-08-07 03:22:18

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	e.gtld-servers.net, l.gtld-servers.net, g.gtld-servers.net, h.gtld-servers.net...	-
wmidbot.com	dns1.yandex.net, dns2.yandex.net	-

✅ Authoritative Response

Server:93.158.134.213

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

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for wmidbot.com (unsigned zone)

⏱️ Timing

Total: 859ms | Queries: -

📄 Records

Type	Count	Sample Data
AAAA	1	`2a0b:6903:fdb:c425:c:e628:fd27:4478`
NS	2	`dns1.yandex.net, dns2.yandex.net`
MX	1	`mx.yandex.net (pri: 10)`
TXT	1	`v=spf1 redirect=_spf.yandex.net`
SOA	1	`dns1.yandex.net dns-hosting.yandex.ru`

Analysis

IP Addresses

wmidbot.com resolves to one IP address: 2a0b:6903:fdb:c425:c:e628:fd27:4478.

Name Servers

wmidbot.com is served by two delegated name servers, dns1.yandex.net and dns2.yandex.net.

wmidbot.com uses the same name servers as several other domains — among them svetmariya.ru, fondres.ru, mrmasly.com and two more.

The name servers of wmidbot.com overlap at least partially with those of other domains — among them money-man.ru, xn--j1afix.xn--p1ai, atom.ru and two more.

These name servers commonly appear alongside the name servers dns1.yandex.ru and dns2.yandex.ru.

Each of the two host names carries two IP addresses: dns1.yandex.net points to 213.180.204.213 and 2a02:6b8::213, and dns2.yandex.net points to 93.158.134.213 and 2a02:6b8:0:1::213.

Mail Servers

Mail for wmidbot.com is handled by a single mail server, mx.yandex.net.

wmidbot.com uses an identical mail server configuration to several other domains — among them canek.ru, novaperde.com, gataairlines.com and two more.

There is at least a partial overlap in mail servers between wmidbot.com and other domains like akb-market.ru, krasnovandrey.ru and naviline.org.

mx.yandex.net resolves to two IP numbers — 77.88.21.249 and 2a02:6b8::311.