acubalance.dk

📜 Historical scan 2026-08-07 16:03:50 · ← Latest scan

🧟 Lame delegation ⬇ Zone File 📜 Timeline & History ⚡ Scan Now

acubalance.dk is a registered .dk domain whose nameservers (ns1.dns-123.net, ns2.dns-123.net, ns3.dns-123.net) do not answer for it, so it is currently a lame delegation and does not resolve. It was registered on 8 September 2014 (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#

3 records 680ms

Nameserver	IP addresses	PTR	ASN / ISP
ns1.dns-123.net	35.198.132.83	83.132.198.35.bc.googleusercontent.com	AS396982 Google LLC
ns2.dns-123.net	35.187.184.173	173.184.187.35.bc.googleusercontent.com	AS396982 Google LLC
ns3.dns-123.net	35.228.54.1	1.54.228.35.bc.googleusercontent.com	AS396982 Google LLC

🌍 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

🔗 TLSA / DANE#

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

🔐 DNSSEC#

751ms

Check	Result
Validation Status	❓ Unknown (the delegated nameservers don't answer)
AD Flag (resolver validates)	✗ Not set
DS Record	✗ Not found
DNSKEY Record	✗ Not found
Flags	resolution failed: failure

🏷️ SOA#

✗ No SOA record found

📋 Registration#

WHOIS fetched 2026-10-11 16:53:06

Field	Value
Registrar	Punktum dk A/S (direct)
Registered	2014-09-08
Expires	2027-09-30 (348d)

🔗 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#

680ms

677ms

750ms

AAAA

667ms

TXT

3271ms

CAA

678ms

HTTPS

681ms

TLSA

642ms

SOA

31ms

MTA-STS

779ms

DNSSEC

751ms

SRV

744ms

Total

5825ms

🕐 Scan History#

Scanned At	Duration	Records	DNSSEC
2026-08-23 06:17:58	9656ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-22 06:07:05	3631ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-21 05:57:16	2361ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-20 04:56:15	8907ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-19 04:05:38	4279ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-18 02:23:34	2148ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-17 01:37:01	2099ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-15 23:48:50	7876ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-13 06:28:05	7025ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-11 17:37:19	12847ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-10 14:38:49	9042ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-07 16:03:50 shown	5825ms	3 NS 0 A 0 MX	❓ Unknown
2026-07-31 10:45:56	7180ms	3 NS 0 A 0 MX	❓ Unknown
2026-07-29 10:13:48	5696ms	3 NS 0 A 0 MX	❓ Unknown
2026-07-28 06:56:58	20060ms	3 NS 0 A 0 MX	❓ Unknown
2026-07-27 05:12:39	12571ms	3 NS 0 A 0 MX	❓ Unknown
2026-07-26 04:30:30	21920ms	3 NS 0 A 0 MX	❓ Unknown
2026-07-25 04:15:08	25371ms	3 NS 0 A 0 MX	❓ Unknown
2026-07-24 03:56:00	36213ms	3 NS 0 A 0 MX	❓ Unknown
2026-07-23 03:36:08	12451ms	3 NS 0 A 0 MX	❓ Unknown
2026-07-21 15:31:24	26546ms	3 NS 0 A 0 MX	❓ Unknown
2026-07-20 13:57:48	6501ms	3 NS 0 A 0 MX	❓ Unknown
2026-07-19 11:54:12	25817ms	3 NS 0 A 0 MX	❓ Unknown
2026-07-18 06:21:03	27070ms	3 NS 0 A 0 MX	❓ Unknown
2026-07-17 05:54:27	42374ms	3 NS 0 A 0 MX	❓ Unknown