stefanbrorsen.dk

Historical scan 2026-06-22 19:03:34  ·  ← Latest scan
Zone File Timeline & History Scan Now

stefanbrorsen.dk is a .dk domain with no delegation in this scan. It was registered on 4 September 2009 (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-19 17:22:33
www CNAMEstefanbrorsen.dk (all on stefanbrorsen.dk)
www vs bare domainSame network
stefanbrorsen.dk: 46.183.138.100 (AS47292)
www.stefanbrorsen.dk: 46.183.138.100 (AS47292)
WildcardYes: any name under the zone resolves

TLSA / DANE#

No TLSA records — DANE not configured for HTTPS (_443) or MX (_25)

DNSSEC#

459ms
CheckResult
Validation StatusNot 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
Flagsresolution failed: failure

SOA#

No SOA record found

Registration#

WHOIS fetched 2026-11-13 05:49:09
FieldValue
RegistrarPunktum dk A/S (direct)
Registered2009-09-04
Expires2027-09-30 (314d)

Same registrant#

0 domains

Other .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
169ms
A
218ms
MX
177ms
AAAA
168ms
TXT
490ms
CAA
211ms
HTTPS
197ms
TLSA
17ms
SOA
209ms
MTA-STS
170ms
DNSSEC
459ms
SRV
220ms
Total
1177ms

Scan History#

Scanned AtDurationRecordsDNSSEC
2026-11-19 17:22:33 671ms 5 NS 1 A 3 MX Insecure
2026-11-13 00:52:28 496ms 5 NS 1 A 3 MX Insecure
2026-11-05 22:15:17 794ms 5 NS 1 A 3 MX Insecure
2026-10-29 08:12:40 1512ms 5 NS 1 A 3 MX Insecure
2026-10-25 09:05:58 2240ms 5 NS 1 A 3 MX Insecure
2026-10-15 21:53:54 1256ms 5 NS 1 A 3 MX Insecure
2026-10-08 10:53:06 999ms 5 NS 1 A 3 MX Insecure
2026-10-01 12:49:49 527ms 5 NS 1 A 3 MX Insecure
2026-09-30 12:47:24 598ms 5 NS 1 A 3 MX Insecure
2026-09-24 18:16:51 772ms 5 NS 1 A 3 MX Insecure
2026-09-17 22:44:31 845ms 5 NS 1 A 3 MX Insecure
2026-09-10 09:07:44 802ms 5 NS 1 A 3 MX Insecure
2026-09-03 19:28:19 675ms 5 NS 1 A 3 MX Insecure
2026-08-27 09:50:07 857ms 5 NS 1 A 3 MX Insecure
2026-08-26 09:49:20 1011ms 5 NS 1 A 3 MX Insecure
2026-08-25 22:26:16 893ms 5 NS 1 A 3 MX Insecure
2026-08-20 18:35:37 9073ms 5 NS 1 A 3 MX Insecure
2026-08-13 15:20:49 1181ms 5 NS 1 A 3 MX Insecure
2026-08-08 06:43:57 1254ms 5 NS 1 A 3 MX Insecure
2026-08-03 08:57:09 1426ms 5 NS 1 A 3 MX Insecure
2026-07-23 22:57:34 1768ms 5 NS 1 A 3 MX Insecure
2026-07-16 06:16:20 1053ms 5 NS 1 A 3 MX Insecure
2026-07-10 02:29:51 967ms 5 NS 1 A 3 MX Insecure
2026-07-03 15:30:19 4380ms 5 NS 1 A 3 MX Insecure
2026-06-26 02:46:14 890ms 5 NS 1 A 3 MX Insecure