SurfaceMap › s › sylt.de

sylt.de

Checked 2026-10-22 00:31 UTC · first added 2026-10-21

✗Problems found Score 69 of 100

Domain & DNS

warn

23 passed 1 warn 0 failed

Areas

iRegistration iDelegation iNameservers ✓SOA !DNSSEC iRecords

Problems

!

Not signed

DNSSEC · The zone is not signed with DNSSEC, so answers can be spoofed. Enable DNSSEC at your DNS provider and publish the DS record at your registrar.

#27

Recent checks

!

Full report

Domain & DNS report for sylt.de ›

Mail

fail

17 passed 6 warn 1 failed

Areas

✓SPF ✗DMARC !DKIM !DNSSEC !MX !TLS iBIMI

Problems

✗

Policy: none (monitoring only)

DMARC · DMARC policy is set to 'none', which only monitors but doesn't protect against spoofing. Consider upgrading to 'quarantine' or ideally 'reject'.

#4
!

No key under common selectors

DKIM · The _domainkey name exists but no DKIM key was found under the common selectors. Selectors are provider-specific; check yours with -selector.

#7
!

Not enabled

DNSSEC · DNSSEC is not enabled for this domain. Consider enabling DNSSEC to protect against DNS spoofing attacks.

#8
!

Hosts without IPv6

MX · The following MX hosts could not be resolved to IPv6 addresses: mx23a.antispameurope.com, mx23b.antispameurope.com, mx23c.antispameurope.com, mx23d.antispameurope.com

#11
!

No aggregate reports (rua)

DMARC · DMARC record has no rua tag, so you receive no aggregate reports about who sends mail as your domain. Add rua=mailto:...

#19
!

Reverse DNS does not match

MX · The PTR name of these addresses does not resolve back to the same address: 83.246.65.100 -> nlb01-hz2.hornetsecurity.com.65.246.83.in-addr.arpa.

#30
!

Not configured

TLS · MTA-STS is not configured, so other mail servers fall back to unencrypted delivery when TLS fails or is stripped by an attacker. Publish a _mta-sts TXT record and a policy at https://mta-sts.<domain>/.well-known/mta-sts.txt.

#32

Recent checks

✗

Full report

Mail report for sylt.de ›