SurfaceMap › w › webgo24.de

webgo24.de

Checked 2026-10-22 01:00 UTC · first added 2026-10-21
✗Problems found Score 63 of 100

Domain & DNS

warn

20 passed 4 warn 0 failed

Areas

iRegistration iDelegation !Nameservers !SOA !DNSSEC !Records

Problems

  • !
    Software version disclosed
    Nameservers · These nameservers report their software version via version.bind/version.server, which helps attackers find known vulnerabilities: ns1.webgo.de: "PowerDNS Authoritative Server 4.7.3"; ns2.webgo.de: "PowerDNS Authoritative Server 4.7.3"; ns3.webgo.de: "PowerDNS Authoritative Server 4.7.3"; ns4.webgo.de: "PowerDNS Authoritative Server 4.7.3". Hide or replace the version string.
    #17
  • !
    Unusual SOA timers
    SOA · negative caching TTL (minimum) 3m is outside 5m–1d (RFC 2308 recommends 1–3 hours). Current values: refresh 12h, retry 4h, expire 7d, negative TTL 3m.
    #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
  • !
    Very low TTLs
    Records · These records have a TTL below 5m, causing extra queries and slower lookups: A (3m), MX (3m), NS (3m). Low TTLs are useful just before a planned change. The NS TTL at the parent is 1d and in the zone 3m; resolvers may use either.
    #32

Recent checks

!

Full report

Domain & DNS report for webgo24.de ›

Mail

fail

15 passed 5 warn 1 failed

Areas

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

Problems

  • ✗
    No SPF record
    SPF · No SPF record was found for this domain. SPF is important for preventing email spoofing. Add an SPF record to specify which servers are authorized to send email for your domain.
    #6
  • !
    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
  • !
    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: website.webgo.de, website.webgo.de
    #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
  • !
    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 webgo24.de ›