`hhqcalliance.com`

DNSSEC	⚠️ Not signed
A	101.99.77.36^{🇲🇾 SHINJIRU-MY-AS-AP101.99.77.0/24 Shinjiru Technology Sdn Bhd 19-2, Wisma Laxton, Jln Desa, Tmn Desa, Jln Klang Lama,}
		PTR	`server1.kamon.la`
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=11

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

Same first word

hhqcalliance.com

DNS History

4 records (4 active, 0 former)

●NSdns1.yandex.net2019-12-17 → 2026-08-05 · 2 obs

● 2019-12-17 00:18:12
● 2026-08-05 21:58:40

●NSdns2.yandex.net2019-12-17 → 2026-08-05 · 2 obs

● 2019-12-17 00:18:12
● 2026-08-05 21:58:40

●MXmx.yandex.net2019-12-17 → 2026-08-05 · 2 obs

● 2019-12-17 00:18:12
● 2026-08-05 21:58:40

●A101.99.77.362019-12-17 → 2026-08-05 · 2 obs

● 2019-12-17 00:18:12
● 2026-08-05 21:58:40

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	a.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net...	-
hhqcalliance.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 hhqcalliance.com (unsigned zone)

⏱️ Timing

Total: 761ms | Queries: -

📄 Records

Type	Count	Sample Data
A	1	`101.99.77.36`
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

hhqcalliance.com directs to one IP number, which is 101.99.77.36.

Other host names, such as mail.netpartners.com.my, share IP numbers with hhqcalliance.com.

Name Servers

hhqcalliance.com is delegated to two name servers: dns1.yandex.net and dns2.yandex.net.

hhqcalliance.com has the same name server delegation as a number of other domains, such as avtoimport-st.com, olimpas.com, viled.net and two more.

hhqcalliance.com shares at least some of its name servers with other domains, including maryutin.com, cctea.org.tw, invariant.biz and two others.

These name servers are frequently paired with the name servers dns1.yandex.ru and dns2.yandex.ru.

dns1.yandex.net and dns2.yandex.net each resolve to two IP addresses: dns1.yandex.net points to 213.180.204.213 and 2a02:6b8::213, while dns2.yandex.net points to 93.158.134.213 and 2a02:6b8:0:1::213.

Mail Servers

hhqcalliance.com routes its mail through a single mail server, mx.yandex.net.

hhqcalliance.com has the same mail server arrangement as a number of other domains, for example ivishot.ru, tuncmermer.com.tr, teh-rezina.ru and two more.

hhqcalliance.com shares at least some of its mail servers with other domains — for example elshop.ru, shenmatk.com, fitmost.ru and two more.

mx.yandex.net points to two IP addresses: 77.88.21.249 and 2a02:6b8::311.

hhqcalliance.com - robtex.com