nextpay.dk

📜 Historical scan 2026-07-02 22:46:00 · ← Latest scan

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

nextpay.dk is a registered .dk domain whose nameservers (ns.dandomain.dk, ns2.dandomain.dk) do not answer for it, so it is currently a lame delegation and does not resolve. It was registered on 27 August 2026 (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 369ms

Nameserver	IP addresses	PTR	ASN / ISP
ns.dandomain.dk	185.25.141.3 2a02:2339:4006:109::dd	ns.dandomain.dk ns.dandomain.dk	AS48854 team.blue Denmark A/S AS48854 team.blue Denmark A/S
ns2.dandomain.dk	2a02:2339:1:108::dd:dd 91.197.248.66	ns2.dandomain.dk ns2.dandomain.dk	AS48854 team.blue Denmark A/S AS48854 team.blue Denmark A/S

🌍 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-10-11 22:55:23

www CNAME	nextpay.dk (all on nextpay.dk) → 44.232.173.249 52.40.42.113 (AS16509)
www vs bare domain	Same network nextpay.dk: 44.232.173.249 52.40.42.113 (AS16509) www.nextpay.dk: 44.232.173.249 52.40.42.113 (AS16509)
Wildcard	No

🔗 TLSA / DANE#

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

🔐 DNSSEC#

2360ms

Check	Result
Validation Status	⚠️ Bogus — the parent still publishes a DS record, but the delegated nameservers don't answer, so no signed answer can be fetched. The zone isn't serving broken signatures; it isn't serving at all.
AD Flag (resolver validates)	✗ Not set
DS Record	✓ Found
DNSKEY Record	✗ Not found
Flags	resolution failed: failure

🏷️ SOA#

✗ No SOA record found

📋 Registration#

WHOIS fetched 2026-10-07 01:50:05

Field	Value
Registrar	Dynadot LLC
Registered	2026-08-27
Expires	2027-08-26 (309d)

📋 WHOIS#

⏱️ Lookup Timing#

369ms

332ms

394ms

AAAA

362ms

TXT

1553ms

CAA

350ms

HTTPS

394ms

TLSA

165ms

SOA

384ms

MTA-STS

431ms

DNSSEC

2360ms

SRV

407ms

Total

6881ms

🕐 Scan History#

Scanned At	Duration	Records	DNSSEC
2026-09-25 09:46:37	1366ms	2 NS 2 A 0 MX	🔓 Insecure
2026-09-04 08:55:08	2520ms	2 NS 2 A 0 MX	🔓 Insecure
2026-08-28 08:36:55	2548ms	2 NS 3 A 0 MX	🔓 Insecure
2026-08-25 18:34:26	290ms	1 NS 0 A 0 MX	❓ Unknown
2026-08-24 14:26:34	313ms	1 NS 0 A 0 MX	❓ Unknown
2026-08-23 06:13:43	2747ms	1 NS 0 A 0 MX	❓ Unknown
2026-08-22 06:02:34	3708ms	1 NS 0 A 0 MX	❓ Unknown
2026-08-21 05:39:56	1750ms	1 NS 0 A 0 MX	❓ Unknown
2026-08-20 03:33:54	778ms	1 NS 0 A 0 MX	❓ Unknown
2026-08-19 03:20:49	5095ms	1 NS 0 A 0 MX	❓ Unknown
2026-08-17 12:09:21	780ms	1 NS 0 A 0 MX	❓ Unknown
2026-08-16 10:33:50	2536ms	1 NS 0 A 0 MX	❓ Unknown
2026-08-14 20:00:22	806ms	1 NS 0 A 0 MX	❓ Unknown
2026-08-13 17:20:36	3448ms	1 NS 0 A 0 MX	❓ Unknown
2026-08-12 05:10:50	2325ms	1 NS 0 A 0 MX	❓ Unknown
2026-08-10 20:08:39	625ms	1 NS 0 A 0 MX	❓ Unknown
2026-08-09 15:37:09	2915ms	1 NS 0 A 0 MX	❓ Unknown
2026-08-07 09:43:56	803ms	1 NS 0 A 0 MX	❓ Unknown
2026-08-03 07:34:27	8737ms	1 NS 0 A 0 MX	❓ Unknown
2026-07-31 21:04:02	877ms	1 NS 0 A 0 MX	❓ Unknown
2026-07-27 22:52:39	680ms	1 NS 0 A 0 MX	❓ Unknown
2026-07-26 22:26:04	742ms	1 NS 0 A 0 MX	❓ Unknown
2026-07-25 21:57:44	1145ms	2 NS 0 A 0 MX	⚠️ Bogus
2026-07-24 21:22:13	9867ms	2 NS 0 A 0 MX	⚠️ Bogus
2026-07-23 20:06:33	1325ms	2 NS 0 A 0 MX	⚠️ Bogus