`virtualanchors.com`

DNSSEC	⚠️ Not signed
A	144.76.136.166^{🇩🇪 Hetzner144.76.0.0/16 HETZNER-RZ-BLK-ERX1}
		PTR	`static.166.136.76.144.clients.your-server.de`
NS	`ns1.hostnext.net` ⭐ ⚠️ Not in parent delegation
		A	66.42.73.248^{🇺🇸 AS-VULTR66.42.64.0/20 Vultr Assigned Prefix}
			PTR	`ns1.hostnext.net`
NS	`n1.hostnext.net` ⚠️ Not in zone NS records
		A	66.42.73.248^{🇺🇸 AS-VULTR66.42.64.0/20 Vultr Assigned Prefix}
			PTR	`ns1.hostnext.net`
NS	`n2.hostnext.net` ⚠️ Not in zone NS records
		A	167.172.150.90^{🇺🇸 DIGITALOCEAN167.172.144.0/20 DigitalOcean}
			PTR	`ns2.hostnext.net`
NS	`ns2.hostnext.net` ⚠️ Not in parent delegation
		A	167.172.150.90^{🇺🇸 DIGITALOCEAN167.172.144.0/20 DigitalOcean}
			PTR	`ns2.hostnext.net`
MX	`virtualanchors.com` ⭐
		A	144.76.136.166^{🇩🇪 Hetzner144.76.0.0/16 HETZNER-RZ-BLK-ERX1}
			PTR	`static.166.136.76.144.clients.your-server.de`
TXT	`v=spf1 ip4:144.76.136.166 include:relay.mailchannels.net +a +mx +ip4:23.111.1...`
SOA	`ns1.hostnext.net`root@h32.eu.core.hostnext.net 2026-03-18 #1

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

MX for

virtualanchors.com

Same first word

virtualanchors.com

DNS History

11 records (6 active, 5 former)

●NSn1.hostnext.net2026-03-27 → 2026-03-27 · 2 obs

○ 2017-06-11 20:08:24
● 2026-03-27 03:30:40

●NSn2.hostnext.net2026-03-27 → 2026-03-27 · 2 obs

○ 2017-06-11 20:08:24
● 2026-03-27 03:30:40

○NSns.mainnameserver.com2015-07-16 → 2017-06-11 · 3 obs

● 2015-07-16 01:31:30
● 2017-06-11 20:08:24
○ 2026-03-27 03:30:40

●NSns1.hostnext.net2026-03-27 → 2026-03-27 · 2 obs

○ 2017-06-11 20:08:24
● 2026-03-27 03:30:40

●NSns2.hostnext.net2026-03-27 → 2026-03-27 · 2 obs

○ 2017-06-11 20:08:24
● 2026-03-27 03:30:40

○NSns2.mainnameserver.com2015-07-16 → 2017-06-11 · 3 obs

● 2015-07-16 01:31:30
● 2017-06-11 20:08:24
○ 2026-03-27 03:30:40

○MXmail.virtualanchors.com2015-07-16 → 2017-06-11 · 3 obs

● 2015-07-16 01:31:30
● 2017-06-11 20:08:24
○ 2026-03-27 03:30:40

●MXvirtualanchors.com2026-03-27 → 2026-03-27 · 2 obs

○ 2017-06-11 20:08:24
● 2026-03-27 03:30:40

●A144.76.136.1662026-03-27 → 2026-03-27 · 2 obs

○ 2017-06-11 20:08:24
● 2026-03-27 03:30:40

○A144.76.136.2532026-03-27 → 2026-03-27 · 1 obs

○ 2026-03-27 03:30:40

○A176.32.230.242015-07-16 → 2017-06-11 · 3 obs

● 2015-07-16 01:31:30
● 2017-06-11 20:08:24
○ 2026-03-27 03:30: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...	-
virtualanchors.com	n1.hostnext.net, n2.hostnext.net	-

✅ Authoritative Response

Server:66.42.73.248

NS records: n1.hostnext.net, n2.hostnext.net

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for virtualanchors.com (unsigned zone)

⏱️ Timing

Total: 430ms | Queries: -

📄 Records

Type	Count	Sample Data
A	1	`144.76.136.166`
NS	2	`ns1.hostnext.net, ns2.hostnext.net`
MX	1	`virtualanchors.com (pri: 0)`
TXT	1	`v=spf1 ip4:144.76.136.166 include:relay.`
SOA	1	`ns1.hostnext.net root.h32.eu.core.hostne`

Analysis

Mail Server Role

virtualanchors.com serves as a mail server for virtualanchors.com.

IP Addresses

virtualanchors.com points to a single IP: 144.76.136.166.

Other host names, for instance mail.jacquard.pk, kinghostpk.com, deeknight.blog, razabrotherind.com and frizcon.net share IP numbers with virtualanchors.com.

Name Servers

virtualanchors.com's delegation is handled by four name servers: n1.hostnext.net, n2.hostnext.net, ns1.hostnext.net and ns2.hostnext.net.

virtualanchors.com partially shares name servers with other domains; examples include finmortg.com.au, webdesigns.pk, smart.net.pk, slmc.edu.pk and slg.com.pk.