fam-thyme.dk
Historical scan 2026-06-21 17:28:05 · ← Latest scan
fam-thyme.dk is a .dk domain with no delegation in this scan. It was registered on 4 March 2007 (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#
No NS records found
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-17 12:00:28| www | 46.30.213.110 2a02:2350:5:10b:8077:c762:cc12:f7d3 (AS51468) (address records, no CNAME) |
| www vs bare domain | Same network fam-thyme.dk: 46.30.213.110 2a02:2350:5:10b:8077:c762:cc12:f7d3 (AS51468) www.fam-thyme.dk: 46.30.213.110 2a02:2350:5:10b:8077:c762:cc12:f7d3 (AS51468) |
| Wildcard | No |
| Denial of existence | NSEC3 · 0 iterations · no salt RFC 9276 ✓ |
| CDS / CDNSKEY | None 0 CDS, 0 CDNSKEY |
TLSA / DANE#
No TLSA records — DANE not configured for HTTPS (_443) or MX (_25)
DNSSEC#
311ms| Check | Result |
|---|---|
| Validation Status | Not applicable: the domain has no delegation, so there is no zone to validate (stored verdict: Unknown). |
| 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-11-16 11:45:53| Field | Value |
|---|---|
| Registrar | ONE.COM A/S |
| Registered | 2007-03-04 |
| Expires | 2027-03-31 (129d) |
Same registrant#
0 domainsOther .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
A
MX
AAAA
TXT
CAA
HTTPS
TLSA
SOA
MTA-STS
DNSSEC
SRV
Total
Scan History#
| Scanned At | Duration | Records | DNSSEC |
|---|---|---|---|
| 2026-11-17 12:00:28 | 453ms | 2 NS 1 A 4 MX | Secure |
| 2026-11-16 11:39:28 | 1751ms | 2 NS 1 A 4 MX | Secure |
| 2026-11-12 11:03:43 | 478ms | 2 NS 1 A 4 MX | Secure |
| 2026-10-25 05:51:44 | 1365ms | 2 NS 1 A 4 MX | Secure |
| 2026-10-07 15:36:36 | 841ms | 2 NS 1 A 4 MX | Secure |
| 2026-09-24 10:32:46 | 577ms | 2 NS 1 A 4 MX | Secure |
| 2026-09-11 22:02:51 | 1473ms | 2 NS 1 A 4 MX | Secure |
| 2026-08-27 11:03:33 | 809ms | 2 NS 1 A 4 MX | Secure |
| 2026-08-26 01:07:09 | 929ms | 2 NS 1 A 4 MX | Secure |
| 2026-08-15 11:16:37 | 4904ms | 2 NS 1 A 4 MX | Secure |
| 2026-08-07 22:20:52 | 1004ms | 2 NS 1 A 4 MX | Secure |
| 2026-08-04 19:34:01 | 8823ms | 2 NS 1 A 4 MX | Secure |
| 2026-07-09 00:52:22 | 1227ms | 2 NS 1 A 4 MX | Secure |
| 2026-07-03 19:53:51 | 5399ms | 2 NS 1 A 4 MX | Secure |
| 2026-06-30 13:30:58 | 704ms | 2 NS 1 A 4 MX | Secure |
| 2026-06-27 18:47:10 | 1457ms | 2 NS 1 A 4 MX | Secure |
| 2026-06-25 09:36:35 | 725ms | 2 NS 1 A 4 MX | Secure |
| 2026-06-21 17:28:05 shown | 1025ms | 0 NS 0 A 0 MX | Unknown |
| 2026-06-20 23:03:06 | 596ms | 2 NS 1 A 4 MX | Secure |
| 2026-06-17 09:13:55 | 1202ms | 2 NS 1 A 4 MX | Secure |