`pandoraclearance.com`

DNSSEC	⚠️ Not signed
A	44.195.229.203^{🇺🇸 Amazon44.192.0.0/11 EC2 IAD prefix}
		PTR	`ec2-44-195-229-203.compute-1.amazonaws.com`
A	52.200.66.12^{🇺🇸 Amazon52.200.0.0/13 EC2 IAD prefix}
NS	`ns1.domain-is-4-sale-at-domainmarket.com` ⭐
		A	35.169.19.39^{🇺🇸 Amazon35.168.0.0/13 EC2 IAD prefix}
			PTR	`ec2-35-169-19-39.compute-1.amazonaws.com`
NS	`ns2.domainmarket.com`
		A	3.216.12.111^{🇺🇸 Amazon3.208.0.0/12 EC2 IAD prefix}
			PTR	`ec2-3-216-12-111.compute-1.amazonaws.com`
TXT	`09ee649ae5a1b195b9c2422ce34a26e7eb49a40d`
SOA	`ns1.domain-is-4-sale-at-domainmarket.com`hostmaster@domainmarket.com serial=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=1774367522

WOT: SUSPICIOUS (1/100)

Same first word

pandoraclearance.com

DNS History

21 records (4 active, 17 former)

○NSdns1.registrar-servers.com2015-05-30 → 2016-03-23 · 4 obs

● 2015-05-30 16:42:48
● 2016-03-23 12:16:58
○ 2016-07-23 03:06:58
○ 2026-03-24 16:15:04

○NSdns2.registrar-servers.com2015-05-30 → 2016-03-23 · 4 obs

● 2015-05-30 16:42:48
● 2016-03-23 12:16:58
○ 2016-07-23 03:06:58
○ 2026-03-24 16:15:04

○NSdns3.registrar-servers.com2015-05-30 → 2016-03-23 · 4 obs

● 2015-05-30 16:42:48
● 2016-03-23 12:16:58
○ 2016-07-23 03:06:58
○ 2026-03-24 16:15:04

○NSdns4.registrar-servers.com2015-05-30 → 2016-03-23 · 4 obs

● 2015-05-30 16:42:48
● 2016-03-23 12:16:58
○ 2016-07-23 03:06:58
○ 2026-03-24 16:15:04

○NSdns5.registrar-servers.com2015-05-30 → 2016-03-23 · 4 obs

● 2015-05-30 16:42:48
● 2016-03-23 12:16:58
○ 2016-07-23 03:06:58
○ 2026-03-24 16:15:04

●NSns1.domain-is-4-sale-at-domainmarket.com2020-03-06 → 2026-03-24 · 3 obs

○ 2017-03-21 16:44:48
● 2020-03-06 01:59:34
● 2026-03-24 16:15:04

●NSns2.domainmarket.com2026-02-22 → 2026-03-24 · 3 obs

○ 2020-03-06 01:59:34
● 2026-02-22 13:33:32
● 2026-03-24 16:15:04

○NSvip6623050.earth.orderbox-dns.com2017-03-21 → 2017-03-21 · 4 obs

○ 2016-07-23 03:06:58
● 2017-03-21 16:44:48
○ 2020-03-06 01:59:34
○ 2026-03-24 16:15:04

○NSvip6623050.mars.orderbox-dns.com2017-03-21 → 2017-03-21 · 4 obs

○ 2016-07-23 03:06:58
● 2017-03-21 16:44:48
○ 2020-03-06 01:59:34
○ 2026-03-24 16:15:04

○NSvip6623050.mercury.orderbox-dns.com2017-03-21 → 2017-03-21 · 4 obs

○ 2016-07-23 03:06:58
● 2017-03-21 16:44:48
○ 2020-03-06 01:59:34
○ 2026-03-24 16:15:04

○NSvip6623050.venus.orderbox-dns.com2017-03-21 → 2017-03-21 · 4 obs

○ 2016-07-23 03:06:58
● 2017-03-21 16:44:48
○ 2020-03-06 01:59:34
○ 2026-03-24 16:15:04

○MXeforward1.registrar-servers.com2015-10-15 → 2016-03-23 · 4 obs

● 2015-10-15 13:49:44
● 2016-03-23 12:16:58
○ 2016-07-23 03:06:58
○ 2026-03-24 16:15:04

○MXeforward2.registrar-servers.com2015-10-15 → 2016-03-23 · 4 obs

● 2015-10-15 13:49:44
● 2016-03-23 12:16:58
○ 2016-07-23 03:06:58
○ 2026-03-24 16:15:04

○MXeforward3.registrar-servers.com2015-10-15 → 2016-03-23 · 4 obs

● 2015-10-15 13:49:44
● 2016-03-23 12:16:58
○ 2016-07-23 03:06:58
○ 2026-03-24 16:15:04

○MXeforward4.registrar-servers.com2015-10-15 → 2016-03-23 · 4 obs

● 2015-10-15 13:49:44
● 2016-03-23 12:16:58
○ 2016-07-23 03:06:58
○ 2026-03-24 16:15:04

○MXeforward5.registrar-servers.com2015-10-15 → 2016-03-23 · 4 obs

● 2015-10-15 13:49:44
● 2016-03-23 12:16:58
○ 2016-07-23 03:06:58
○ 2026-03-24 16:15:04

○A208.98.56.1742015-05-30 → 2016-03-23 · 4 obs

● 2015-05-30 16:42:48
● 2016-03-23 12:16:58
○ 2016-07-23 03:06:58
○ 2026-03-24 16:15:04

○A209.134.10.2032017-03-21 → 2017-03-21 · 4 obs

○ 2016-07-23 03:06:58
● 2017-03-21 16:44:48
○ 2020-03-06 01:59:34
○ 2026-03-24 16:15:04

●A44.195.229.2032026-02-22 → 2026-03-24 · 3 obs

○ 2020-03-06 01:59:34
● 2026-02-22 13:33:32
● 2026-03-24 16:15:04

●A52.200.66.122026-02-22 → 2026-03-24 · 3 obs

○ 2020-03-06 01:59:34
● 2026-02-22 13:33:32
● 2026-03-24 16:15:04

○CNAMEnb-69-164-223-52.newark.nodebalancer.linode.com2020-03-06 → 2020-03-06 · 3 obs

● 2020-03-06 01:59:34
○ 2026-02-22 13:33:32
○ 2026-03-24 16:15:04

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	a.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net...	-
pandoraclearance.com	ns2.domainmarket.com, ns1.domain-is-4-sale-at-domainmarket.com	2 records

✅ Authoritative Response

Server:35.169.19.39

NS records: ns2.domainmarket.com, ns1.domain-is-4-sale-at-domainmarket.com

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for pandoraclearance.com (unsigned zone)

⏱️ Timing

Total: 3474ms | Queries: -

📄 Records

Type	Count	Sample Data
A	2	`44.195.229.203, 52.200.66.12`
NS	2	`ns2.domainmarket.com, ns1.domain-is-4-sale-at-domainmarket.com`
TXT	1	`09ee649ae5a1b195b9c2422ce34a26e7eb49a40d`
SOA	1	`ns1.domain-is-4-sale-at-domainmarket.com`

📌 Glue Records Collected

Total: 2

Out-of-bailiwick: 2 (ns2.domainmarket.com, ns1.domain-is-4-sale-at-domainmarket.com)

Analysis

IP Addresses

pandoraclearance.com points to two IP numbers: 44.195.229.203 and 52.200.66.12.

Other host names such as dindak.com, filtram.com, samael.com, emotionalchord.com and quickcashrealestate.com share IPs with pandoraclearance.com.

Name Servers

pandoraclearance.com is delegated to two name servers: ns1.domain-is-4-sale-at-domainmarket.com and ns2.domainmarket.com.

pandoraclearance.com shares the same name server setup as gerust.com, agricdev.com, turkseries.com, chocoloko.com and kingfisherholidays.com.

Host names with a single IP:

ns1.domain-is-4-sale-at-domainmarket.com points to 35.169.19.39.

ns2.domainmarket.com points to 3.216.12.111.

pandoraclearance.com - robtex.com