slemm.dk

📜 Historical scan 2026-08-19 02:59:18 · ← Latest scan

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

slemm.dk is a registered .dk domain whose nameservers (ns1.simply.com, ns2.simply.com, ns3.simply.com) do not answer for it, so it is currently a lame delegation and does not resolve. It was registered on 3 August 2025 (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#

3 records 513ms

Nameserver	IP addresses	PTR	ASN / ISP
ns1.simply.com	2a02:2339:1:15c::4562:4562 91.197.248.78	ns1.simply.com ns1.simply.com	AS48854 team.blue Denmark A/S AS48854 team.blue Denmark A/S
ns2.simply.com	185.25.141.15 2a02:2339:4006:101::4562:4562	ns2.simply.com ns2.simply.com	AS48854 team.blue Denmark A/S AS48854 team.blue Denmark A/S
ns3.simply.com	91.197.248.79	ns3.simply.com	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-09 10:10:36

www	93.191.156.76 (AS48854) (address records, no CNAME)
www vs bare domain	Same network slemm.dk: 93.191.156.76 (AS48854) www.slemm.dk: 93.191.156.76 (AS48854)
Wildcard	Yes: any name under the zone resolves
Denial of existence	NSEC zone can be walked (all names enumerable)
CDS / CDNSKEY	Published: key rollovers can be automated with the registry (RFC 7344/8078) 1 CDS, 1 CDNSKEY

🔗 TLSA / DANE#

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

🔐 DNSSEC#

769ms

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-03 02:28:28

Field	Value
Registrar	Simply.com A/S
Registered	2025-08-03
Expires	2027-08-02 (287d)

📋 WHOIS#

⏱️ Lookup Timing#

513ms

517ms

521ms

AAAA

513ms

TXT

1795ms

CAA

541ms

HTTPS

565ms

TLSA

318ms

SOA

367ms

MTA-STS

527ms

DNSSEC

769ms

SRV

607ms

Total

6964ms

🕐 Scan History#

Scanned At	Duration	Records	DNSSEC
2026-10-03 01:56:40	538ms	3 NS 1 A 1 MX	🔒 Secure
2026-09-14 15:48:20	602ms	3 NS 1 A 1 MX	🔒 Secure
2026-08-27 02:14:08	832ms	3 NS 1 A 1 MX	🔒 Secure
2026-08-26 20:00:38	499ms	3 NS 1 A 1 MX	🔒 Secure
2026-08-23 18:28:52	3172ms	3 NS 0 A 0 MX	⚠️ Bogus
2026-08-22 14:23:54	5699ms	3 NS 0 A 0 MX	⚠️ Bogus
2026-08-21 14:04:10	10288ms	3 NS 0 A 0 MX	⚠️ Bogus
2026-08-20 13:58:51	8906ms	3 NS 0 A 0 MX	⚠️ Bogus
2026-08-19 02:59:18 shown	6964ms	3 NS 0 A 0 MX	⚠️ Bogus
2026-08-17 21:55:59	10139ms	3 NS 0 A 0 MX	⚠️ Bogus
2026-08-16 15:37:46	8928ms	3 NS 0 A 0 MX	⚠️ Bogus
2026-08-15 14:12:47	10195ms	3 NS 0 A 0 MX	⚠️ Bogus
2026-08-14 11:57:32	3095ms	3 NS 0 A 0 MX	⚠️ Bogus
2026-08-12 15:27:43	10037ms	3 NS 0 A 0 MX	⚠️ Bogus
2026-08-11 01:13:23	10204ms	3 NS 0 A 0 MX	⚠️ Bogus
2026-08-09 19:25:04	3606ms	3 NS 0 A 0 MX	⚠️ Bogus
2026-08-06 02:24:00	1627ms	3 NS 0 A 0 MX	⚠️ Bogus
2026-06-30 07:43:11	661ms	3 NS 1 A 1 MX	🔒 Secure
2026-06-26 07:25:06	640ms	3 NS 1 A 1 MX	🔒 Secure
2026-06-17 20:03:51	583ms	3 NS 1 A 1 MX	🔒 Secure