acendy.dk

📜 Historical scan 2026-06-16 12:50:25 · ← Latest scan

⬇ Zone File 📜 Timeline & History ⚡ Scan Now

acendy.dk is a .dk domain served by 2 nameservers (ns01.no.brand.one.com, ns02.no.brand.one.com). It was already in the .dk zone when our tracking began on 16 June 2026. Its website address 104.37.39.71 is hosted by One.com A/S (AS51468) in Norway. Mail is handled by x.tornado.email, y.tornado.email and 1 more. 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#

2 records 48ms

Nameserver	IP addresses	PTR	ASN / ISP
ns01.no.brand.one.com	—	—	—
ns02.no.brand.one.com	—	—	—

🌍 A Records#

1 records 58ms

IP	TTL	PTR	ASN	ISP / Org	CIDR	Country	City
104.37.39.71	—	—	AS51468	One.com A/S	104.37.32.0/21	🇳🇴 Norway	—

📧 MX Records#

3 records 66ms

Priority	TTL	Mail Server	IP addresses	PTR	ASN
42	—	x.tornado.email	195.159.29.202	x.tornado.email	AS2116 Globalconnect As
42	—	y.tornado.email	195.159.29.17	y.tornado.email	AS2116 Globalconnect As
42	—	z.tornado.email	195.159.29.209	z.tornado.email	AS2116 Globalconnect As

🔷 AAAA Records (IPv6)#

✗ No AAAA records — IPv6 not configured

🔐 HTTPS Records#

✗ No HTTPS RR — no SVCB/HTTPS service binding

📝 TXT Records#

1 records 195ms

TXT Record
v=spf1 a include:tornado.email ?all

✉️ SPF#

Policy	Record (acendy.dk)
?all (neutral)	v=spf1 a include:tornado.email ?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-08 15:37:11

www CNAME	acendy.dk (all on acendy.dk) → 104.37.39.71 (AS51468)
www vs bare domain	Same network acendy.dk: 104.37.39.71 (AS51468) www.acendy.dk: 104.37.39.71 (AS51468)
Wildcard	No

🔎 SPF check#

zone-wide SPF report

DNS lookups: 2/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#

144ms

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

🏷️ SOA#

50ms

Field	Value
Serial	2026041001
Primary NS (MNAME)	ns01.no.brand.one.com
Responsible (RNAME)	hostmaster@no.brand.one.com
Refresh	14400s
Retry	3600s
Expire	1209600s
Minimum (neg-cache TTL)	600s

📋 Registration#

✗ No registration data yet — queued for a WHOIS lookup

📋 WHOIS#

⏱️ Lookup Timing#

48ms

58ms

66ms

AAAA

50ms

TXT

195ms

CAA

69ms

HTTPS

63ms

TLSA

167ms

SOA

50ms

MTA-STS

118ms

DNSSEC

144ms

SRV

0ms

Total

1478ms

🕐 Scan History#

Scanned At	Duration	Records	DNSSEC
2026-10-08 15:37:11	1046ms	2 NS 1 A 3 MX	🔓 Insecure
2026-08-27 05:52:20	728ms	2 NS 1 A 3 MX	🔓 Insecure
2026-06-27 10:42:56	975ms	2 NS 1 A 3 MX	🔓 Insecure
2026-06-22 14:56:03	833ms	2 NS 1 A 3 MX	🔓 Insecure
2026-06-16 12:50:25 shown	1478ms	2 NS 1 A 3 MX	🔓 Insecure