ssejendomsservice.dk

📜 Historical scan 2026-06-17 13:04:57 · ← Latest scan

⬇ Zone File 📜 Timeline & History ⚡ Scan Now

ssejendomsservice.dk is a .dk domain served by 2 nameservers (ns01.one.com, ns02.one.com). It was registered on 16 May 2024 (WHOIS) and was already in the .dk zone when our tracking began on 16 June 2026. Its website address 46.30.215.127 is hosted by One.com A/S (AS51468) in Denmark. Mail is handled by aspmx.l.google.com, alt1.aspmx.l.google.com and 3 more. 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#

2 records 35ms

Nameserver	IP addresses	PTR	ASN / ISP
ns01.one.com	195.206.121.10 2001:67c:28cc::10	ns01.one.com ns01.one.com	AS197495 One.com A/S AS197495 One.com A/S
ns02.one.com	185.10.11.10 2001:67c:3c0::10	ns02.one.com ns02.one.com	AS51468 One.com A/S AS51468 One.com A/S

🌍 A Records#

1 records 34ms

IP	TTL	PTR	ASN	ISP / Org	CIDR	Country	City
46.30.215.127	—	webforward.webpod16-cph3.one.com	AS51468	One.com A/S	46.30.208.0/21	🇩🇰 Denmark	Copenhagen

📧 MX Records#

5 records 38ms

Priority	TTL	Mail Server	IP addresses	PTR	ASN
1	—	aspmx.l.google.com	108.177.14.26 2a00:1450:4025:c03::1a	lt-in-f26.1e100.net rc-in-f26.1e100.net	AS15169 Google LLC AS15169 Google LLC
5	—	alt1.aspmx.l.google.com	172.253.158.27 2404:6800:4003:c26::1a	so-in-f27.1e100.net so-in-f26.1e100.net	AS15169 Google LLC AS15169 Google LLC
5	—	alt2.aspmx.l.google.com	108.177.125.27 2404:6800:4003:c26::1a	tp-in-f27.1e100.net so-in-f26.1e100.net	AS15169 Google LLC AS15169 Google LLC
10	—	alt3.aspmx.l.google.com	192.178.230.27 2404:6800:400b:c01b::1b	yunrtab-in-f27.1e100.net yunrtab-in-f27.1e100.net	AS15169 Google LLC AS15169 Google LLC
10	—	alt4.aspmx.l.google.com	173.194.43.27 2404:6800:400b:c01b::1a	yudlsqd-in-f27.1e100.net yunrtab-in-f26.1e100.net	AS15169 Google LLC AS15169 Google LLC

🔷 AAAA Records (IPv6)#

✗ No AAAA records — IPv6 not configured

🔐 HTTPS Records#

✗ No HTTPS RR — no SVCB/HTTPS service binding

📝 TXT Records#

7 records 128ms

TXT Record
209.85.220.41
209.85.220.69
google-site-verification=Tw47_PSfLS9pNlyG26Wr6RQfM_KUJ59ydBNTL-AdRoc
v=DKIM1; k=rsa; p=MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEA3Y1/afSUNQrQhEMb7SBP5FQjx5cpAc0zzZsw3Qwc0f8kwdueP8ksdncZ/9Wl98hwR43iLbaKNgGFgcZY6/4NxT90ibceO2swun/3M6F9NPHdk8ToKZuUi/8HfTq3gETV2Cd5dNU9cFTeAQb3VPS7P+peIBReZa0Qdop2pHfGp+LKFXewdaw46/cixt//tAbs62zsPhHfHvQ2YxMRQtOMF21lCbKgHGvaCgaCbv5WKW4ubaJwKhlrTUYASKtgHgFqGXRVBPL5R0I0jYJrGR0hMnLJZQzWG+/0jbPkUJzcTIKEjFjQbNP5zNZiVf/iWGfzLVJJQgDiRAmLxRuF/QeA7QIDAQAB
v=DMARC1; p=none; rua=mailto:postmaster@ssejendomsservice.dk; ruf=mailto:postmaster@ssejendomsservice.dk; fo=1
v=spf1 include:_custspf.one.com include:_spf.google.com ~all
v=spf1 include:_spf.google.com include:_custspf.one.com ~all

✉️ SPF#

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

Policy	Record (ssejendomsservice.dk)
~all (soft fail)	v=spf1 include:_custspf.one.com include:_spf.google.com ~all
~all (soft fail)	v=spf1 include:_spf.google.com include:_custspf.one.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-17 18:19:27

www	195.47.247.18 (AS51468) (address records, no CNAME)
www vs bare domain	Same network ssejendomsservice.dk: 195.47.247.18 (AS51468) www.ssejendomsservice.dk: 195.47.247.18 (AS51468)
Wildcard	Yes: any name under the zone resolves
CDS / CDNSKEY	None 0 CDS, 0 CDNSKEY

✍️ DKIM keys#

1 found

Selector	CNAME	Key
google	—	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: 2/10 · policy: ~all

error 2 SPF records: receivers must treat that as a permanent error (RFC 7208 §4.5)

🔗 TLSA / DANE#

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

🔐 DNSSEC#

83ms

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

🏷️ SOA#

49ms

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

📋 Registration#

WHOIS fetched 2026-10-03 01:10:09

Field	Value
Registrar	ONE.COM A/S
Registered	2024-05-16
Expires	2027-05-15 (205d)

📋 WHOIS#

⏱️ Lookup Timing#

35ms

34ms

38ms

AAAA

50ms

TXT

128ms

CAA

57ms

HTTPS

37ms

TLSA

56ms

SOA

49ms

MTA-STS

100ms

DNSSEC

83ms

SRV

0ms

Total

656ms

🕐 Scan History#

Scanned At	Duration	Records	DNSSEC
2026-10-17 18:19:27	2958ms	2 NS 1 A 5 MX	🔒 Secure
2026-10-03 01:01:13	799ms	2 NS 1 A 5 MX	🔒 Secure
2026-09-30 13:30:37	711ms	2 NS 1 A 5 MX	🔒 Secure
2026-09-29 20:09:36	607ms	2 NS 1 A 5 MX	🔒 Secure
2026-09-27 06:48:10	646ms	2 NS 1 A 5 MX	🔒 Secure
2026-09-16 04:03:14	906ms	2 NS 1 A 5 MX	🔒 Secure
2026-09-02 19:48:29	2755ms	2 NS 1 A 5 MX	🔒 Secure
2026-08-06 04:00:49	1446ms	2 NS 1 A 5 MX	🔒 Secure
2026-06-25 01:33:46	736ms	2 NS 1 A 5 MX	🔒 Secure
2026-06-22 19:41:43	913ms	0 NS 0 A 0 MX	❓ Unknown
2026-06-17 13:04:57 shown	656ms	2 NS 1 A 5 MX	🔒 Secure