`technicalverification.com`

DNSSEC	⚠️ Not signed
NS	`ns-cloud-a1.googledomains.com` ⚠️ Not in zone NS records
		A	2001:4860:4802:32::6a^{🇺🇸 Google2001:4860::/32}
			PTR	`ns-cloud-a1.googledomains.com`
		A	216.239.32.106^{🇺🇸 Google216.239.32.0/24}
			PTR	`ns-cloud-a1.googledomains.com`
NS	`ns-cloud-a2.googledomains.com` ⚠️ Not in zone NS records
		A	2001:4860:4802:34::6a^{🇺🇸 Google2001:4860::/32}
			PTR	`ns-cloud-a2.googledomains.com`
		A	216.239.34.106^{🇺🇸 Google216.239.34.0/24}
			PTR	`ns-cloud-a2.googledomains.com`

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

PTR for

247.227.20.178.in-addr.arpa

Subdomains

ns2.technicalverification.com

ns1.technicalverification.com

Same first word

technicalverification.com

DNS History

9 records (2 active, 7 former)

●NSns-cloud-a1.googledomains.com2026-04-11 → 2026-05-13 · 3 obs

○ 2017-04-20 09:42:14
● 2026-04-11 08:51:24
● 2026-05-13 02:09:36

●NSns-cloud-a2.googledomains.com2026-04-11 → 2026-05-13 · 3 obs

○ 2017-04-20 09:42:14
● 2026-04-11 08:51:24
● 2026-05-13 02:09:36

○NSns1.skarpodata.com2015-06-26 → 2017-04-20 · 4 obs

● 2015-06-26 19:26:06
● 2017-04-20 09:42:14
○ 2026-04-11 08:51:24
○ 2026-05-13 02:09:36

○NSns1.technicalverification.com2026-04-11 → 2026-05-13 · 2 obs

○ 2026-04-11 08:51:24
○ 2026-05-13 02:09:36

○NSns2.skarpodata.com2015-06-26 → 2017-04-20 · 4 obs

● 2015-06-26 19:26:06
● 2017-04-20 09:42:14
○ 2026-04-11 08:51:24
○ 2026-05-13 02:09:36

○NSns2.technicalverification.com2026-04-11 → 2026-05-13 · 2 obs

○ 2026-04-11 08:51:24
○ 2026-05-13 02:09:36

○MXmx.technicalverification.com2026-04-11 → 2026-05-13 · 2 obs

○ 2026-04-11 08:51:24
○ 2026-05-13 02:09:36

○A178.20.227.2472026-04-11 → 2026-05-13 · 2 obs

○ 2026-04-11 08:51:24
○ 2026-05-13 02:09:36

○A79.136.112.1082015-11-01 → 2017-04-20 · 4 obs

● 2015-11-01 09:46:10
● 2017-04-20 09:42:14
○ 2026-04-11 08:51:24
○ 2026-05-13 02:09:36

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	f.gtld-servers.net, b.gtld-servers.net, a.gtld-servers.net, d.gtld-servers.net...	-
technicalverification.com	ns-cloud-a1.googledomains.com, ns-cloud-a2.googledomains.com	4 records

✅ Authoritative Response

Server:216.239.34.106

NS records: ns-cloud-a1.googledomains.com, ns-cloud-a2.googledomains.com

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for technicalverification.com (unsigned zone)

⏱️ Timing

Total: 1668ms | Queries: -

📄 Records

Type	Count	Sample Data

📌 Glue Records Collected

Total: 4

Out-of-bailiwick: 4 (ns-cloud-a1.googledomains.com, ns-cloud-a1.googledomains.com, ns-cloud-a2.googledomains.com...)

Analysis

Hierarchy

technicalverification.com is a parent of ns2.technicalverification.com and ns1.technicalverification.com.

Name Servers

technicalverification.com is delegated to two name servers: ns-cloud-a1.googledomains.com and ns-cloud-a2.googledomains.com.

technicalverification.com uses the same name server setup as other domains such as hdmagazine.org, kydems.org, healstudio.art, impetusjewellery.com and xthinker.org.

technicalverification.com shares name servers with other domains at least partially, for example veracron.com, myriadmarks.com, la.camera, zenmf.com and shipard.pro.

These name servers are commonly used with the name servers ns-cloud-a3.googledomains.com and ns-cloud-a4.googledomains.com.

Host names with two IP numbers:

ns-cloud-a1.googledomains.com points to 2001:4860:4802:32::6a and 216.239.32.106; ns-cloud-a2.googledomains.com points to 2001:4860:4802:34::6a and 216.239.34.106.

technicalverification.com - robtex.com