epelch.dk
Historical scan 2026-06-23 11:28:08 · ← Latest scan
epelch.dk is a .dk domain with no delegation in this scan. It was registered on 7 April 2018 (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-21 03:59:47| www | 46.30.213.24 2a02:2350:5:10a:c6:fd3d:793:8139 (AS51468) (address records, no CNAME) |
| www vs bare domain | Same network epelch.dk: 46.30.213.24 2a02:2350:5:10a:c6:fd3d:793:8139 (AS51468) www.epelch.dk: 46.30.213.24 2a02:2350:5:10a:c6:fd3d:793:8139 (AS51468) |
| 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#
319ms| 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-21 04:23:06| Field | Value |
|---|---|
| Registrar | Punktum dk A/S (direct) |
| Registered | 2018-04-07 |
| Expires | 2027-04-30 (158d) |
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-21 03:59:47 | 653ms | 2 NS 1 A 3 MX | Secure |
| 2026-11-02 01:45:57 | 453ms | 2 NS 1 A 3 MX | Secure |
| 2026-10-24 18:45:36 | 452ms | 2 NS 1 A 3 MX | Secure |
| 2026-10-23 08:43:10 | 1730ms | 2 NS 1 A 3 MX | Secure |
| 2026-10-19 00:45:16 | 748ms | 2 NS 1 A 3 MX | Secure |
| 2026-10-17 00:00:23 | 604ms | 2 NS 1 A 3 MX | Secure |
| 2026-10-09 10:11:50 | 563ms | 2 NS 1 A 2 MX | Secure |
| 2026-10-02 13:16:38 | 34367ms | 2 NS 1 A 3 MX | Secure |
| 2026-09-28 12:45:34 | 662ms | 2 NS 1 A 2 MX | Secure |
| 2026-09-04 23:20:25 | 582ms | 2 NS 1 A 3 MX | Secure |
| 2026-08-28 17:40:28 | 3035ms | 2 NS 1 A 3 MX | Secure |
| 2026-08-26 16:16:43 | 656ms | 2 NS 1 A 3 MX | Secure |
| 2026-08-20 18:09:00 | 3863ms | 2 NS 1 A 3 MX | Secure |
| 2026-08-03 07:00:02 | 1733ms | 2 NS 1 A 3 MX | Secure |
| 2026-07-17 12:52:15 | 16838ms | 2 NS 1 A 3 MX | Secure |
| 2026-07-01 18:29:08 | 949ms | 2 NS 1 A 3 MX | Secure |
| 2026-06-24 19:24:41 | 1832ms | 2 NS 1 A 3 MX | Secure |
| 2026-06-23 11:28:08 shown | 1390ms | 0 NS 0 A 0 MX | Unknown |
| 2026-06-17 07:50:45 | 593ms | 2 NS 1 A 3 MX | Secure |