shootme.dk
Historical scan 2026-07-18 09:52:02 · ← Latest scan
shootme.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 6 July 2016 (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 432msA 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-03 21:38:26| www | 46.30.211.38 (AS51468) (address records, no CNAME) |
| www vs bare domain | Same network |
| 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#
580ms| 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-03 21:52:21| Field | Value |
|---|---|
| Registrar | ONE.COM A/S |
| Registered | 2016-07-06 |
| Expires | 2027-07-31 (251d) |
Same registrant#
8 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).
📋 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-03 21:38:26 | 317ms | 2 NS 1 A 1 MX | Secure |
| 2026-10-08 15:21:34 | 461ms | 2 NS 1 A 1 MX | Secure |
| 2026-10-01 11:19:14 | 314ms | 2 NS 1 A 1 MX | Secure |
| 2026-09-26 10:36:39 | 4396ms | 2 NS 1 A 1 MX | Secure |
| 2026-09-01 04:48:30 | 392ms | 2 NS 1 A 1 MX | Secure |
| 2026-08-27 01:29:23 | 396ms | 2 NS 1 A 1 MX | Secure |
| 2026-08-25 20:20:40 | 465ms | 2 NS 1 A 1 MX | Insecure |
| 2026-08-23 16:57:47 | 3411ms | 2 NS 0 A 0 MX | Bogus |
| 2026-08-22 13:09:22 | 10119ms | 2 NS 0 A 0 MX | Bogus |
| 2026-08-21 12:56:24 | 8979ms | 2 NS 0 A 0 MX | Bogus |
| 2026-08-20 12:21:22 | 10165ms | 2 NS 0 A 0 MX | Bogus |
| 2026-08-19 11:51:55 | 1960ms | 2 NS 0 A 0 MX | Bogus |
| 2026-08-18 11:50:04 | 4035ms | 2 NS 0 A 0 MX | Bogus |
| 2026-08-16 18:13:40 | 1356ms | 2 NS 0 A 0 MX | Bogus |
| 2026-08-14 13:33:25 | 861ms | 2 NS 0 A 0 MX | Bogus |
| 2026-08-13 07:07:44 | 4125ms | 2 NS 0 A 0 MX | Bogus |
| 2026-08-11 15:00:37 | 4050ms | 2 NS 0 A 0 MX | Bogus |
| 2026-08-10 10:55:13 | 1542ms | 2 NS 0 A 0 MX | Bogus |
| 2026-08-09 08:08:52 | 2434ms | 2 NS 0 A 0 MX | Bogus |
| 2026-07-29 14:22:37 | 21295ms | 2 NS 0 A 0 MX | Unknown |
| 2026-07-27 08:52:10 | 1530ms | 2 NS 0 A 0 MX | Bogus |
| 2026-07-26 08:24:13 | 970ms | 2 NS 0 A 0 MX | Bogus |
| 2026-07-25 08:05:27 | 9124ms | 2 NS 0 A 0 MX | Bogus |
| 2026-07-24 07:21:41 | 18612ms | 2 NS 0 A 0 MX | Bogus |
| 2026-07-23 06:53:34 | 1104ms | 2 NS 0 A 0 MX | Bogus |