`questionably.com`

DNSSEC	⚠️ Not signed
A	64.99.64.37^{🇨🇦 TUCOWS64.99.0.0/16 Tucows.com Co}
		PTR	`osrs.systemdns.com`
NS	`ns1.systemdns.com` ⭐
		A	2604:4000:0:d:216:40:47:90^{🇨🇦 TUCOWS2604:4000::/48 -BRA-IPV6-BLK1.1/NET-2604:4000}
			PTR	`ns1.systemdns.com`
		A	216.40.47.90^{🇨🇦 TUCOWS216.40.47.0/24 -BRA-BLK1.4/NET-216-40-47-0}
			PTR	`ns1.systemdns.com`
NS	`ns2.systemdns.com`
		A	2604:4000:2800:d:64:99:148:16^{🇨🇦 TUCOWS-32604:4000:2800::/37 Tucows.com Co.}
			PTR	`ns2.systemdns.com`
		A	64.98.148.16^{🇨🇦 TUCOWS-364.98.144.0/20 Tucows.com Co.}
			PTR	`ns2.systemdns.com`
NS	`ns3.systemdns.com`
		A	2604:4000:0:d:64:99:96:36^{🇨🇦 TUCOWS2604:4000::/48 -BRA-IPV6-BLK1.1/NET-2604:4000}
			PTR	`ns3.systemdns.com`
		A	64.99.96.36^{🇨🇦 TUCOWS64.99.96.0/24 -BRA-BLK2.7.2}
			PTR	`ns3.systemdns.com`
SOA	`ns1.systemdns.com`hostmaster@systemdns.com serial=1751977850

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

Same first word

questionably.com

DNS History

4 records (4 active, 0 former)

●NSns1.systemdns.com2015-05-22 → 2026-03-18 · 3 obs

○ 2008-03-19 08:27:28
● 2015-05-22 23:37:46
● 2026-03-18 03:35:44

●NSns2.systemdns.com2015-05-22 → 2026-03-18 · 3 obs

○ 2008-03-19 08:27:28
● 2015-05-22 23:37:46
● 2026-03-18 03:35:44

●NSns3.systemdns.com2015-05-22 → 2026-03-18 · 3 obs

○ 2008-03-19 08:27:28
● 2015-05-22 23:37:46
● 2026-03-18 03:35:44

●A64.99.64.372015-11-01 → 2026-03-18 · 2 obs

● 2015-11-01 12:37:26
● 2026-03-18 03:35:44

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	a.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net...	-
questionably.com	ns1.systemdns.com, ns2.systemdns.com, ns3.systemdns.com	6 records

✅ Authoritative Response

Server: 64.99.96.36

NS records: ns1.systemdns.com, ns2.systemdns.com, ns3.systemdns.com

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for questionably.com (unsigned zone)

⏱️ Timing

Total: 379ms | Queries: -

📄 Records

Type	Count	Sample Data
A	1	`64.99.64.37`
NS	3	`ns2.systemdns.com, ns3.systemdns.com...`
SOA	1	`ns1.systemdns.com hostmaster.systemdns.c`

📌 Glue Records Collected

Total: 6

Out-of-bailiwick: 6 (ns1.systemdns.com, ns1.systemdns.com, ns2.systemdns.com...)

Analysis

IP Addresses

questionably.com points to a single IP number: 64.99.64.37.

Other host names, for instance christhom.com, cedrsystems.org, 112-60-server.outer-net.com, ko-hen.ca and triadatms.com share IP numbers with questionably.com.

Name Servers

The delegation for questionably.com is handled by three name servers: ns1.systemdns.com, ns2.systemdns.com and ns3.systemdns.com.

questionably.com at least partially shares name servers with other domains, for instance totallyadd.com, 1clickstudio.org, mingscollectibles.com, account-netflix.fyi and gandptransport.com.

Two IP numbers per host:

ns1.systemdns.com points to 2604:4000:0:d:216:40:47:90 and 216.40.47.90.

ns2.systemdns.com points to 2604:4000:2800:d:64:99:148:16 and 64.98.148.16.

ns3.systemdns.com points to 2604:4000:0:d:64:99:96:36 and 64.99.96.36.

questionably.com - robtex.com