brondbycupdenmark.dk

Historical scan 2026-06-23 13:33:06  ·  ← Latest scan
Zone File Timeline & History Scan Now

brondbycupdenmark.dk is a .dk domain with no delegation in this scan. It was registered on 5 May 2021 (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 02:32:31
www CNAMEbrondbycupdenmark.dk (all on brondbycupdenmark.dk)
www vs bare domainSame network
brondbycupdenmark.dk: 46.183.138.100 (AS47292)
www.brondbycupdenmark.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#

265ms
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-05 01:19:10
FieldValue
RegistrarGIGAHOST ApS
Registered2021-05-05
Expires2027-05-31 (192d)

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
183ms
A
132ms
MX
191ms
AAAA
208ms
TXT
317ms
CAA
150ms
HTTPS
225ms
TLSA
17ms
SOA
228ms
MTA-STS
170ms
DNSSEC
265ms
SRV
243ms
Total
987ms

Scan History#

Scanned AtDurationRecordsDNSSEC
2026-11-19 02:32:30 2179ms 5 NS 1 A 3 MX Insecure
2026-11-12 18:21:44 620ms 5 NS 1 A 3 MX Insecure
2026-11-05 01:16:51 2420ms 5 NS 1 A 3 MX Insecure
2026-10-30 08:06:15 764ms 5 NS 1 A 3 MX Insecure
2026-10-26 06:38:01 795ms 5 NS 1 A 3 MX Insecure
2026-10-25 01:29:55 1567ms 5 NS 1 A 3 MX Insecure
2026-10-22 17:06:28 2082ms 5 NS 1 A 3 MX Insecure
2026-10-15 12:46:57 782ms 5 NS 1 A 3 MX Insecure
2026-10-15 12:25:55 742ms 5 NS 1 A 3 MX Insecure
2026-10-08 23:33:41 3411ms 5 NS 1 A 3 MX Insecure
2026-10-01 22:11:45 1027ms 5 NS 1 A 3 MX Insecure
2026-09-30 22:05:35 1121ms 5 NS 1 A 3 MX Insecure
2026-09-24 20:32:58 837ms 5 NS 1 A 3 MX Insecure
2026-09-23 19:38:37 1727ms 5 NS 1 A 3 MX Insecure
2026-09-21 20:49:28 794ms 5 NS 1 A 3 MX Insecure
2026-09-12 19:45:29 1349ms 5 NS 1 A 3 MX Insecure
2026-09-05 18:56:14 1100ms 5 NS 1 A 3 MX Insecure
2026-08-28 04:21:29 774ms 5 NS 1 A 3 MX Insecure
2026-08-26 00:24:08 9580ms 5 NS 1 A 3 MX Insecure
2026-08-20 11:54:42 6056ms 5 NS 1 A 3 MX Insecure
2026-08-13 06:27:08 3969ms 5 NS 1 A 3 MX Insecure
2026-08-07 04:00:59 2198ms 5 NS 1 A 3 MX Insecure
2026-07-30 08:27:15 14101ms 5 NS 1 A 3 MX Insecure
2026-07-23 17:13:46 8967ms 5 NS 1 A 3 MX Insecure
2026-07-16 22:36:41 9357ms 5 NS 1 A 3 MX Insecure