bigbang.dk

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

bigbang.dk is a .dk domain with no delegation in this scan. It was registered on 4 June 1998 (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-12 19:41:07
www CNAMEbigbang.dk (all on bigbang.dk)
www vs bare domainSame network
bigbang.dk: 46.183.138.100 (AS47292)
www.bigbang.dk: 46.183.138.100 (AS47292)
WildcardYes: any name under the zone resolves

DKIM keys#

1 found
SelectorCNAMEKey
default bigbang.dk RSA Invalid key data — receivers can't verify signatures

DKIM selectors can't be listed, so we check the common ones (Microsoft 365, Google, Mailchimp, SendGrid, generic). Keys under other selectors aren't shown.

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-02 11:51:46
FieldValue
RegistrarGIGAHOST ApS
Registered1998-06-04
Expires2027-06-30 (223d)

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
188ms
A
176ms
MX
180ms
AAAA
199ms
TXT
297ms
CAA
204ms
HTTPS
183ms
TLSA
17ms
SOA
177ms
MTA-STS
203ms
DNSSEC
292ms
SRV
221ms
Total
954ms

Scan History#

Scanned AtDurationRecordsDNSSEC
2026-11-12 19:41:07 1518ms 5 NS 1 A 4 MX Insecure
2026-11-06 01:53:42 2569ms 5 NS 1 A 4 MX Insecure
2026-11-06 01:51:43 1211ms 5 NS 1 A 4 MX Insecure
2026-11-02 12:37:38 1608ms 5 NS 1 A 4 MX Insecure
2026-10-30 22:02:38 1905ms 5 NS 1 A 4 MX Insecure
2026-10-29 10:28:53 1210ms 5 NS 1 A 4 MX Insecure
2026-10-25 18:46:30 964ms 5 NS 1 A 4 MX Insecure
2026-10-23 12:54:36 1016ms 5 NS 1 A 4 MX Insecure
2026-10-22 07:23:17 2986ms 5 NS 1 A 4 MX Insecure
2026-10-19 17:40:45 1585ms 5 NS 1 A 4 MX Insecure
2026-10-18 16:36:11 1626ms 5 NS 1 A 4 MX Insecure
2026-10-15 13:55:46 1245ms 5 NS 1 A 4 MX Insecure
2026-10-08 03:03:17 4900ms 5 NS 1 A 4 MX Insecure
2026-10-01 23:51:27 1207ms 5 NS 1 A 4 MX Insecure
2026-09-24 22:19:32 1041ms 5 NS 1 A 4 MX Insecure
2026-09-18 12:30:27 1492ms 5 NS 1 A 4 MX Insecure
2026-09-16 01:54:34 1764ms 5 NS 1 A 4 MX Insecure
2026-09-04 04:52:53 1296ms 5 NS 1 A 4 MX Insecure
2026-08-27 03:56:08 2994ms 5 NS 1 A 4 MX Insecure
2026-08-20 03:53:43 3359ms 5 NS 1 A 4 MX Insecure
2026-08-14 02:23:06 5302ms 5 NS 1 A 4 MX Insecure
2026-08-08 07:34:09 2549ms 5 NS 1 A 4 MX Insecure
2026-07-31 08:41:57 1996ms 5 NS 1 A 4 MX Insecure
2026-07-23 07:57:25 2034ms 5 NS 1 A 4 MX Unknown
2026-07-16 09:15:05 9610ms 5 NS 1 A 4 MX Unknown