`djsandfestivals.com`

DNSSEC	⚠️ Not signed
A	34.92.78.117^{🇭🇰 Google34.92.0.0/16}
		PTR	`117.78.92.34.bc.googleusercontent.com`
NS	`ns1.dnsip.com` ⭐
		A	2001:df2:f080:1::10^{🇭🇰 HKCICL-AS-AP2001:df2:f080::/48 HONG KONG COMMUNICATIONS INTERNATIONAL CO.,LIMITED}
		A	1.193.216.199^{🇨🇳 CHINANET-Henan-Luoyang-IDC1.193.216.0/24 Chinatelecom HeNan Province Network}
		A	218.98.111.202^{🇩🇪 HKCICL-AS-AP218.98.111.0/24 HONG KONG COMMUNICATIONS INTERNATIONAL CO.,LIMITED}
		A	218.98.111.206^{🇩🇪 HKCICL-AS-AP218.98.111.0/24 HONG KONG COMMUNICATIONS INTERNATIONAL CO.,LIMITED}
NS	`ns2.dnsip.com`
		A	240e:97d:10:1402:0:1:0:1008^{🇨🇳 CHINANET-Guangdong-DongGuan-IDC240e:97d::/36 DongGuan IDC Network}
		A	61.158.128.1^{🇨🇳 CHINA169-Backbone61.158.128.0/17 CNC Group CHINA169 Henan Province Network}
			PTR	`1.128.158.61.ha.cnc`
		A	183.253.57.193^{🇨🇳 CHINAMOBILE-CN183.253.0.0/16 CMI (Customer Route)}
		A	211.99.99.29^{🇨🇳 DONGGUAN-1211.99.99.0/24 Proxy-registered route object}
		A	211.99.99.33^{🇨🇳 DONGGUAN-1211.99.99.0/24 Proxy-registered route object}
SOA	`ns1.dnsip.com`dnsadmin@dnsip.com serial=1760237333

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

⚠️ On DNS blocklist: tif

Same first word

djsandfestivals.com

DNS History

20 records (3 active, 17 former)

○NSauth01.dns.trueserver.nl2017-06-24 → 2017-06-24 · 4 obs

○ 2016-12-17 03:48:36
● 2017-06-24 11:43:32
○ 2026-03-06 01:44:38
○ 2026-03-23 21:13:18

○NSauth02.dns.trueserver.nl2017-06-24 → 2017-06-24 · 4 obs

○ 2016-12-17 03:48:36
● 2017-06-24 11:43:32
○ 2026-03-06 01:44:38
○ 2026-03-23 21:13:18

○NSauth03.dns.trueserver.nl2017-06-24 → 2017-06-24 · 4 obs

○ 2016-12-17 03:48:36
● 2017-06-24 11:43:32
○ 2026-03-06 01:44:38
○ 2026-03-23 21:13:18

○NSns1.cloudvps.com2016-12-17 → 2016-12-17 · 3 obs

● 2016-12-17 03:48:36
○ 2017-06-24 11:43:32
○ 2026-03-23 21:13:18

●NSns1.dnsip.com2026-03-06 → 2026-03-23 · 3 obs

○ 2017-06-24 11:43:32
● 2026-03-06 01:44:38
● 2026-03-23 21:13:18

○NSns2.cloudvps.com2016-12-17 → 2016-12-17 · 3 obs

● 2016-12-17 03:48:36
○ 2017-06-24 11:43:32
○ 2026-03-23 21:13:18

●NSns2.dnsip.com2026-03-06 → 2026-03-23 · 3 obs

○ 2017-06-24 11:43:32
● 2026-03-06 01:44:38
● 2026-03-23 21:13:18

○NSns3.cloudvps.com2016-12-17 → 2016-12-17 · 3 obs

● 2016-12-17 03:48:36
○ 2017-06-24 11:43:32
○ 2026-03-23 21:13:18

○MXalt1.aspmx.l.google.com2016-12-17 → 2017-06-24 · 4 obs

● 2016-12-17 03:48:36
● 2017-06-24 11:43:32
○ 2026-03-06 01:44:38
○ 2026-03-23 21:13:18

○MXalt2.aspmx.l.google.com2016-12-17 → 2017-06-24 · 4 obs

● 2016-12-17 03:48:36
● 2017-06-24 11:43:32
○ 2026-03-06 01:44:38
○ 2026-03-23 21:13:18

○MXalt3.aspmx.l.google.com2017-06-24 → 2017-06-24 · 4 obs

○ 2016-12-17 03:48:36
● 2017-06-24 11:43:32
○ 2026-03-06 01:44:38
○ 2026-03-23 21:13:18

○MXalt4.aspmx.l.google.com2017-06-24 → 2017-06-24 · 4 obs

○ 2016-12-17 03:48:36
● 2017-06-24 11:43:32
○ 2026-03-06 01:44:38
○ 2026-03-23 21:13:18

○MXaspmx.l.google.com2016-12-17 → 2017-06-24 · 4 obs

● 2016-12-17 03:48:36
● 2017-06-24 11:43:32
○ 2026-03-06 01:44:38
○ 2026-03-23 21:13:18

○MXaspmx2.googlemail.com2016-12-17 → 2016-12-17 · 3 obs

● 2016-12-17 03:48:36
○ 2017-06-24 11:43:32
○ 2026-03-23 21:13:18

○MXaspmx3.googlemail.com2016-12-17 → 2016-12-17 · 3 obs

● 2016-12-17 03:48:36
○ 2017-06-24 11:43:32
○ 2026-03-23 21:13:18

○MXaspmx4.googlemail.com2016-12-17 → 2016-12-17 · 3 obs

● 2016-12-17 03:48:36
○ 2017-06-24 11:43:32
○ 2026-03-23 21:13:18

○MXaspmx5.googlemail.com2016-12-17 → 2016-12-17 · 3 obs

● 2016-12-17 03:48:36
○ 2017-06-24 11:43:32
○ 2026-03-23 21:13:18

○A185.21.191.592016-12-17 → 2016-12-17 · 3 obs

● 2016-12-17 03:48:36
○ 2017-06-24 11:43:32
○ 2026-03-23 21:13:18

●A34.92.78.1172026-03-06 → 2026-03-23 · 3 obs

○ 2017-06-24 11:43:32
● 2026-03-06 01:44:38
● 2026-03-23 21:13:18

○A87.233.153.1942017-06-24 → 2017-06-24 · 4 obs

○ 2016-12-17 03:48:36
● 2017-06-24 11:43:32
○ 2026-03-06 01:44:38
○ 2026-03-23 21:13:18

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	l.gtld-servers.net, j.gtld-servers.net, h.gtld-servers.net, d.gtld-servers.net...	-
djsandfestivals.com	ns1.dnsip.com, ns2.dnsip.com	9 records

✅ Authoritative Response

Server:1.193.216.199

NS records: ns1.dnsip.com, ns2.dnsip.com

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for djsandfestivals.com (unsigned zone)

⏱️ Timing

Total: 1386ms | Queries: -

📄 Records

Type	Count	Sample Data
A	1	`34.92.78.117`
NS	2	`ns1.dnsip.com, ns2.dnsip.com`
SOA	1	`ns1.dnsip.com dnsadmin.dnsip.com`

📌 Glue Records Collected

Total: 9

Out-of-bailiwick: 9 (ns1.dnsip.com, ns1.dnsip.com, ns1.dnsip.com...)

Analysis

IP Addresses

djsandfestivals.com points to IP number 34.92.78.117.

For instance, other host names bali-perfect.com, ailsinisa.com, healthiermillie.com, 117.78.92.34.bc.googleusercontent.com and orlandostuccorepaircontractors.com share IP numbers with djsandfestivals.com.

Name Servers

djsandfestivals.com is delegated to two name servers: ns1.dnsip.com and ns2.dnsip.com.

djsandfestivals.com uses the same name server setup as other domains such as gszxjxsb.com, 84640.cn, 34346v.com, 171845.com and quanko.com.

djsandfestivals.com shares name servers with other domains at least partially, for example izmr.cn.

Five IP numbers for ns2.dnsip.com: ns2.dnsip.com points to 240e:97d:10:1402:0:1:0:1008, 61.158.128.1, 183.253.57.193, 211.99.99.29 and 211.99.99.33.

Four IP numbers for ns1.dnsip.com: ns1.dnsip.com points to 2001:df2:f080:1::10, 1.193.216.199, 218.98.111.202 and 218.98.111.206.

djsandfestivals.com - robtex.com