flowervisiondirect.dk

📜 Historical scan 2026-07-21 23:18:25 · ← Latest scan

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

flowervisiondirect.dk is a registered .dk domain whose nameservers (ns1.dn-s.nl, ns2.dn-s.nl) do not answer for it, so it is currently a lame delegation and does not resolve. It was registered on 4 October 2019 (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 320ms

Nameserver	IP addresses	PTR	ASN / ISP
ns1.dn-s.nl	185.104.28.19 2a06:2ec0:1::10	ns1.zxcs.nl ns1.zxcs.nl	AS206281 Stichting DIGI NL AS206281 Stichting DIGI NL
ns2.dn-s.nl	2a03:b0c0:3:d0::116:2001 46.101.179.64	ns2.zxcs.nl ns2.zxcs.nl	AS14061 DigitalOcean, LLC AS14061 DigitalOcean, 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#

361ms

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-21 08:16:38

Field	Value
Registrar	Key-Systems GmbH
Registered	2019-10-04
Expires	2026-10-31 (10d)

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

320ms

317ms

339ms

AAAA

320ms

TXT

1619ms

CAA

319ms

HTTPS

321ms

TLSA

266ms

SOA

22ms

MTA-STS

296ms

DNSSEC

361ms

SRV

538ms

Total

5188ms

🕐 Scan History#

Scanned At	Duration	Records	DNSSEC
2026-09-30 01:07:09	3214ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-24 11:14:39	5934ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-23 09:05:51	5617ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-22 08:38:29	9636ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-21 08:23:47	12613ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-20 07:42:22	16662ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-19 06:10:59	5580ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-16 05:41:55	15261ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-12 18:57:55	9114ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-11 08:34:43	7662ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-06 19:59:44	11563ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-02 03:12:41	2370ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-30 02:03:59	11680ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-27 12:37:46	13124ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-26 12:20:04	2633ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-25 11:41:32	11162ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-24 10:06:39	7292ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-23 07:47:26	13079ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-21 23:18:25 shown	5188ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-20 11:36:37	2523ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-19 06:50:54	9113ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-18 06:10:25	8128ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-16 12:06:18	9022ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-11 15:57:14	10776ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-09 16:01:22	8134ms	2 NS 0 A 0 MX	❓ Unknown