pidsa.dk
pidsa.dk is a registered .dk domain whose nameservers (ns01.one.com, ns02.one.com) do not answer for it, so it is currently a lame delegation and does not resolve. It was registered on 16 May 2024 (WHOIS) and was already in the .dk zone when our tracking began on 16 June 2026. Below are all of its DNS records from this scan: nameservers, A/AAAA, MX, TXT, SPF, DMARC, CAA, TLSA/DANE, MTA-STS, SRV and more.
Nameservers#
2 records 353msA Records#
MX Records#
AAAA Records (IPv6)#
HTTPS Records#
TXT Records#
SPF#
DMARC#
MTA-STS#
TLSRPT#
CAA Records#
Web & zone#
latest probe, not this scan · checked 2026-11-09 03:13:37| www CNAME | pidsa.dk (all on pidsa.dk) |
| www vs bare domain | Same network |
| Wildcard | No |
| Denial of existence | Compact NSEC (RFC 9824, "black lies") not walkable |
| CDS / CDNSKEY | Published: key rollovers can be automated with the registry (RFC 7344/8078) 1 CDS, 1 CDNSKEY |
DKIM keys#
1 found| Selector | CNAME | Key |
|---|---|---|
| default | — | RSA · ~2048 bit |
DKIM selectors can't be listed, so we check the common ones (Microsoft 365, Google, Mailchimp, SendGrid, generic). Keys under other selectors aren't shown.
TLSA / DANE#
DNSSEC#
712ms| Check | Result |
|---|---|
| Validation Status | Bogus — the parent still publishes a DS record, but the delegated nameservers don't answer, so no signed answer can be fetched. The zone isn't serving broken signatures; it isn't serving at all. |
| AD Flag (resolver validates) | Not set |
| DS Record | Found |
| DNSKEY Record | Not found |
| Flags | resolution failed: failure |
SOA#
Registration#
WHOIS fetched 2026-11-04 02:33:51| Field | Value |
|---|---|
| Registrar | nordicway ApS |
| Registered | 2024-05-16 |
| Expires | 2027-05-15 (179d) |
Same registrant#
0 domainsOther .dk domains whose WHOIS registrant has the same name and postal address. Matched on a keyed hash: the registrant's details are not stored or shown. Covers only domains whose WHOIS we have fetched (refreshed about monthly).
No other domain with this registrant in our WHOIS data yetLookup Timing#
Scan History#
| Scanned At | Duration | Records | DNSSEC |
|---|---|---|---|
| 2026-11-09 03:13:37 | 384ms | 2 NS 1 A 1 MX | Secure |
| 2026-11-04 02:22:31 | 1885ms | 2 NS 1 A 1 MX | Secure |
| 2026-10-27 16:29:27 | 51836ms | 2 NS 0 A 0 MX | Unknown |
| 2026-09-17 09:13:33 | 35043ms | 2 NS 0 A 0 MX | Unknown |
| 2026-08-23 07:20:37 | 2907ms | 2 NS 0 A 0 MX | Bogus |
| 2026-08-22 07:18:32 | 4641ms | 2 NS 0 A 0 MX | Bogus |
| 2026-08-21 07:10:36 | 5420ms | 2 NS 0 A 0 MX | Bogus |
| 2026-08-20 05:44:23 | 6946ms | 2 NS 0 A 0 MX | Bogus |
| 2026-08-19 04:18:56 shown | 5496ms | 2 NS 0 A 0 MX | Bogus |
| 2026-08-18 02:01:02 | 1886ms | 2 NS 0 A 0 MX | Bogus |
| 2026-08-16 16:44:12 | 2922ms | 2 NS 0 A 0 MX | Bogus |
| 2026-08-15 09:22:51 | 27941ms | 2 NS 0 A 0 MX | Unknown |
| 2026-08-13 00:31:11 | 3331ms | 2 NS 0 A 0 MX | Bogus |
| 2026-08-11 16:20:27 | 10128ms | 2 NS 0 A 0 MX | Bogus |
| 2026-08-10 14:43:32 | 865ms | 2 NS 0 A 0 MX | Bogus |
| 2026-08-08 07:16:11 | 1434ms | 2 NS 0 A 0 MX | Bogus |
| 2026-08-06 07:58:43 | 1501ms | 2 NS 0 A 0 MX | Bogus |
| 2026-08-02 03:13:18 | 2950ms | 2 NS 0 A 0 MX | Bogus |
| 2026-07-27 16:36:33 | 947ms | 2 NS 0 A 0 MX | Bogus |
| 2026-07-26 16:18:33 | 10035ms | 2 NS 0 A 0 MX | Bogus |
| 2026-07-25 15:55:03 | 925ms | 2 NS 0 A 0 MX | Bogus |
| 2026-07-24 15:32:04 | 1023ms | 2 NS 0 A 0 MX | Bogus |
| 2026-07-23 13:46:43 | 949ms | 2 NS 0 A 0 MX | Bogus |
| 2026-07-22 02:30:45 | 1180ms | 2 NS 0 A 0 MX | Bogus |
| 2026-07-19 20:53:58 | 1024ms | 2 NS 0 A 0 MX | Bogus |