katastrofeberedskabet.dk
Historical scan 2026-06-24 05:13:12 · ← Latest scan
katastrofeberedskabet.dk is a .dk domain with no delegation in this scan. It was registered on 6 February 2013 (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-13 14:51:51| www | 213.174.68.36 (AS44398) (address records, no CNAME) |
| www vs bare domain | Same network katastrofeberedskabet.dk: 213.174.68.36 (AS44398) www.katastrofeberedskabet.dk: 213.174.68.36 (AS44398) |
| 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#
472ms| 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-05 04:58:56| Field | Value |
|---|---|
| Registrar | Key-Systems GmbH |
| Registered | 2013-02-06 |
| Expires | 2027-02-28 (102d) |
Same registrant#
372 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).
Showing 100 of 372.
📋 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-13 14:51:50 | 1244ms | 5 NS 1 A 0 MX | Secure |
| 2026-11-05 04:46:44 | 1622ms | 5 NS 1 A 0 MX | Secure |
| 2026-10-29 18:57:43 | 585ms | 5 NS 1 A 0 MX | Secure |
| 2026-10-24 06:44:32 | 4464ms | 5 NS 1 A 0 MX | Secure |
| 2026-10-15 22:48:52 | 775ms | 5 NS 1 A 0 MX | Secure |
| 2026-10-09 11:09:22 | 685ms | 5 NS 1 A 0 MX | Secure |
| 2026-10-08 10:24:10 | 2138ms | 5 NS 1 A 0 MX | Secure |
| 2026-10-01 05:52:50 | 1827ms | 5 NS 1 A 0 MX | Secure |
| 2026-09-24 03:38:52 | 4487ms | 5 NS 1 A 0 MX | Secure |
| 2026-09-21 21:36:55 | 1089ms | 5 NS 1 A 0 MX | Secure |
| 2026-09-11 15:55:19 | 1385ms | 5 NS 1 A 0 MX | Secure |
| 2026-09-04 09:02:20 | 690ms | 5 NS 1 A 0 MX | Secure |
| 2026-08-27 15:08:24 | 1267ms | 5 NS 1 A 0 MX | Secure |
| 2026-08-26 13:44:22 | 4635ms | 5 NS 1 A 0 MX | Secure |
| 2026-08-20 06:07:48 | 5267ms | 5 NS 1 A 0 MX | Secure |
| 2026-08-13 22:35:31 | 843ms | 5 NS 1 A 0 MX | Secure |
| 2026-08-07 18:34:32 | 940ms | 5 NS 1 A 0 MX | Secure |
| 2026-07-23 09:43:51 | 5006ms | 5 NS 1 A 0 MX | Secure |
| 2026-07-17 21:08:41 | 2729ms | 5 NS 1 A 0 MX | Secure |
| 2026-07-11 15:44:30 | 11633ms | 5 NS 1 A 0 MX | Secure |
| 2026-07-03 13:17:18 | 6833ms | 5 NS 1 A 0 MX | Secure |
| 2026-06-25 05:36:45 | 3124ms | 5 NS 1 A 0 MX | Secure |
| 2026-06-24 05:13:12 shown | 1203ms | 0 NS 0 A 0 MX | Unknown |
| 2026-06-23 23:12:03 | 1844ms | 5 NS 1 A 0 MX | Secure |
| 2026-06-19 23:03:50 | 3325ms | 5 NS 1 A 0 MX | Secure |