famweb.dk
Records from scan: 2026-10-09 12:38:20 · 4094ms total · last checked 2026-11-21 08:59 (unchanged)
famweb.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 8 September 2008 (WHOIS) and was already in the .dk zone when our tracking began on 16 June 2026. Below are all of its DNS records from our latest scan: nameservers, A/AAAA, MX, TXT, SPF, DMARC, CAA, TLSA/DANE, MTA-STS, SRV and more.
Nameservers#
2 records 81msA 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#
checked 2026-10-04 08:11:02| www | NXDOMAIN |
| 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#
1364ms| Check | Result |
|---|---|
| Validation Status | Bogus — the parent still publishes a DS record, but the delegated nameservers don't answer, so no signed answer can be fetched. The zone isn't serving broken signatures; it isn't serving at all. |
| AD Flag (resolver validates) | Not set |
| DS Record | Found |
| DNSKEY Record | Not found |
| Flags | resolution failed: failure |
SOA#
No SOA record found
Registration#
WHOIS fetched 2026-11-06 18:31:17| Field | Value |
|---|---|
| Registrar | Punktum dk A/S (direct) |
| Registered | 2008-09-08 |
| Expires | 2027-09-30 (312d) |
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-10-09 12:38:20 shown | 4094ms | 2 NS 0 A 0 MX | Bogus |
| 2026-10-04 08:11:02 | 404ms | 2 NS 0 A 0 MX | Secure |
| 2026-09-24 18:15:59 | 483ms | 2 NS 0 A 0 MX | Secure |
| 2026-09-22 15:19:19 | 648ms | 2 NS 0 A 0 MX | Secure |
| 2026-09-15 13:58:21 | 485ms | 2 NS 0 A 0 MX | Secure |
| 2026-09-06 02:15:31 | 1223ms | 2 NS 1 A 4 MX | Secure |
| 2026-08-27 19:43:27 | 748ms | 2 NS 1 A 4 MX | Secure |
| 2026-08-23 07:51:09 | 969ms | 2 NS 1 A 4 MX | Secure |
| 2026-08-22 07:36:59 | 1146ms | 2 NS 1 A 4 MX | Secure |
| 2026-08-19 05:35:08 | 5907ms | 2 NS 1 A 4 MX | Secure |
| 2026-07-17 21:14:44 | 1063ms | 2 NS 1 A 4 MX | Secure |
| 2026-06-26 00:40:58 | 1752ms | 2 NS 1 A 4 MX | Secure |
| 2026-06-25 09:20:50 | 836ms | 2 NS 1 A 4 MX | Secure |
| 2026-06-24 21:09:54 | 723ms | 2 NS 1 A 4 MX | Secure |
| 2026-06-22 07:25:17 | 763ms | 2 NS 1 A 4 MX | Secure |
| 2026-06-21 17:08:16 | 571ms | 2 NS 1 A 4 MX | Secure |
| 2026-06-19 18:20:46 | 720ms | 2 NS 1 A 4 MX | Secure |
| 2026-06-17 09:15:25 | 2239ms | 2 NS 1 A 4 MX | Secure |