jm-madexpressen.dk
Historical scan 2026-08-23 12:04:46 · ← Latest scan
jm-madexpressen.dk is a .dk domain served by 2 nameservers (ns01.one.com, ns02.one.com). It was registered on 18 November 2026 (WHOIS) and was already in the .dk zone when our tracking began on 16 June 2026. The zone is DNSSEC-signed and validates, has no DMARC policy and has no IPv6 address. 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 48msA 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#
1 records 182ms| TXT Record |
|---|
| v=spf1 -all |
SPF#
| Policy | Record (jm-madexpressen.dk) |
|---|---|
| -all (hard fail) | v=spf1 -all |
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
SPF check#
zone-wide SPF reportDNS lookups: 0/10 · policy: -all
No problems foundTLSA / DANE#
No TLSA records — DANE not configured for HTTPS (_443) or MX (_25)
DNSSEC#
111ms| Check | Result |
|---|---|
| Validation Status | Secure |
| AD Flag (resolver validates) | Set |
| DS Record | Found |
| DNSKEY Record | Found |
| Flags | resolution failed: ncache nxrrset |
SOA#
0ms| Field | Value |
|---|---|
| Serial | 2026082301 |
| Primary NS (MNAME) | ns01.one.com |
| Responsible (RNAME) | hostmaster@one.com |
| Refresh | 14400s |
| Retry | 3600s |
| Expire | 1209600s |
| Minimum (neg-cache TTL) | 600s |
Registration#
WHOIS fetched 2026-11-19 08:57:07| Field | Value |
|---|---|
| Registrar | Dynadot LLC |
| Registered | 2026-11-18 |
| Expires | 2027-11-17 (363d) |
Same registrant#
38 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).
📋 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-10-02 05:58:37 | 246ms | 1 NS 0 A 0 MX | Unknown |
| 2026-10-01 05:51:43 | 234ms | 1 NS 0 A 0 MX | Unknown |
| 2026-09-30 05:43:57 | 229ms | 1 NS 0 A 0 MX | Unknown |
| 2026-09-29 05:33:59 | 232ms | 1 NS 0 A 0 MX | Unknown |
| 2026-09-28 05:15:56 | 213ms | 1 NS 0 A 0 MX | Unknown |
| 2026-09-27 05:00:43 | 209ms | 1 NS 0 A 0 MX | Unknown |
| 2026-09-26 04:45:15 | 337ms | 1 NS 0 A 0 MX | Unknown |
| 2026-09-25 04:17:50 | 225ms | 1 NS 0 A 0 MX | Unknown |
| 2026-09-24 03:44:16 | 239ms | 1 NS 0 A 0 MX | Unknown |
| 2026-09-21 02:29:31 | 210ms | 1 NS 0 A 0 MX | Unknown |
| 2026-09-19 15:53:32 | 230ms | 1 NS 0 A 0 MX | Unknown |
| 2026-09-15 11:32:13 | 289ms | 1 NS 0 A 0 MX | Unknown |
| 2026-09-10 00:45:46 | 237ms | 1 NS 0 A 0 MX | Unknown |
| 2026-09-07 21:56:19 | 1215ms | 1 NS 0 A 0 MX | Unknown |
| 2026-09-01 00:51:50 | 808ms | 2 NS 0 A 0 MX | Secure |
| 2026-08-30 18:27:39 | 359ms | 2 NS 0 A 0 MX | Secure |
| 2026-08-29 17:18:37 | 646ms | 2 NS 0 A 0 MX | Secure |
| 2026-08-28 14:15:59 | 393ms | 2 NS 0 A 0 MX | Secure |
| 2026-08-27 13:29:02 | 594ms | 2 NS 0 A 0 MX | Secure |
| 2026-08-27 03:57:15 | 497ms | 2 NS 0 A 0 MX | Secure |
| 2026-08-26 18:29:10 | 427ms | 2 NS 0 A 0 MX | Secure |
| 2026-08-25 16:00:47 | 967ms | 2 NS 0 A 0 MX | Secure |
| 2026-08-24 13:26:49 | 1011ms | 2 NS 0 A 0 MX | Secure |
| 2026-08-23 12:04:46 shown | 658ms | 2 NS 0 A 0 MX | Secure |
| 2026-08-22 09:06:56 | 1067ms | 2 NS 0 A 0 MX | Secure |