q-courage.dk

📜 Historical scan 2026-06-18 03:35:09 · ← Latest scan

⬇ Zone File 📜 Timeline & History ⚡ Scan Now

q-courage.dk is a .dk domain served by 3 nameservers (ns1.simply.com, ns2.simply.com, ns3.simply.com). It was registered on 21 March 2023 (WHOIS) and was already in the .dk zone when our tracking began on 16 June 2026. The zone is DNSSEC-signed and validates, has no DMARC policy and has no IPv6 address. 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#

3 records 69ms

Nameserver	IP addresses	PTR	ASN / ISP
ns1.simply.com	2a02:2339:1:15c::4562:4562 91.197.248.78	ns1.simply.com ns1.simply.com	AS48854 team.blue Denmark A/S AS48854 team.blue Denmark A/S
ns2.simply.com	185.25.141.15 2a02:2339:4006:101::4562:4562	ns2.simply.com ns2.simply.com	AS48854 team.blue Denmark A/S AS48854 team.blue Denmark A/S
ns3.simply.com	91.197.248.79	ns3.simply.com	AS48854 team.blue Denmark 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

🧩 Web & zone#

latest probe, not this scan · checked 2026-10-13 08:13:44

www	93.191.156.188 (AS48854) (address records, no CNAME)
www vs bare domain	Same network q-courage.dk: 93.191.156.188 (AS48854) www.q-courage.dk: 93.191.156.188 (AS48854)
Wildcard	Yes: any name under the zone resolves
Denial of existence	NSEC zone can be walked (all names enumerable)
CDS / CDNSKEY	Published: key rollovers can be automated with the registry (RFC 7344/8078) 1 CDS, 1 CDNSKEY

✍️ DKIM keys#

1 found

Selector	CNAME	Key
google	—	RSA Invalid key data — receivers can't verify signatures

DKIM selectors can't be listed, so we check the common ones (Microsoft 365, Google, Mailchimp, SendGrid, generic). Keys under other selectors aren't shown.

🔗 TLSA / DANE#

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

🔐 DNSSEC#

176ms

Check	Result
Validation Status	🔒 Secure
AD Flag (resolver validates)	✓ Set
DS Record	✓ Found
DNSKEY Record	✓ Found
Flags	resolution failed: ncache nxrrset

🏷️ SOA#

75ms

Field	Value
Serial	2026061500
Primary NS (MNAME)	ns1.simply.com
Responsible (RNAME)	hostmaster@simply.com
Refresh	14400s
Retry	3600s
Expire	1209600s
Minimum (neg-cache TTL)	3600s

📋 Registration#

WHOIS fetched 2026-07-03 05:23:05

Field	Value
Registrar	Simply.com A/S
Registered	2023-03-21
Expires	2027-03-20 (153d)

📋 WHOIS#

⏱️ Lookup Timing#

69ms

72ms

61ms

AAAA

76ms

TXT

252ms

CAA

75ms

HTTPS

90ms

TLSA

36ms

SOA

75ms

MTA-STS

63ms

DNSSEC

176ms

SRV

119ms

Total

569ms

🕐 Scan History#

Scanned At	Duration	Records	DNSSEC
2026-10-03 07:47:53	490ms	3 NS 1 A 5 MX	🔒 Secure
2026-09-26 06:27:38	807ms	3 NS 1 A 5 MX	🔒 Secure
2026-09-18 08:24:21	665ms	3 NS 1 A 5 MX	🔒 Secure
2026-08-26 20:32:03	976ms	3 NS 1 A 5 MX	🔒 Secure
2026-07-03 05:22:28	2686ms	3 NS 1 A 5 MX	🔒 Secure
2026-06-28 05:22:24	511ms	3 NS 0 A 0 MX	🔒 Secure
2026-06-25 23:12:01	1485ms	3 NS 0 A 0 MX	🔒 Secure
2026-06-20 05:20:59	673ms	3 NS 0 A 0 MX	🔒 Secure
2026-06-18 13:11:35	471ms	3 NS 0 A 0 MX	🔒 Secure
2026-06-18 03:35:09 shown	569ms	3 NS 0 A 0 MX	🔒 Secure