be-happy.dk

📜 Historical scan 2026-06-16 14:13:01 · ← Latest scan

⬇ Zone File 📜 Timeline & History ⚡ Scan Now

be-happy.dk is a .dk domain served by 3 nameservers (ns5.chosting.dk, ns6.chosting.dk, ns7.chosting.dk). It was registered on 23 December 2013 (WHOIS) and was already in the .dk zone when our tracking began on 16 June 2026. Its website address 109.201.154.65 is hosted by NForce Entertainment B.V. (AS43350) in The Netherlands. Mail is handled by be-happy.dk. The zone is not DNSSEC-signed, 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 67ms

Nameserver	IP addresses	PTR	ASN / ISP
ns5.chosting.dk	—	—	—
ns6.chosting.dk	—	—	—
ns7.chosting.dk	—	—	—

🌍 A Records#

1 records 68ms

IP	TTL	PTR	ASN	ISP / Org	CIDR	Country	City
109.201.154.65	—	—	AS43350	NForce Entertainment B.V.	109.201.128.0/19	🇳🇱 The Netherlands	—

📧 MX Records#

1 records 65ms

Priority	TTL	Mail Server	IP addresses	PTR	ASN
0	—	be-happy.dk	109.201.154.65	—	AS43350 NForce Entertainment B.V.

🔷 AAAA Records (IPv6)#

✗ No AAAA records — IPv6 not configured

🔐 HTTPS Records#

✗ No HTTPS RR — no SVCB/HTTPS service binding

📝 TXT Records#

1 records 243ms

TXT Record
v=spf1 include:spf.chosting.dk include:spf.mandrillapp.com ?all

✉️ SPF#

Policy	Record (be-happy.dk)
?all (neutral)	v=spf1 include:spf.chosting.dk include:spf.mandrillapp.com ?all

📨 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-12 08:52:19

www CNAME	be-happy.dk (all on be-happy.dk) → 109.201.154.65 (AS43350)
www vs bare domain	Same network be-happy.dk: 109.201.154.65 (AS43350) www.be-happy.dk: 109.201.154.65 (AS43350)
Wildcard	No

🔎 SPF check#

zone-wide SPF report

DNS lookups: 4/10 · policy: ?all

warn "?all" is neutral: it gives receivers no guidance, much like having no SPF

🔗 TLSA / DANE#

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

🔐 DNSSEC#

160ms

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

🏷️ SOA#

69ms

Field	Value
Serial	2018011800
Primary NS (MNAME)	ns5.chosting.dk
Responsible (RNAME)	logs@chosting.dk
Refresh	86400s
Retry	7200s
Expire	3600000s
Minimum (neg-cache TTL)	86400s

📋 Registration#

WHOIS fetched 2026-10-06 00:50:16

Field	Value
Registrar	Punktum dk A/S (direct)
Registered	2013-12-23
Expires	2026-12-31 (75d)

📋 WHOIS#

⏱️ Lookup Timing#

67ms

68ms

65ms

AAAA

68ms

TXT

243ms

CAA

63ms

HTTPS

67ms

TLSA

159ms

SOA

69ms

MTA-STS

44ms

DNSSEC

160ms

SRV

0ms

Total

800ms

🕐 Scan History#

Scanned At	Duration	Records	DNSSEC
2026-06-26 18:20:43	2094ms	3 NS 1 A 1 MX	🔓 Insecure
2026-06-26 05:31:24	868ms	3 NS 1 A 1 MX	🔓 Insecure
2026-06-16 14:13:32	353ms	3 NS 1 A 1 MX	🔓 Insecure
2026-06-16 14:13:01 shown	800ms	3 NS 1 A 1 MX	🔓 Insecure