frederikkereese.dk

Records from scan: 2026-09-30 09:18:54 · 761ms total · last checked 2026-10-21 19:46 (unchanged)

⬇ Zone File 📜 Timeline & History ⚡ Scan Now

frederikkereese.dk is a .dk domain served by 3 nameservers (ns5.chosting.dk, ns6.chosting.dk, ns7.chosting.dk). It was already in the .dk zone when our tracking began on 16 June 2026. Its website address 178.20.216.100 is hosted by Atea A/S (AS21060) in Denmark. Mail is handled by mail.frederikkereese.dk. The zone is not DNSSEC-signed, publishes a DMARC policy and is reachable over IPv6. 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#

3 records 44ms

Nameserver	IP addresses	PTR	ASN / ISP
ns5.chosting.dk	167.235.66.236 2a01:4f8:1c1e:d097::1	ns5.chosting.dk ns5.chosting.dk	AS24940 Hetzner Online GmbH AS24940 Hetzner Online GmbH
ns6.chosting.dk	2001:41d0:305:2100::80e9 51.91.57.33	ns6.chosting.dk ns6.chosting.dk	AS16276 OVH SAS AS16276 OVH SAS
ns7.chosting.dk	178.20.220.33	ns7.chosting.dk	AS21060 Atea A/S

🌍 A Records#

1 records 44ms

IP	TTL	PTR	ASN	ISP / Org	CIDR	Country	City
178.20.216.100	14400s	server18.chosting.dk	AS21060	Atea A/S	178.20.216.0/23	🇩🇰 Denmark	—

📧 MX Records#

1 records 52ms

Priority	TTL	Mail Server	IP addresses	PTR	ASN
0	14400s	mail.frederikkereese.dk	178.20.216.100 2a01:7cc0:101:ffff::1:14	server18.chosting.dk —	AS21060 Atea A/S AS21060 Atea A/S

📧 Autodiscover / Autoconfig#

Service	CNAME / IP
🔷 Autodiscover	178.20.216.100
🔶 Autoconfig	178.20.216.100

🔷 AAAA Records (IPv6)#

1 records 51ms

IPv6 Address	TTL	PTR	ASN	ISP / Org	CIDR	Country	City
2a01:7cc0:101:ffff::1:14	14400s	—	AS21060	Atea A/S	2a01:7cc0:100:0:0:0:0:0/40	🇩🇰 Denmark	—

🔐 HTTPS Records#

✗ No HTTPS RR — no SVCB/HTTPS service binding

🔌 SRV Records#

1 records 90ms

Service	Priority	Weight	Port	Target
_autodiscover._tcp	0	0	443	cpanelemaildiscovery.cpanel.net

📝 TXT Records#

3 records 279ms

TXT Record
google-site-verification=pKdTKFK3lqhrsQCueEpyqGVu7v_RMsY1_SmQagxon3U
v=spf1 a mx include:_spf.mlsend.com ?all
v=spf1 ip4:178.20.216.100 include:spf.chosting.dk +a +mx ~all

✉️ SPF#

⚠ Multiple SPF records — RFC 7208 §4.5 violation (receivers must treat this as permerror)

Policy	Record (frederikkereese.dk)
?all (neutral)	v=spf1 a mx include:_spf.mlsend.com ?all
~all (soft fail)	v=spf1 ip4:178.20.216.100 include:spf.chosting.dk +a +mx ~all

📨 DMARC#

Policy	Record (_dmarc.frederikkereese.dk)
p=none (monitor only)	v=DMARC1; p=none;

📬 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-09 18:00:43

www CNAME	frederikkereese.dk (all on frederikkereese.dk) → 178.20.216.100 2a01:7cc0:101:ffff::1:14 (AS21060)
www vs bare domain	Same network frederikkereese.dk: 178.20.216.100 2a01:7cc0:101:ffff::1:14 (AS21060) www.frederikkereese.dk: 178.20.216.100 2a01:7cc0:101:ffff::1:14 (AS21060)
Wildcard	No

✍️ DKIM keys#

1 found

Selector	CNAME	Key
default	—	RSA · ~2048 bit

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.

🔎 SPF check#

zone-wide SPF report

DNS lookups: 3/10 · policy: ?all

error 2 SPF records: receivers must treat that as a permanent error (RFC 7208 §4.5)
warn "?all" is neutral: it gives receivers no guidance, much like having no SPF

🔏 ACME Challenge#

Type	Name	Value
TXT	_acme-challenge.frederikkereese.dk	JOY8KILEgsUAMtx5_qikgGqRLMg_goE_I-3coD9q_s0

🔗 TLSA / DANE#

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

🔐 DNSSEC#

80ms

Check	Result
Validation Status	🔓 Insecure
AD Flag (resolver validates)	✗ Not set
DS Record	✗ Not found
DNSKEY Record	✗ Not found
Flags	unsigned answer

🏷️ SOA#

0ms

Field	Value
Serial	2026092402
Primary NS (MNAME)	ns5.chosting.dk
Responsible (RNAME)	logs@chosting.dk
Refresh	3600s
Retry	1800s
Expire	1209600s
Minimum (neg-cache TTL)	86400s

📋 Registration#

✗ No registration data yet — queued for a WHOIS lookup

📋 WHOIS#

⏱️ Lookup Timing#

44ms

52ms

AAAA

51ms

TXT

279ms

CAA

59ms

HTTPS

40ms

TLSA

198ms

SOA

0ms

MTA-STS

84ms

DNSSEC

80ms

SRV

90ms

Total

761ms

🕐 Scan History#

Scanned At	Duration	Records	DNSSEC
2026-09-30 09:18:54 shown	761ms	3 NS 1 A 1 MX	🔓 Insecure
2026-09-24 10:52:37	1905ms	3 NS 1 A 1 MX	🔓 Insecure
2026-07-25 07:19:43	9972ms	3 NS 1 A 1 MX	🔓 Insecure
2026-07-01 23:31:59	863ms	3 NS 1 A 1 MX	🔓 Insecure
2026-06-17 09:33:32	1013ms	3 NS 1 A 1 MX	🔓 Insecure