`jali-group.com`

DNSSEC	⚠️ Not signed
A	209.42.22.62^{🇬🇧 WHG-LON209.42.22.0/24}
		PTR	`s2997.lon1.stableserver.net`
NS	`ns1.mysecurecloudhost.com` ⭐ ⚠️ Not in parent delegation
		A	13.248.158.180^{🇺🇸 Amazon13.248.144.0/20}
			PTR	`a79764cc55c0ac9c0.awsglobalaccelerator.com`
NS	`ns1.spiderbithosting.com` ⚠️ Not in zone NS records
		A	13.248.158.180^{🇺🇸 Amazon13.248.144.0/20}
			PTR	`a79764cc55c0ac9c0.awsglobalaccelerator.com`
NS	`ns2.mysecurecloudhost.com` ⚠️ Not in parent delegation
		A	75.2.118.134^{🇺🇸 Amazon75.2.112.0/20}
			PTR	`abc65dd9a44b5332f.awsglobalaccelerator.com`
NS	`ns2.spiderbithosting.com` ⚠️ Not in zone NS records
		A	75.2.118.134^{🇺🇸 Amazon75.2.112.0/20}
			PTR	`abc65dd9a44b5332f.awsglobalaccelerator.com`
NS	`ns3.mysecurecloudhost.com` ⚠️ Not in parent delegation
		A	76.223.26.245^{🇺🇸 Amazon76.223.16.0/20}
			PTR	`a79764cc55c0ac9c0.awsglobalaccelerator.com`
NS	`ns4.mysecurecloudhost.com` ⚠️ Not in parent delegation
		A	99.83.147.209^{🇺🇸 Amazon99.83.144.0/20}
			PTR	`abc65dd9a44b5332f.awsglobalaccelerator.com`
MX	`jali-group.com` ⭐
		A	209.42.22.62^{🇬🇧 WHG-LON209.42.22.0/24}
			PTR	`s2997.lon1.stableserver.net`
TXT	`v=spf1 +a +mx +ip4:209.42.22.62 include:spf.mysecurecloudhost.com +ip4:192.25...`
SOA	`ns1.mysecurecloudhost.com`servers@mysecurecloudhost.com 2026-07-07 #0

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

MX for

jali-group.com

Same first word

jali-group.com

DNS History

11 records (8 active, 3 former)

○NSns1.adicthost.net2019-01-26 → 2019-01-26 · 3 obs

● 2019-01-26 10:50:10
○ 2026-03-06 13:56:52
○ 2026-07-07 21:15:50

●NSns1.mysecurecloudhost.com2026-03-06 → 2026-07-07 · 3 obs

○ 2019-01-26 10:50:10
● 2026-03-06 13:56:52
● 2026-07-07 21:15:50

●NSns1.spiderbithosting.com2026-03-06 → 2026-07-07 · 3 obs

○ 2019-01-26 10:50:10
● 2026-03-06 13:56:52
● 2026-07-07 21:15:50

○NSns2.adicthost.net2019-01-26 → 2019-01-26 · 3 obs

● 2019-01-26 10:50:10
○ 2026-03-06 13:56:52
○ 2026-07-07 21:15:50

●NSns2.mysecurecloudhost.com2026-03-06 → 2026-07-07 · 3 obs

○ 2019-01-26 10:50:10
● 2026-03-06 13:56:52
● 2026-07-07 21:15:50

●NSns2.spiderbithosting.com2026-03-06 → 2026-07-07 · 3 obs

○ 2019-01-26 10:50:10
● 2026-03-06 13:56:52
● 2026-07-07 21:15:50

●NSns3.mysecurecloudhost.com2026-03-06 → 2026-07-07 · 3 obs

○ 2019-01-26 10:50:10
● 2026-03-06 13:56:52
● 2026-07-07 21:15:50

●NSns4.mysecurecloudhost.com2026-03-06 → 2026-07-07 · 3 obs

○ 2019-01-26 10:50:10
● 2026-03-06 13:56:52
● 2026-07-07 21:15:50

●MXjali-group.com2019-01-26 → 2026-07-07 · 2 obs

● 2019-01-26 10:50:10
● 2026-07-07 21:15:50

●A209.42.22.622026-03-06 → 2026-07-07 · 3 obs

○ 2019-01-26 10:50:10
● 2026-03-06 13:56:52
● 2026-07-07 21:15:50

○A212.1.210.502019-01-26 → 2019-01-26 · 3 obs

● 2019-01-26 10:50:10
○ 2026-03-06 13:56:52
○ 2026-07-07 21:15:50

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	a.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net...	-
jali-group.com	ns1.spiderbithosting.com, ns2.spiderbithosting.com	2 records

✅ Authoritative Response

Server:75.2.118.134

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

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for jali-group.com (unsigned zone)

⏱️ Timing

Total: 102ms | Queries: -

📄 Records

Type	Count	Sample Data
A	1	`209.42.22.62`
NS	4	`ns4.mysecurecloudhost.com, ns3.mysecurecloudhost.com...`
MX	1	`jali-group.com (pri: 0)`
TXT	1	`v=spf1 +a +mx +ip4:209.42.22.62 include:`
SOA	1	`ns1.mysecurecloudhost.com servers.mysecu`

📌 Glue Records Collected

Total: 2

Out-of-bailiwick: 2 (ns1.spiderbithosting.com, ns2.spiderbithosting.com)

Analysis

Mail Server Role

jali-group.com is listed as a mail server for itself.

IP Addresses

jali-group.com resolves to one IP address: 209.42.22.62.

glyndalekennelsandcattery.co.uk, kundubuzima.rw, fablab.rw and two other host names share IP numbers with jali-group.com.

Name Servers

The DNS delegation for jali-group.com covers 6 name servers: ns1.mysecurecloudhost.com, ns2.mysecurecloudhost.com, ns3.mysecurecloudhost.com and 3 more.

jali-group.com shares at least some of its name servers with other domains, including qxt.pl, larkslearning.com, globaltruckimports.com.au and two others.

These name servers are frequently paired with the name servers ns4.mysecurecloudhost.com, ns1.spiderbithosting.com and ns2.spiderbithosting.com.

Hosts with just one IP address:

ns1.mysecurecloudhost.com points to the IP address 13.248.158.180.

ns2.mysecurecloudhost.com points to the IP address 75.2.118.134.

ns3.mysecurecloudhost.com points to the IP address 76.223.26.245.

ns4.mysecurecloudhost.com points to the IP address 99.83.147.209.

ns1.spiderbithosting.com points to the IP address 13.248.158.180.

ns2.spiderbithosting.com points to the IP address 75.2.118.134.

These two host names — ns1.mysecurecloudhost.com and ns1.spiderbithosting.com — each point to 13.248.158.180 IP addresses.

These two host names — ns2.mysecurecloudhost.com and ns2.spiderbithosting.com — each point to 75.2.118.134 IP addresses.