`labmedbot.ru`

DNSSEC	⚠️ Not signed
A	2606:4700:3031::ac43:c2d4^{🇺🇸 Cloudflare2606:4700:3031::/48 , Inc. 101 Townsend Street, San Francisco, California 94107, US} ✓ In HTTPS hints
A	2606:4700:3034::6815:2487^{🇺🇸 Cloudflare2606:4700:3034::/48 , Inc. 101 Townsend Street, San Francisco, California 94107, US} ✓ In HTTPS hints
A	104.21.36.135^{Cloudflare104.21.32.0/20 , Inc. 101 Townsend Street, San Francisco, California 94107, US} ✓ In HTTPS hints
A	172.67.194.212^{🇺🇸 Cloudflare172.67.192.0/20 , Inc. 101 Townsend Street, San Francisco, California 94107, US} ✓ In HTTPS hints
NS	`chan.ns.cloudflare.com` ⭐
		A	2606:4700:50::adf5:3a52^{🇺🇸 Cloudflare2606:4700:50::/44 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`chan.ns.cloudflare.com`
		A	2803:f800:50::6ca2:c052^{🇨🇷 Cloudflare2803:f800:50::/45 LACNIC generated route6 for CloudFlare Latin America S.R.L}
			PTR	`chan.ns.cloudflare.com`
		A	2a06:98c1:50::ac40:2052^{🇺🇸 Cloudflare2a06:98c1:50::/45}
			PTR	`chan.ns.cloudflare.com`
		A	108.162.192.82^{🇺🇸 Cloudflare108.162.192.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`chan.ns.cloudflare.com`
		A	172.64.32.82^{🇺🇸 Cloudflare172.64.32.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`chan.ns.cloudflare.com`
		A	173.245.58.82^{🇺🇸 Cloudflare173.245.58.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`chan.ns.cloudflare.com`
NS	`tom.ns.cloudflare.com`
		A	2606:4700:58::adf5:3b93^{🇺🇸 Cloudflare2606:4700:50::/44 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`tom.ns.cloudflare.com`
		A	2803:f800:50::6ca2:c193^{🇨🇷 Cloudflare2803:f800:50::/45 LACNIC generated route6 for CloudFlare Latin America S.R.L}
			PTR	`tom.ns.cloudflare.com`
		A	2a06:98c1:50::ac40:2193^{🇺🇸 Cloudflare2a06:98c1:50::/45}
			PTR	`tom.ns.cloudflare.com`
		A	108.162.193.147^{🇺🇸 Cloudflare108.162.193.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`tom.ns.cloudflare.com`
		A	172.64.33.147^{🇺🇸 Cloudflare172.64.33.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`tom.ns.cloudflare.com`
		A	173.245.59.147^{🇺🇸 Cloudflare173.245.59.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`tom.ns.cloudflare.com`
MX	`route1.mx.cloudflare.net` ⭐
		A	2606:4700:f5::b^{🇺🇸 Cloudflare2606:4700:f5::/48 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`route1.mx.cloudflare.net`
		A	2606:4700:f5::c^{🇺🇸 Cloudflare2606:4700:f5::/48 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`route1.mx.cloudflare.net`
		A	2606:4700:f5::d^{🇺🇸 Cloudflare2606:4700:f5::/48 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`route1.mx.cloudflare.net`
		A	162.159.205.11^{Cloudflare162.159.205.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`route1.mx.cloudflare.net`
		A	162.159.205.12^{Cloudflare162.159.205.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`route1.mx.cloudflare.net`
		A	162.159.205.13^{Cloudflare162.159.205.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`route1.mx.cloudflare.net`
MX	`route2.mx.cloudflare.net`⁽⁷⁶⁾
		A	2606:4700:f5::e^{🇺🇸 Cloudflare2606:4700:f5::/48 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`route2.mx.cloudflare.net`
		A	2606:4700:f5::f^{🇺🇸 Cloudflare2606:4700:f5::/48 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`route2.mx.cloudflare.net`
		A	2606:4700:f5::10^{🇺🇸 Cloudflare2606:4700:f5::/48 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`route2.mx.cloudflare.net`
		A	162.159.205.17^{Cloudflare162.159.205.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`route2.mx.cloudflare.net`
		A	162.159.205.18^{Cloudflare162.159.205.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`route2.mx.cloudflare.net`
		A	162.159.205.19^{Cloudflare162.159.205.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`route2.mx.cloudflare.net`
MX	`route3.mx.cloudflare.net`⁽⁹⁹⁾
		A	2606:4700:f5::11^{🇺🇸 Cloudflare2606:4700:f5::/48 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`route3.mx.cloudflare.net`
		A	2606:4700:f5::12^{🇺🇸 Cloudflare2606:4700:f5::/48 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`route3.mx.cloudflare.net`
		A	2606:4700:f5::13^{🇺🇸 Cloudflare2606:4700:f5::/48 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`route3.mx.cloudflare.net`
		A	162.159.205.23^{Cloudflare162.159.205.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`route3.mx.cloudflare.net`
		A	162.159.205.24^{Cloudflare162.159.205.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`route3.mx.cloudflare.net`
		A	162.159.205.25^{Cloudflare162.159.205.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`route3.mx.cloudflare.net`
TXT	`v=spf1 include:_spf.mx.cloudflare.net ~all`
HTTPS	HTTP/3, HTTP/2 ✓ hints match
		IPv4 hints	104.21.36.135, 172.67.194.212
		IPv6 hints	2606:4700:3031::ac43:c2d4, 2606:4700:3034::6815:2487
		ECH	X25519, HKDF-SHA256 + AES-128-GCM draft, id=68, name=cloudflare-ech.com
SOA	`chan.ns.cloudflare.com`dns@cloudflare.com serial=2411787211

`ru`

	DNSSEC	🔒 Signed (DS record present)
	NS	`a.dns.ripn.net` ⭐
	NS	`b.dns.ripn.net`
	NS	`c.tld-servers.ru`
	NS	`d.dns.ripn.net`
	NS	`e.dns.ripn.net`
	NS	`f.dns.ripn.net`
	SOA	`a.dns.ripn.net`hostmaster@ripn.net serial=4069962

Same first word

labmedbot.ru

DNS History

13 records (9 active, 4 former)

●NSchan.ns.cloudflare.com2026-06-22 → 2026-08-12 · 2 obs

● 2026-06-22 22:34:24
● 2026-08-12 17:51:58

●NStom.ns.cloudflare.com2026-06-22 → 2026-08-12 · 2 obs

● 2026-06-22 22:34:24
● 2026-08-12 17:51:58

●MXroute1.mx.cloudflare.net2026-06-22 → 2026-08-12 · 2 obs

● 2026-06-22 22:34:24
● 2026-08-12 17:51:58

●MXroute2.mx.cloudflare.net2026-06-22 → 2026-08-12 · 2 obs

● 2026-06-22 22:34:24
● 2026-08-12 17:51:58

●MXroute3.mx.cloudflare.net2026-06-22 → 2026-08-12 · 2 obs

● 2026-06-22 22:34:24
● 2026-08-12 17:51:58

●A104.21.36.1352026-08-12 → 2026-08-12 · 2 obs

○ 2026-06-22 22:34:24
● 2026-08-12 17:51:58

●A172.67.194.2122026-08-12 → 2026-08-12 · 2 obs

○ 2026-06-22 22:34:24
● 2026-08-12 17:51:58

○A188.114.96.02026-06-22 → 2026-06-22 · 2 obs

● 2026-06-22 22:34:24
○ 2026-08-12 17:51:58

○A188.114.97.02026-06-22 → 2026-06-22 · 2 obs

● 2026-06-22 22:34:24
○ 2026-08-12 17:51:58

●A2606:4700:3031::ac43:c2d42026-08-12 → 2026-08-12 · 2 obs

○ 2026-06-22 22:34:24
● 2026-08-12 17:51:58

●A2606:4700:3034::6815:24872026-08-12 → 2026-08-12 · 2 obs

○ 2026-06-22 22:34:24
● 2026-08-12 17:51:58

○A2a06:98c1:3120::2026-06-22 → 2026-06-22 · 2 obs

● 2026-06-22 22:34:24
○ 2026-08-12 17:51:58

○A2a06:98c1:3121::2026-06-22 → 2026-06-22 · 2 obs

● 2026-06-22 22:34:24
○ 2026-08-12 17:51:58

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
ru	a.dns.ripn.net, b.dns.ripn.net, c.tld-servers.ru, d.dns.ripn.net...	-
labmedbot.ru	chan.ns.cloudflare.com, tom.ns.cloudflare.com	-

✅ Authoritative Response

Server:172.64.33.147

NS records: chan.ns.cloudflare.com, tom.ns.cloudflare.com

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for labmedbot.ru (unsigned zone)

⏱️ Timing

Total: 984ms | Queries: -

📄 Records

Type	Count	Sample Data
A	2	`172.67.194.212, 104.21.36.135`
AAAA	2	`2606:4700:3031::ac43:c2d4, 2606:4700:3034::6815:2487`
NS	2	`chan.ns.cloudflare.com, tom.ns.cloudflare.com`
MX	3	`route1.mx.cloudflare.net (pri: 34), route2.mx.cloudflare.net (pri: 76)...`
TXT	1	`v=spf1 include:_spf.mx.cloudflare.net ~a`
HTTPS	1	`{"priority":1,"target":".","alpn":["h3",`
SOA	1	`chan.ns.cloudflare.com dns.cloudflare.co`

Analysis

IP Addresses

labmedbot.ru has four IP addresses: 104.21.36.135, 172.67.194.212, 2606:4700:3031::ac43:c2d4 and 2606:4700:3034::6815:2487.

Among the host names that share IP numbers with labmedbot.ru are china-jiurun.com, arabic-nvda.org, labohemeresale.com and two others.

Name Servers

labmedbot.ru uses two name servers for its delegation: chan.ns.cloudflare.com and tom.ns.cloudflare.com.

labmedbot.ru has the same name server delegation as a number of other domains, such as dogking.es, gbtango.it, gakdo.com and two more.

labmedbot.ru has at least partial name server overlap with other domains, such as misadaptlayer.digital, inmosystem.com, juara77.com and two others.

These name servers are routinely co-deployed with the name servers kia.ns.cloudflare.com, merlin.ns.cloudflare.com, theo.ns.cloudflare.com and two others.

Host names resolving to 6 IP numbers:

Hostname chan.ns.cloudflare.com directs to 108.162.192.82, 172.64.32.82 and 173.245.58.82 along with 3 other IP addresses.

Hostname tom.ns.cloudflare.com directs to 108.162.193.147, 172.64.33.147 and 173.245.59.147 along with 3 other IP addresses.

Mail Servers

labmedbot.ru has three mail servers: route1.mx.cloudflare.net, route2.mx.cloudflare.net and route3.mx.cloudflare.net.

labmedbot.ru shares at least some of its mail servers with other domains — for example smail.club, anarkalika.com, gaozm.com and two more.

Host names resolving to 6 IP numbers:

Hostname route1.mx.cloudflare.net directs to 162.159.205.11, 162.159.205.12 and 162.159.205.13 along with 3 other IP addresses.

Hostname route2.mx.cloudflare.net directs to 162.159.205.17, 162.159.205.18 and 162.159.205.19 along with 3 other IP addresses.

Hostname route3.mx.cloudflare.net directs to 162.159.205.23, 162.159.205.24 and 162.159.205.25 along with 3 other IP addresses.

labmedbot.ru - robtex.com

labmedbot.ru

ru

Same first word

DNS History

🔍 DNS Trace

📋 Delegation Chain

✅ Authoritative Response

🔒 DNSSEC Status

⏱️ Timing

📄 Records

Analysis

IP Addresses

Name Servers

Mail Servers

`labmedbot.ru`

`ru`