rtf.dk

Historical scan 2026-07-03 00:44:45  ·  ← Latest scan
Lame delegation Zone File Timeline & History Scan Now

rtf.dk is a registered .dk domain whose nameservers (ns01.one.com, ns02.one.com) do not answer for it, so it is currently a lame delegation and does not resolve. It was registered on 2 October 1997 (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   4285ms

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-11-05 12:59:04
www185.31.76.135 (AS47527) (address records, no CNAME)
www vs bare domainSame network
WildcardYes: any name under the zone resolves
CDS / CDNSKEYNone 0 CDS, 0 CDNSKEY

TLSA / DANE#

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

DNSSEC#

10491ms
CheckResult
Validation Status Unknown (the delegated nameservers don't answer)
AD Flag (resolver validates) Not set
DS Record Found
DNSKEY Record Not found
Flagsresolution failed: timed out

SOA#

No SOA record found

Registration#

WHOIS fetched 2026-11-05 13:14:30
FieldValue
RegistrarCURANET A/S
Registered1997-10-02
Expires2026-12-31 (42d)

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#

NS
4285ms
A
4232ms
MX
4234ms
AAAA
4250ms
TXT
8820ms
CAA
4169ms
HTTPS
4224ms
TLSA
192ms
SOA
4211ms
MTA-STS
4337ms
DNSSEC
10491ms
SRV
4370ms
Total
22372ms

Scan History#

Scanned AtDurationRecordsDNSSEC
2026-11-05 12:59:04 2284ms 2 NS 1 A 1 MX Secure
2026-10-24 23:32:31 613ms 2 NS 1 A 1 MX Secure
2026-10-23 20:25:16 630ms 2 NS 1 A 1 MX Secure
2026-10-21 20:35:28 584ms 2 NS 1 A 1 MX Secure
2026-10-09 10:23:10 1152ms 2 NS 1 A 1 MX Secure
2026-10-04 03:28:07 3286ms 2 NS 1 A 1 MX Secure
2026-10-03 09:27:43 748ms 2 NS 1 A 1 MX Secure
2026-09-25 06:37:57 1265ms 2 NS 1 A 1 MX Secure
2026-09-23 14:03:03 2128ms 2 NS 1 A 1 MX Secure
2026-09-19 05:01:13 1223ms 2 NS 1 A 1 MX Secure
2026-09-06 17:22:14 2253ms 2 NS 1 A 1 MX Secure
2026-08-02 00:29:34 1309ms 2 NS 1 A 1 MX Secure
2026-07-04 02:57:20 1343ms 2 NS 1 A 1 MX Secure
2026-07-03 00:44:45 shown 22372ms 2 NS 0 A 0 MX Unknown
2026-07-03 00:04:27 14903ms 2 NS 0 A 0 MX Unknown
2026-06-25 19:43:46 848ms 2 NS 1 A 1 MX Secure
2026-06-18 06:19:33 1078ms 2 NS 1 A 1 MX Secure