copenhagenbrass.dk

Historical scan 2026-06-23 10:05:36  ·  ← Latest scan
Zone File Timeline & History Scan Now

copenhagenbrass.dk is a .dk domain with no delegation in this scan. It was registered on 3 February 2004 (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:20:24
www CNAMEcopenhagenbrass.dk (all on copenhagenbrass.dk)
www vs bare domainSame network
copenhagenbrass.dk: 46.183.138.100 (AS47292)
www.copenhagenbrass.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#

292ms
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-12 23:27:01
FieldValue
RegistrarGIGAHOST ApS
Registered2004-02-03
Expires2027-02-28 (100d)

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
186ms
A
204ms
MX
194ms
AAAA
172ms
TXT
280ms
CAA
181ms
HTTPS
172ms
TLSA
17ms
SOA
210ms
MTA-STS
198ms
DNSSEC
292ms
SRV
199ms
Total
982ms

Scan History#

Scanned AtDurationRecordsDNSSEC
2026-11-19 17:20:24 1640ms 5 NS 1 A 3 MX Insecure
2026-11-18 15:34:49 915ms 5 NS 1 A 3 MX Insecure
2026-11-12 23:26:01 655ms 5 NS 1 A 3 MX Insecure
2026-11-05 09:11:12 1486ms 5 NS 1 A 3 MX Insecure
2026-10-30 21:11:29 742ms 5 NS 1 A 3 MX Insecure
2026-10-23 04:49:36 1530ms 5 NS 1 A 3 MX Insecure
2026-10-15 12:03:45 1706ms 5 NS 1 A 3 MX Insecure
2026-10-12 07:42:36 909ms 5 NS 1 A 3 MX Insecure
2026-10-08 20:56:40 753ms 5 NS 1 A 3 MX Insecure
2026-10-02 18:59:17 771ms 5 NS 1 A 3 MX Insecure
2026-10-01 20:07:46 1145ms 5 NS 1 A 3 MX Insecure
2026-09-27 19:31:05 740ms 5 NS 1 A 3 MX Insecure
2026-09-24 16:44:05 963ms 5 NS 1 A 3 MX Insecure
2026-09-17 07:20:45 1032ms 5 NS 1 A 3 MX Insecure
2026-09-10 04:35:10 898ms 5 NS 1 A 3 MX Insecure
2026-09-07 18:48:47 727ms 5 NS 1 A 3 MX Insecure
2026-08-27 20:41:52 685ms 5 NS 1 A 3 MX Insecure
2026-08-20 06:09:18 1528ms 5 NS 1 A 3 MX Insecure
2026-08-14 01:24:26 2458ms 5 NS 1 A 3 MX Insecure
2026-08-07 15:05:06 1198ms 5 NS 1 A 3 MX Insecure
2026-07-31 19:44:36 1915ms 5 NS 1 A 3 MX Insecure
2026-07-23 21:34:04 10056ms 5 NS 1 A 3 MX Insecure
2026-07-17 02:10:33 1083ms 5 NS 1 A 3 MX Insecure
2026-07-12 01:57:49 9770ms 5 NS 1 A 3 MX Insecure
2026-07-03 16:17:03 1567ms 5 NS 1 A 3 MX Insecure