love2match.dk

📜 Historical scan 2026-08-21 16:22:13 · ← Latest scan

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

love2match.dk is a registered .dk domain whose nameservers (ns1.proisp.no, ns2.proisp.no) do not answer for it, so it is currently a lame delegation and does not resolve. It was registered on 29 October 2016 (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 112ms

Nameserver	IP addresses	PTR	ASN / ISP
ns1.proisp.no	2001:41d0:203:6419:: 51.91.130.25	ns1.proisp.no ns1.proisp.no	AS16276 OVH SAS AS16276 OVH SAS
ns2.proisp.no	168.119.69.108 2400:cb00:2049:1::a29f:198a	ns2.proisp.no ns2.proisp.no	AS24940 Hetzner Online GmbH AS13335 Cloudflare, Inc.

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

625ms

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-16 09:24:11

Field	Value
Registrar	Punktum dk A/S (direct)
Registered	2016-10-29
Expires	2026-10-31 (14d)

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

112ms

2076ms

1104ms

AAAA

81ms

TXT

4543ms

CAA

117ms

HTTPS

2107ms

TLSA

103ms

SOA

61ms

MTA-STS

191ms

DNSSEC

625ms

SRV

468ms

Total

6798ms

🕐 Scan History#

Scanned At	Duration	Records	DNSSEC
2026-10-03 08:12:20	24166ms	2 NS 0 A 0 MX	❓ Unknown
2026-09-30 19:34:02	3557ms	2 NS 0 A 0 MX	❓ Unknown
2026-09-24 09:11:48	11469ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-23 17:31:52	11650ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-22 16:35:54	5360ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-21 16:22:13 shown	6798ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-20 16:17:14	11509ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-19 11:36:10	11591ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-18 11:33:55	6956ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-15 23:43:47	6950ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-14 19:01:17	3869ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-13 17:02:20	4025ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-11 05:27:04	5903ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-10 02:10:43	7494ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-07 11:37:45	3849ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-29 14:18:30	26059ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-27 09:03:19	11523ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-26 08:51:43	2856ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-25 08:28:04	2288ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-24 08:19:38	3685ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-23 05:21:07	3763ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-22 03:57:21	6711ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-21 00:40:48	2000ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-19 07:50:54	2371ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-18 07:37:30	2104ms	2 NS 0 A 0 MX	❓ Unknown