richmeetbeautiful.dk

📜 Historical scan 2026-08-15 22:56:40 · ← Latest scan

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

richmeetbeautiful.dk is a registered .dk domain whose nameservers (ns.fastname.no, ns2.fastname.no) do not answer for it, so it is currently a lame delegation and does not resolve. It was registered on 3 April 2013 (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 533ms

Nameserver	IP addresses	PTR	ASN / ISP
ns.fastname.no	195.206.121.12 2001:67c:28cc::12	ns01.no.brand.one.com ns01.no.brand.one.com	AS197495 One.com A/S AS197495 One.com A/S
ns2.fastname.no	185.10.11.12 2001:67c:3c0::12	ns02.no.brand.one.com ns02.no.brand.one.com	AS51468 One.com A/S AS51468 One.com 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

🔗 TLSA / DANE#

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

🔐 DNSSEC#

770ms

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-12 07:27:47

Field	Value
Registrar	Punktum dk A/S (direct)
Registered	2013-04-03
Expires	2027-04-30 (191d)

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

533ms

653ms

638ms

AAAA

536ms

TXT

1271ms

CAA

530ms

HTTPS

559ms

TLSA

243ms

SOA

427ms

MTA-STS

597ms

DNSSEC

770ms

SRV

625ms

Total

4044ms

🕐 Scan History#

Scanned At	Duration	Records	DNSSEC
2026-10-01 01:19:12	1399ms	2 NS 0 A 0 MX	❓ Unknown
2026-09-20 23:32:25	31276ms	2 NS 0 A 0 MX	❓ Unknown
2026-09-09 13:01:37	10415ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-23 18:01:34	27433ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-22 17:36:31	1747ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-21 17:20:02	1289ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-20 17:10:46	10179ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-19 16:12:21	10110ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-18 16:05:40	4206ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-17 13:08:26	2997ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-15 22:56:40 shown	4044ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-13 21:56:37	3487ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-12 16:53:37	10231ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-10 11:14:09	1148ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-09 07:19:31	1477ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-07 16:50:26	1252ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-01 13:07:09	944ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-29 06:22:07	2969ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-27 14:10:58	1055ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-26 13:36:15	870ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-25 13:11:04	996ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-24 13:06:56	853ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-23 12:29:04	17029ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-22 09:12:05	897ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-20 18:11:04	1821ms	2 NS 0 A 0 MX	❓ Unknown