callbackhunter.com - dns.ninja

`callbackhunter.com`

DNSSEC	⚠️ Not signed
A	178.209.118.101^{🇷🇺 WESTCALL-AS178.209.96.0/19 WestCall Ltd}
NS	`ns41.cloudns.net` ⭐
		A	2a00:1768:1001:9::196^{🇳🇱 NFORCE2a00:1768:1001:9::/64}
			PTR	`ns41.cloudns.net`
		A	109.201.133.196^{🇳🇱 NFORCE109.201.128.0/19 NFOrce Entertainment BV - 109.201.128.0/19 route}
			PTR	`ns41.cloudns.net`
NS	`ns42.cloudns.net`
		A	2604:9a00:2100:b000:1::1^{🇺🇸 LEASEWEB-US2604:9a00::/32 Leaseweb USA, Inc. US}
			PTR	`ns42.cloudns.net`
		A	108.62.121.219^{🇺🇸 LEASEWEB-US108.62.120.0/22 Leaseweb USA, Inc.}
			PTR	`ns42.cloudns.net`
NS	`ns43.cloudns.net`
		A	2a07:8dc0:19:0:5d:37ff:fea5:bacd^{🇫🇷 VIRTUASYS-EU2a07:8dc0::/32 PAR01.FR.VIRTUA.SYSTEMS}
		A	185.10.17.44^{🇫🇷 VIRTUASYS-EU185.10.17.0/24 PAR01.FR.VIRTUA.SYSTEMS}
NS	`ns44.cloudns.net`
		A	2a0b:1640:1:1:1:1:762:9aa6^{🇧🇬 Publicloud2a0b:1640:1::/48 PubliCloud}
			PTR	`ns44.cloudns.net`
		A	185.206.180.140^{🇩🇪 Publicloud185.206.180.0/24 PubliCloud}
			PTR	`ns44.cloudns.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	`_globalsign-domain-verification=xSHl_BgH7s0BNaTiGzmla4GNktfCULs2SuKTXq5vEl`
SOA	`ns41.cloudns.net`admin@callbackhunter.com 2025-08-28 #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=1784254522

⚠️ On DNS blocklist: ultimate
WOT: SAFE (79/100)
📈 Tranco rank: #390,579

Subdomains

app.callbackhunter.com

Same first word

callbackhunter.com

DNS History

14 records (6 active, 8 former)

○NSdns1.yandex.net2015-06-11 → 2017-06-12 · 7 obs

● 2015-06-11 22:27:42
● 2016-02-02 11:18:02
○ 2016-04-22 10:20:46
○ 2016-07-04 18:15:30
● 2017-06-12 19:28:06
○ 2026-02-16 23:49:50
○ 2026-07-17 02:21:22

○NSdns2.yandex.net2015-06-11 → 2017-06-12 · 7 obs

● 2015-06-11 22:27:42
● 2016-02-02 11:18:02
○ 2016-04-22 10:20:46
○ 2016-07-04 18:15:30
● 2017-06-12 19:28:06
○ 2026-02-16 23:49:50
○ 2026-07-17 02:21:22

○NSns-1156.awsdns-16.org2016-04-22 → 2016-07-04 · 5 obs

○ 2016-02-02 11:18:02
● 2016-04-22 10:20:46
● 2016-07-04 18:15:30
○ 2017-06-12 19:28:06
○ 2026-07-17 02:21:22

○NSns-1621.awsdns-10.co.uk2016-04-22 → 2016-07-04 · 5 obs

○ 2016-02-02 11:18:02
● 2016-04-22 10:20:46
● 2016-07-04 18:15:30
○ 2017-06-12 19:28:06
○ 2026-07-17 02:21:22

○NSns-310.awsdns-38.com2016-04-22 → 2016-07-04 · 5 obs

○ 2016-02-02 11:18:02
● 2016-04-22 10:20:46
● 2016-07-04 18:15:30
○ 2017-06-12 19:28:06
○ 2026-07-17 02:21:22

○NSns-742.awsdns-28.net2016-04-22 → 2016-07-04 · 5 obs

○ 2016-02-02 11:18:02
● 2016-04-22 10:20:46
● 2016-07-04 18:15:30
○ 2017-06-12 19:28:06
○ 2026-07-17 02:21:22

●NSns41.cloudns.net2026-02-16 → 2026-07-17 · 3 obs

○ 2017-06-12 19:28:06
● 2026-02-16 23:49:50
● 2026-07-17 02:21:22

●NSns42.cloudns.net2026-02-16 → 2026-07-17 · 3 obs

○ 2017-06-12 19:28:06
● 2026-02-16 23:49:50
● 2026-07-17 02:21:22

●NSns43.cloudns.net2026-02-16 → 2026-07-17 · 3 obs

○ 2017-06-12 19:28:06
● 2026-02-16 23:49:50
● 2026-07-17 02:21:22

●NSns44.cloudns.net2026-02-16 → 2026-07-17 · 3 obs

○ 2017-06-12 19:28:06
● 2026-02-16 23:49:50
● 2026-07-17 02:21:22

●MXmx.yandex.net2015-06-11 → 2026-07-17 · 2 obs

● 2015-06-11 22:27:42
● 2026-07-17 02:21:22

●A178.209.118.1012026-02-16 → 2026-07-17 · 3 obs

○ 2017-06-12 19:28:06
● 2026-02-16 23:49:50
● 2026-07-17 02:21:22

○A78.46.116.952015-06-11 → 2016-04-22 · 4 obs

● 2015-06-11 22:27:42
● 2016-04-22 10:20:46
○ 2016-07-04 18:15:30
○ 2026-07-17 02:21:22

○A88.198.117.542016-07-04 → 2017-06-12 · 5 obs

○ 2016-04-22 10:20:46
● 2016-07-04 18:15:30
● 2017-06-12 19:28:06
○ 2026-02-16 23:49:50
○ 2026-07-17 02:21:22

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	l.gtld-servers.net, j.gtld-servers.net, h.gtld-servers.net, d.gtld-servers.net...	-
callbackhunter.com	ns44.cloudns.net, ns43.cloudns.net, ns41.cloudns.net, ns42.cloudns.net	-

✅ Authoritative Response

Server:109.201.133.196

NS records: ns44.cloudns.net, ns43.cloudns.net, ns41.cloudns.net, ns42.cloudns.net

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for callbackhunter.com (unsigned zone)

⏱️ Timing

Total: 981ms | Queries: -

📄 Records

Type	Count	Sample Data
A	1	`178.209.118.101`
NS	4	`ns41.cloudns.net, ns43.cloudns.net...`
MX	1	`mx.yandex.net (pri: 0)`
TXT	1	`_globalsign-domain-verification=xSHl_BgH`
SOA	1	`ns41.cloudns.net admin.callbackhunter.co`

Analysis

Hierarchy

The domain app.callbackhunter.com falls under the parent callbackhunter.com.

IP Addresses

callbackhunter.com resolves to just one IP address, 178.209.118.101.

Name Servers

The NS records for callbackhunter.com point to four name servers: ns41.cloudns.net, ns42.cloudns.net, ns43.cloudns.net and ns44.cloudns.net.

At least some of callbackhunter.com's name servers are shared with other domains, for example joywulkan24.com, artkela.ru, unuttum.net and two more.

These name servers are often deployed together with the name servers pns41.cloudns.net, pns43.cloudns.net, pns44.cloudns.net and pns42.cloudns.net.

Four hostnames, each resolving to a pair of IP addresses: ns41.cloudns.net directs to 109.201.133.196 and 2a00:1768:1001:9::196; ns42.cloudns.net directs to 108.62.121.219 and 2604:9a00:2100:b000:1::1; ns43.cloudns.net directs to 185.10.17.44 and 2a07:8dc0:19:0:5d:37ff:fea5:bacd; ns44.cloudns.net directs to 185.206.180.140 and 2a0b:1640:1:1:1:1:762:9aa6.

Mail Servers

The sole mail server for callbackhunter.com is mx.yandex.net.

Among the domains sharing a mail server setup with callbackhunter.com are yochting.com, grani.su, dvik.info and two others.

There is at least a partial MX overlap between callbackhunter.com and other domains, including extra-car.de, agroitalservice.ru, stovolt.ru and two others.

mx.yandex.net directs to two IP numbers, 77.88.21.249 and 2a02:6b8::311.