bysophy.dk

📜 Historical scan 2026-08-01 07:43:28 · ← Latest scan

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

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

3 records 201ms

Nameserver	IP addresses	PTR	ASN / ISP
ns1.speedbox.dk	94.130.138.185	ns1.azehosting.net	AS24940 Hetzner Online GmbH
ns2.speedbox.dk	88.99.15.5	ns2.azehosting.net	AS24940 Hetzner Online GmbH
ns3.speedbox.dk	—	—	—

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

341ms

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 02:55:17

Field	Value
Registrar	Punktum dk A/S (direct)
Registered	2019-11-03
Expires	2026-11-30 (40d)

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

201ms

268ms

201ms

AAAA

268ms

TXT

757ms

CAA

199ms

HTTPS

261ms

TLSA

265ms

SOA

32ms

MTA-STS

246ms

DNSSEC

341ms

SRV

668ms

Total

2398ms

🕐 Scan History#

Scanned At	Duration	Records	DNSSEC
2026-09-25 13:53:01	51992ms	3 NS 0 A 0 MX	❓ Unknown
2026-09-01 12:46:18	52544ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-23 07:30:13	10621ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-22 07:01:06	4718ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-21 06:28:19	22018ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-20 04:48:19	6845ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-19 03:36:02	6498ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-18 01:28:31	11222ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-16 19:59:46	4981ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-15 03:43:24	7101ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-13 04:41:14	12747ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-11 04:35:53	1966ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-09 02:28:27	2064ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-07 04:34:55	1979ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-01 07:43:28 shown	2398ms	3 NS 0 A 0 MX	❓ Unknown
2026-07-28 10:47:36	4910ms	3 NS 0 A 0 MX	❓ Unknown
2026-07-27 10:25:19	3046ms	3 NS 0 A 0 MX	❓ Unknown
2026-07-26 09:29:34	2430ms	3 NS 0 A 0 MX	❓ Unknown
2026-07-25 09:12:28	10351ms	3 NS 0 A 0 MX	❓ Unknown
2026-07-24 08:35:47	19323ms	3 NS 0 A 0 MX	❓ Unknown
2026-07-22 23:37:13	9905ms	3 NS 0 A 0 MX	❓ Unknown
2026-07-21 09:49:04	6436ms	3 NS 0 A 0 MX	❓ Unknown
2026-07-19 16:25:59	13581ms	3 NS 0 A 0 MX	❓ Unknown
2026-07-18 10:41:22	19648ms	3 NS 0 A 0 MX	❓ Unknown
2026-07-13 18:04:50	3758ms	3 NS 0 A 0 MX	❓ Unknown