`liberty39.com`

DNSSEC	⚠️ Not signed
NS	`dns1.yandex.net` ⚠️ Not in zone NS records
		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` ⚠️ Not in zone NS records
		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`
NS	`ns1.hosthp.net` ⚠️ Not in zone NS records
		A	109.94.209.174^{🇪🇪 ARVID-LOGICUM109.94.209.0/24}
			PTR	`liberty.web-host.gen.in`
NS	`ns2.hosthp.net` ⚠️ Not in zone NS records
		A	109.94.209.191^{🇪🇪 ARVID-LOGICUM109.94.209.0/24}
			PTR	`free.zbs.cloud`
TXT	`v=spf1 redirect=_spf.yandex.net`
TXT	`wmail-verification: 8be5b631d30935798f28a56689ccce1e`
TXT	`_globalsign-domain-verification=psMmFJuYWGwxvmLrgGDL-MnpbQlUUx8OSaSHPW8R75`

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

Same first word

liberty39.com

DNS History

8 records (4 active, 4 former)

●NSdns1.yandex.net2016-07-26 → 2026-03-27 · 2 obs

● 2016-07-26 04:57:18
● 2026-03-27 19:53:16

●NSdns2.yandex.net2016-07-26 → 2026-03-27 · 2 obs

● 2016-07-26 04:57:18
● 2026-03-27 19:53:16

●NSns1.hosthp.net2026-02-22 → 2026-03-27 · 3 obs

○ 2016-07-26 04:57:18
● 2026-02-22 05:05:42
● 2026-03-27 19:53:16

●NSns2.hosthp.net2026-02-22 → 2026-03-27 · 3 obs

○ 2016-07-26 04:57:18
● 2026-02-22 05:05:42
● 2026-03-27 19:53:16

○MXmx.yandex.net2016-07-26 → 2026-03-08 · 6 obs

● 2016-07-26 04:57:18
● 2017-04-10 17:54:56
○ 2026-02-22 05:05:42
● 2026-02-28 21:42:14
● 2026-03-08 09:10:58
○ 2026-03-27 19:53:16

○A109.94.209.532026-02-22 → 2026-03-08 · 4 obs

○ 2017-04-10 17:54:56
● 2026-02-22 05:05:42
● 2026-03-08 09:10:58
○ 2026-03-27 19:53:16

○A141.101.128.1142016-07-26 → 2016-07-26 · 3 obs

● 2016-07-26 04:57:18
○ 2017-04-10 17:54:56
○ 2026-03-27 19:53:16

○A141.101.128.1212017-04-10 → 2017-04-10 · 4 obs

○ 2016-07-26 04:57:18
● 2017-04-10 17:54:56
○ 2026-02-22 05:05:42
○ 2026-03-27 19:53:16

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	h.gtld-servers.net, b.gtld-servers.net, l.gtld-servers.net, f.gtld-servers.net...	-
liberty39.com	dns1.yandex.net, dns2.yandex.net, ns1.hosthp.net, ns2.hosthp.net	-

✅ Authoritative Response

Server:109.94.209.174

NS records: dns1.yandex.net, dns2.yandex.net, ns1.hosthp.net, ns2.hosthp.net

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for liberty39.com (unsigned zone)

⏱️ Timing

Total: 1644ms | Queries: -

📄 Records

Type	Count	Sample Data
A	1	`109.94.209.53`
NS	2	`dns1.yandex.net, dns2.yandex.net`
MX	1	`mx.yandex.net (pri: 10)`
TXT	3	`v=spf1 redirect=_spf.yandex.net, wmail-verification: 8be5b631d30935798f28...`

Analysis

Name Servers

liberty39.com is delegated to four name servers: ns1.hosthp.net, ns2.hosthp.net, dns1.yandex.net and dns2.yandex.net.

liberty39.com at least partially shares name servers with other domains, for instance ildan.ru, magusa.org, kranzle.ru, applite.ru and semkarev.ru.

These name servers are commonly used with the following name servers: ns1.web-host.gen.in, ns2.web-host.gen.in, ns1.host27.info, ns2.host27.info, ns1.binar777.net, ns2.binar777.net, ns1.server-dns.net.in, ns2.server-dns.net.in, dns1.yandex.ru and dns2.yandex.ru.

Host names with two IP numbers:

dns1.yandex.net points to 2a02:6b8::213 and 213.180.204.213; dns2.yandex.net points to 2a02:6b8:0:1::213 and 93.158.134.213.

Host names with one IP number:

ns1.hosthp.net points to 109.94.209.174; ns2.hosthp.net points to 109.94.209.191.

liberty39.com - robtex.com

liberty39.com

com