floodle.dk

📜 Historical scan 2026-06-19 09:07:46 · ← Latest scan

⬇ Zone File 📜 Timeline & History ⚡ Scan Now

floodle.dk is a .dk domain with no delegation in this scan. It was registered on 28 August 2024 (WHOIS) and was already in the .dk zone when our tracking began on 16 June 2026. Mail is handled by localhost. 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#

🖥️

No NS records found

🌍 A Records#

1 records 112ms

IP	TTL	PTR	ASN	ISP / Org	CIDR	Country	City
127.0.0.1	600s	localhost	—	—	—	—	—

📧 MX Records#

1 records 143ms

Priority	TTL	Mail Server	IP addresses	PTR	ASN
0	600s	localhost	::1 127.0.0.1	localhost localhost	— —

📧 Autodiscover / Autoconfig#

Service	CNAME / IP
🔷 Autodiscover	127.0.0.1
🔶 Autoconfig	127.0.0.1

🔷 AAAA Records (IPv6)#

1 records 99ms

IPv6 Address	TTL	PTR	ASN	ISP / Org	CIDR	Country	City
::1	600s	localhost	—	—	—	—	—

🔐 HTTPS Records#

✗ No HTTPS RR — no SVCB/HTTPS service binding

📝 TXT Records#

1 records 328ms

TXT Record
expired

✉️ 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#

115ms

Check	Result
Validation Status	Not applicable: the domain has no delegation, so there is no zone to validate (stored verdict: 🔓 Insecure).
AD Flag (resolver validates)	✗ Not set
DS Record	✗ Not found
DNSKEY Record	✗ Not found
Flags	unsigned answer

🏷️ SOA#

✗ No SOA record found

📋 Registration#

WHOIS fetched 2026-10-17 05:58:29

Field	Value
Registrar	Realtime Register B.V.
Registered	2024-08-28
Expires	2027-08-27 (311d)

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

67ms

112ms

143ms

AAAA

99ms

TXT

328ms

CAA

81ms

HTTPS

80ms

TLSA

72ms

SOA

118ms

MTA-STS

128ms

DNSSEC

115ms

SRV

286ms

Total

674ms

🕐 Scan History#

Scanned At	Duration	Records	DNSSEC
2026-10-01 05:38:10	1127ms	6 NS 1 A 1 MX	🔓 Insecure
2026-08-23 22:31:02	2591ms	6 NS 1 A 1 MX	🔓 Insecure
2026-08-22 17:00:34	7332ms	6 NS 1 A 1 MX	🔓 Insecure
2026-08-21 16:45:44	12468ms	6 NS 1 A 1 MX	🔓 Insecure
2026-08-20 16:39:56	14419ms	6 NS 1 A 1 MX	🔓 Insecure
2026-08-19 15:37:44	6751ms	6 NS 1 A 1 MX	🔓 Insecure
2026-08-18 15:34:34	2114ms	6 NS 1 A 1 MX	🔓 Insecure
2026-08-16 09:18:30	7513ms	6 NS 1 A 1 MX	🔓 Insecure
2026-08-14 21:59:14	9031ms	6 NS 1 A 1 MX	🔓 Insecure
2026-08-13 14:27:06	15545ms	6 NS 1 A 1 MX	🔓 Insecure
2026-08-12 00:51:16	9808ms	6 NS 1 A 1 MX	🔓 Insecure
2026-08-09 10:08:47	9610ms	6 NS 1 A 1 MX	🔓 Insecure
2026-08-06 21:58:49	1519ms	6 NS 1 A 1 MX	🔓 Insecure
2026-08-03 08:15:38	1703ms	6 NS 1 A 1 MX	🔓 Insecure
2026-08-01 23:38:49	9489ms	6 NS 1 A 1 MX	🔓 Insecure
2026-07-29 15:04:15	11156ms	6 NS 1 A 1 MX	🔓 Insecure
2026-07-28 00:14:38	1962ms	6 NS 1 A 1 MX	🔓 Insecure
2026-07-27 00:09:01	6861ms	6 NS 1 A 1 MX	🔓 Insecure
2026-07-25 23:41:33	1799ms	6 NS 1 A 1 MX	🔓 Insecure
2026-07-24 23:26:27	6751ms	6 NS 1 A 1 MX	🔓 Insecure
2026-07-23 21:33:32	10889ms	6 NS 1 A 1 MX	🔓 Insecure
2026-07-22 21:17:08	6789ms	6 NS 1 A 1 MX	🔓 Insecure
2026-07-21 12:55:37	17370ms	6 NS 1 A 1 MX	🔓 Insecure
2026-07-20 08:11:40	6876ms	6 NS 1 A 1 MX	🔓 Insecure
2026-07-19 07:52:01	17984ms	6 NS 1 A 1 MX	🔓 Insecure