nst-service.dk

📜 Historical scan 2026-07-13 08:13:01 · ← Latest scan

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

nst-service.dk is a registered .dk domain whose nameservers (ns1.codex-design.com, ns2.codex-design.com) do not answer for it, so it is currently a lame delegation and does not resolve. It was registered on 2 June 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#

2 records 32ms

Nameserver	IP addresses	PTR	ASN / ISP
ns1.codex-design.com	212.172.50.138	vs-88.webhoster.ag	AS12312 ecotel communication ag
ns2.codex-design.com	212.172.50.138	vs-88.webhoster.ag	AS12312 ecotel communication ag

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

1593ms

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-22 10:08:02

Field	Value
Registrar	Punktum dk A/S (direct)
Registered	2014-06-02
Expires	2027-06-30 (250d)

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

32ms

83ms

71ms

AAAA

64ms

TXT

2827ms

CAA

1572ms

HTTPS

1572ms

TLSA

59ms

SOA

17ms

MTA-STS

2407ms

DNSSEC

1593ms

SRV

16063ms

Total

19673ms

🕐 Scan History#

Scanned At	Duration	Records	DNSSEC
2026-10-09 04:43:13	30205ms	2 NS 0 A 0 MX	❓ Unknown
2026-09-20 22:31:07	32051ms	2 NS 0 A 0 MX	❓ Unknown
2026-09-06 20:01:13	31468ms	2 NS 0 A 0 MX	❓ Unknown
2026-09-02 11:36:12	27001ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-23 07:33:22	32131ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-22 07:24:18	36088ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-21 07:17:52	28354ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-20 05:29:05	30432ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-19 03:08:35	30596ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-17 22:27:21	29014ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-16 22:10:14	29305ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-15 01:43:03	28631ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-13 06:15:34	22981ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-10 23:04:50	37745ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-07 15:06:33	26253ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-05 03:01:01	21631ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-28 11:59:17	28490ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-27 06:01:10	36694ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-26 05:26:29	27956ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-25 05:13:41	25984ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-24 04:24:47	30635ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-23 00:42:45	26313ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-21 16:06:21	27800ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-20 03:06:04	27959ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-18 22:01:52	28229ms	2 NS 0 A 0 MX	❓ Unknown