straight-up.dk

📜 Historical scan 2026-07-04 06:38:52 · ← Latest scan

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

straight-up.dk is a registered .dk domain whose nameservers (ns1.123hjemmeside.dk, ns2.123hjemmeside.dk) do not answer for it, so it is currently a lame delegation and does not resolve. It was registered on 25 November 2011 (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 2215ms

Nameserver	IP addresses	PTR	ASN / ISP
ns1.123hjemmeside.dk	52.51.2.215	ec2-52-51-2-215.eu-west-1.compute.amazonaws.com	AS16509 Amazon.com, Inc.
ns2.123hjemmeside.dk	52.200.246.146	ec2-52-200-246-146.compute-1.amazonaws.com	AS14618 Amazon.com, 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#

1556ms

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-20 04:34:43

Field	Value
Registrar	Punktum dk A/S (direct)
Registered	2011-11-25
Expires	2026-11-30 (37d)

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

2215ms

2202ms

2179ms

AAAA

200ms

TXT

500ms

CAA

197ms

HTTPS

2204ms

TLSA

78ms

SOA

199ms

MTA-STS

209ms

DNSSEC

1556ms

SRV

210ms

Total

23405ms

🕐 Scan History#

Scanned At	Duration	Records	DNSSEC
2026-10-22 01:05:59	64957ms	2 NS 0 A 0 MX	❓ Unknown
2026-10-03 07:54:40	60889ms	2 NS 0 A 0 MX	❓ Unknown
2026-09-27 07:45:24	63148ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-23 19:07:00	61981ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-22 12:58:49	59335ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-21 12:36:35	61875ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-20 11:50:58	53968ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-19 06:19:53	65535ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-18 03:40:29	63384ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-15 20:07:42	58443ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-11 23:00:54	60628ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-10 10:43:14	65535ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-09 06:00:17	61502ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-08 00:30:07	65535ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-04 11:26:59	65535ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-27 10:03:03	63397ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-26 09:50:28	61215ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-25 09:16:33	65535ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-24 08:47:12	65535ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-23 06:46:24	61345ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-22 05:17:02	61398ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-21 04:07:04	65535ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-20 03:40:52	65535ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-19 02:35:47	65535ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-17 21:27:36	58812ms	2 NS 0 A 0 MX	❓ Unknown