pariah.dk
Historical scan 2026-06-21 21:21:42 · ← Latest scan
pariah.dk is a .dk domain with no delegation in this scan. It was registered on 8 February 2022 (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#
No NS records found
A Records#
No A records found
MX Records#
No MX records found
AAAA Records (IPv6)#
No AAAA records — IPv6 not configured
HTTPS Records#
No HTTPS RR — no SVCB/HTTPS service binding
TXT Records#
No TXT records found
SPF#
No SPF record — mail spoofing not restricted
DMARC#
No DMARC record — mail spoofing not restricted
MTA-STS#
No MTA-STS policy — SMTP TLS not enforced
TLSRPT#
No TLSRPT record — no SMTP TLS failure reporting
CAA Records#
No CAA records — any CA may issue certificates
Web & zone#
latest probe, not this scan · checked 2026-11-10 06:52:38| www CNAME | shops.myshopify.com (all on myshopify.com) |
| www vs bare domain | Same network |
| Wildcard | No |
| Denial of existence | NSEC3 · 0 iterations · no salt RFC 9276 ✓ |
| CDS / CDNSKEY | None 0 CDS, 0 CDNSKEY |
TLSA / DANE#
No TLSA records — DANE not configured for HTTPS (_443) or MX (_25)
DNSSEC#
386ms| Check | Result |
|---|---|
| Validation Status | Not applicable: the domain has no delegation, so there is no zone to validate (stored verdict: Unknown). |
| AD Flag (resolver validates) | Not set |
| DS Record | Not found |
| DNSKEY Record | Not found |
| Flags | resolution failed: failure |
SOA#
No SOA record found
Registration#
WHOIS fetched 2026-11-10 07:04:36| Field | Value |
|---|---|
| Registrar | ONE.COM A/S |
| Registered | 2022-02-08 |
| Expires | 2027-02-07 (82d) |
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 yet
📋 WHOIS#
Lookup Timing#
NS
A
MX
AAAA
TXT
CAA
HTTPS
TLSA
SOA
MTA-STS
DNSSEC
SRV
Total
Scan History#
| Scanned At | Duration | Records | DNSSEC |
|---|---|---|---|
| 2026-11-10 06:52:38 | 539ms | 2 NS 1 A 4 MX | Secure |
| 2026-11-01 15:24:02 | 591ms | 2 NS 1 A 4 MX | Secure |
| 2026-10-18 02:00:17 | 484ms | 2 NS 1 A 4 MX | Secure |
| 2026-10-07 08:57:03 | 672ms | 2 NS 1 A 4 MX | Secure |
| 2026-10-04 03:27:33 | 4482ms | 2 NS 1 A 4 MX | Secure |
| 2026-09-22 11:12:25 | 2472ms | 2 NS 1 A 4 MX | Secure |
| 2026-09-06 19:11:20 | 604ms | 2 NS 1 A 4 MX | Secure |
| 2026-08-31 13:33:13 | 522ms | 2 NS 1 A 4 MX | Secure |
| 2026-08-27 18:13:45 | 806ms | 2 NS 1 A 4 MX | Secure |
| 2026-08-20 19:45:51 | 4927ms | 2 NS 1 A 4 MX | Secure |
| 2026-08-19 17:30:39 | 6245ms | 2 NS 1 A 4 MX | Secure |
| 2026-08-18 17:28:12 | 14266ms | 2 NS 0 A 4 MX | Secure |
| 2026-07-29 11:00:48 | 5037ms | 2 NS 1 A 4 MX | Secure |
| 2026-07-13 02:21:30 | 907ms | 2 NS 1 A 4 MX | Secure |
| 2026-06-23 08:24:16 | 1322ms | 2 NS 1 A 4 MX | Secure |
| 2026-06-21 21:21:42 shown | 1170ms | 0 NS 0 A 0 MX | Unknown |
| 2026-06-21 03:45:11 | 1344ms | 2 NS 1 A 4 MX | Secure |
| 2026-06-17 23:49:34 | 694ms | 2 NS 1 A 4 MX | Secure |