SurfaceMap › a › arnsberg.de

arnsberg.de

Checked 2026-10-21 21:30 UTC · first added 2026-10-21

✗Problems found Score 44 of 100

Domain & DNS

fail

22 passed 2 warn 1 failed

Areas

iRegistration ✓Delegation ✗Nameservers ✓SOA !DNSSEC !Records

Problems

✗

Nameservers not responding

Nameservers · These addresses did not answer, so resolvers waste time on timeouts: ns.suedwestfalenit.de (2a02:100e:bef8:2:0:57:11:1): read udp [2a01:4f8:1c1c:eebf::1]:54756->[2a02:100e:bef8:2:0:57:11:1]:53: i/o timeout; ns.suedwestfalenit.nrw (2a02:100e:bef8:2:0:57:12:1): read udp [2a01:4f8:1c1c:eebf::1]:37495->[2a02:100e:bef8:2:0:57:12:1]:53: i/o timeout.

#14
!

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
!

Very low TTLs

Records · These records have a TTL below 5m, causing extra queries and slower lookups: A (1m), AAAA (1m), MX (1m). Low TTLs are useful just before a planned change.

#32

Recent checks

✗

Full report

Domain & DNS report for arnsberg.de ›

Mail

fail

17 passed 10 warn 1 failed

Areas

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

Problems

✗

TLSA records not DNSSEC-validated

TLS · These MX hosts publish TLSA records that the resolver could not validate with DNSSEC, so senders ignore them or, if validation fails, may refuse delivery: mx-in.kommunale.it.

#36
!

Policy: quarantine

DMARC · DMARC policy is set to 'quarantine'. Consider upgrading to 'reject' for stronger protection once you've verified legitimate emails are passing authentication.

#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: mx-in.kommunale.it

#11
!

Single MX host, no backup

MX · Only one MX record found. For better email reliability, consider adding at least one backup MX server.

#12
!

Applies to 50% of mail

DMARC · DMARC policy only applies to 50% of failing mail (pct=50). Raise pct to 100 once you are confident in your setup.

#18
!

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
!

Subdomains unprotected (sp=none)

DMARC · DMARC subdomain policy is sp=none, so spoofed mail from subdomains is not blocked. Consider sp=quarantine or sp=reject.

#20
!

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