allergy.dk

📜 Historical scan 2026-07-08 20:50:09 · ← Latest scan

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

allergy.dk is a registered .dk domain whose nameservers (authns1.webpartner.dk, authns2.webpartner.dk) do not answer for it, so it is currently a lame delegation and does not resolve. It 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 6029ms

Nameserver	IP addresses	PTR	ASN / ISP
authns1.webpartner.dk	213.150.60.234 2a01:3a0:53:4::1	authns1.webpartner.dk authns1.webpartner.dk	AS3308 Norlys Telco A/S AS3308 Norlys Telco A/S
authns2.webpartner.dk	195.184.108.10 2a01:3a0:53:5::1	authns2.webpartner.dk authns2.webpartner.dk	AS3308 Norlys Telco A/S AS3308 Norlys Telco 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

🔗 TLSA / DANE#

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

🔐 DNSSEC#

2117ms

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#

✗ No registration data yet — queued for a WHOIS lookup

📋 WHOIS#

⏱️ Lookup Timing#

6029ms

2042ms

4051ms

AAAA

2023ms

TXT

29368ms

CAA

6027ms

HTTPS

2035ms

TLSA

16035ms

SOA

23ms

MTA-STS

16046ms

DNSSEC

2117ms

SRV

16046ms

Total

65535ms

🕐 Scan History#

Scanned At	Duration	Records	DNSSEC
2026-09-30 16:37:50	65535ms	2 NS 0 A 0 MX	❓ Unknown
2026-09-07 00:31:18	65535ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-28 00:06:55	63661ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-24 10:08:43	65535ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-23 06:17:12	65535ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-22 06:07:01	65535ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-21 05:49:20	65535ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-20 05:16:45	55349ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-19 04:02:23	65535ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-18 03:04:08	65535ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-16 22:59:02	65535ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-15 01:19:32	64562ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-13 22:53:27	64548ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-10 21:04:10	65153ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-09 13:59:14	61464ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-07 11:19:35	60082ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-04 03:35:59	65535ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-29 11:39:00	63273ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-28 06:31:37	57361ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-27 05:16:28	65535ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-26 04:34:55	59251ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-25 04:26:01	65535ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-24 03:15:35	65535ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-23 00:38:37	59294ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-22 00:23:17	65535ms	2 NS 0 A 0 MX	❓ Unknown