evhydrogen.dk

📜 Historical scan 2026-06-17 09:08:13 · ← Latest scan

⬇ Zone File 📜 Timeline & History ⚡ Scan Now

evhydrogen.dk is a .dk domain served by 2 nameservers (ns1.curanet.dk, ns2.curanet.dk). It was already in the .dk zone when our tracking began on 16 June 2026. Its website address 93.191.152.164 is hosted by team.blue Denmark A/S (AS48854) in Denmark. The zone is DNSSEC-signed and validates, publishes a 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 65ms

Nameserver	IP addresses	PTR	ASN / ISP
ns1.curanet.dk	—	—	—
ns2.curanet.dk	—	—	—

🌍 A Records#

1 records 64ms

IP	TTL	PTR	ASN	ISP / Org	CIDR	Country	City
93.191.152.164	—	web4.vjm.dk	AS48854	team.blue Denmark A/S	93.191.152.0/21	🇩🇰 Denmark	—

📧 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#

2 records 256ms

TXT Record
mandrill_verify.s69HJhG-5CBrctJu1sMWUA
v=spf1 include:spf.mandrillapp.com ?all

✉️ SPF#

Policy	Record (evhydrogen.dk)
?all (neutral)	v=spf1 include:spf.mandrillapp.com ?all

📨 DMARC#

Policy	Record (_dmarc.evhydrogen.dk)
p=quarantine	v=DMARC1; p=quarantine;

📬 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 22:59:10

www	93.191.152.164 (AS48854) (address records, no CNAME)
www vs bare domain	Same network evhydrogen.dk: 93.191.152.164 (AS48854) www.evhydrogen.dk: 93.191.152.164 (AS48854)
Wildcard	Yes: any name under the zone resolves
Denial of existence	NSEC3 · 1 iteration · 1-byte salt RFC 9276 recommends 0 iterations and no salt
CDS / CDNSKEY	None 0 CDS, 0 CDNSKEY

🔎 SPF check#

zone-wide SPF report

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

190ms

Check	Result
Validation Status	🔒 Secure
AD Flag (resolver validates)	✓ Set
DS Record	✓ Found
DNSKEY Record	✓ Found
Flags	fully validated

🏷️ SOA#

44ms

Field	Value
Serial	2024012201
Primary NS (MNAME)	ns1.curanet.dk
Responsible (RNAME)	hostmaster@curanet.dk
Refresh	14400s
Retry	3600s
Expire	1209600s
Minimum (neg-cache TTL)	300s

📋 Registration#

✗ No registration data yet — queued for a WHOIS lookup

📋 WHOIS#

⏱️ Lookup Timing#

65ms

64ms

63ms

AAAA

52ms

TXT

256ms

CAA

68ms

HTTPS

62ms

TLSA

116ms

SOA

44ms

MTA-STS

105ms

DNSSEC

190ms

SRV

0ms

Total

1021ms

🕐 Scan History#

Scanned At	Duration	Records	DNSSEC
2026-09-29 21:43:29	348ms	2 NS 1 A 0 MX	🔒 Secure
2026-09-26 02:05:33	413ms	2 NS 1 A 0 MX	🔒 Secure
2026-09-22 21:37:06	402ms	2 NS 1 A 0 MX	🔒 Secure
2026-06-27 02:04:26	1311ms	2 NS 1 A 0 MX	🔒 Secure
2026-06-24 21:13:22	1761ms	2 NS 1 A 0 MX	🔒 Secure
2026-06-23 22:42:35	1170ms	0 NS 0 A 0 MX	❓ Unknown
2026-06-17 09:08:13 shown	1021ms	2 NS 1 A 0 MX	🔒 Secure