pidaworks.com - dns.ninja
pidaworks.com
| DNSSEC | ⚠️ Not signed | ||||||
| NS | ns1.vultr.com ⚠️ Not in zone NS records | ||||||
| A | 2001:19f0:ccc::1🇺🇸 AS-VULTR2001:19f0:ccc::/48 DNS1 | ||||||
| A | 2001:19f0:ccd::1🇺🇸 AS-VULTR2001:19f0:ccd::/48 Vultr Assigned Prefix | ||||||
| PTR | ns1.vultr.com | ||||||
| A | 173.199.96.96🇺🇸 AS-VULTR173.199.96.0/24 Vultr Assigned Prefix | ||||||
| PTR | ns1.vultrusercontent.com | ||||||
| NS | ns2.vultr.com ⚠️ Not in zone NS records | ||||||
| A | 2001:19f0:ccc::2🇺🇸 AS-VULTR2001:19f0:ccc::/48 DNS1 | ||||||
| A | 2001:19f0:ccd::2🇺🇸 AS-VULTR2001:19f0:ccd::/48 Vultr Assigned Prefix | ||||||
| PTR | ns2.vultr.com | ||||||
| A | 173.199.96.97🇺🇸 AS-VULTR173.199.96.0/24 Vultr Assigned Prefix | ||||||
| PTR | ns2.vultrusercontent.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.netnstld@verisign-grs.com serial=1785930829 | ||||||
Same first word
pidaworks.com |
Similar names
DNS History
6 records (2 active, 4 former)
○NSns1.ksdom.kr2015-08-04 → 2018-09-24 · 4 obs
● 2018-09-24 09:15:36
○ 2026-06-28 08:17:34
○ 2026-08-05 12:10:54
●NSns1.vultr.com2026-06-28 → 2026-08-05 · 3 obs
● 2026-06-28 08:17:34
● 2026-08-05 12:10:54
○NSns2.ksdom.kr2015-08-04 → 2018-09-24 · 4 obs
● 2018-09-24 09:15:36
○ 2026-06-28 08:17:34
○ 2026-08-05 12:10:54
●NSns2.vultr.com2026-06-28 → 2026-08-05 · 3 obs
● 2026-06-28 08:17:34
● 2026-08-05 12:10:54
○MXmailapp.hiworks.co.kr2015-08-04 → 2018-09-24 · 4 obs
● 2018-09-24 09:15:36
○ 2026-06-28 08:17:34
○ 2026-08-05 12:10:54
○A115.68.13.2372015-08-04 → 2018-09-24 · 4 obs
● 2018-09-24 09:15:36
○ 2026-06-28 08:17:34
○ 2026-08-05 12:10:54
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| com | m.gtld-servers.net, b.gtld-servers.net, e.gtld-servers.net, l.gtld-servers.net... | - |
| pidaworks.com | ns1.vultr.com, ns2.vultr.com | 4 records |
✅ Authoritative Response
Server:173.199.96.97
NS records: ns1.vultr.com, ns2.vultr.com
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for pidaworks.com (unsigned zone)
⏱️ Timing
Total: 127ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|
📌 Glue Records Collected
Total: 4
Out-of-bailiwick: 4 (ns1.vultr.com, ns1.vultr.com, ns2.vultr.com...)
Analysis
Name Servers
pidaworks.com is delegated to two name servers: ns1.vultr.com and ns2.vultr.com.
The name server configuration of pidaworks.com is shared with other domains, for instance qianmingzhu.com, radiofreqs.space, (0x68656e746169)folder.com and two others.
pidaworks.com has at least partial name server overlap with other domains, such as inthewash.co.uk, stagg.plumbing, lauragriesbach.com and two others.
These name servers tend to appear together with the name servers ns1.wpdns.host, ns2.wpdns.host and ns3.wpdns.host.
ns1.vultr.com and ns2.vultr.com each have three IP addresses — ns1.vultr.com directs to 173.199.96.96, 2001:19f0:ccc::1 and 2001:19f0:ccd::1; ns2.vultr.com directs to 173.199.96.97, 2001:19f0:ccc::2 and 2001:19f0:ccd::2.