SurfaceMap › g › guug.de

guug.de

Checked 2026-10-21 22:41 UTC · first added 2026-10-21

✗Problems found Score 62 of 100

Domain & DNS

fail

22 passed 2 warn 1 failed

Areas

iRegistration ✓Delegation ✗Nameservers !SOA !DNSSEC iRecords

Problems

✗

Nameservers not responding

Nameservers · These addresses did not answer, so resolvers waste time on timeouts: ns2.guug.de (46.4.78.167): read udp 46.225.38.91:44961->46.4.78.167:53: i/o timeout; ns2.guug.de (2a01:4f8:140:54e4::2): read udp [2a01:4f8:1c1c:eebf::1]:57442->[2a01:4f8:140:54e4::2]:53: i/o timeout.

#14
!

Unusual SOA timers

SOA · retry 2h should be shorter than refresh 1h. Current values: refresh 1h, retry 2h, expire 14d, negative TTL 10m.

#23
!

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 guug.de ›

Mail

fail

18 passed 4 warn 1 failed

Areas

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

Problems

✗

No DMARC record

DMARC · No DMARC record was found for this domain. DMARC is essential for preventing email spoofing. Add a DMARC record with p=reject or at least p=quarantine.

#5
!

Ends with ?all (neutral)

SPF · SPF record uses ?all (neutral), which gives no protection against unauthorized senders. Use -all or ~all instead.

#3
!

Not enabled

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

#8
!

Single MX host, no backup

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

#12
!

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 guug.de ›