SurfaceMap › w › webgarden.com

webgarden.com

Checked 2026-10-22 11:24 UTC · first added 2026-10-21
✗Problems found Score 50 of 100

Domain & DNS

warn

24 passed 4 warn 0 failed

Areas

iRegistration !Delegation !Nameservers ✓SOA !DNSSEC iRecords

Problems

  • !
    NS sets differ
    Delegation · The nameservers at the parent and in the zone should be the same. Only in the zone: ns4.gransy.com, ns5.gransy.com. ns.gransy.com, ns2.gransy.com, ns3.gransy.com, ns4.gransy.com, ns5.gransy.com report NS ns.gransy.com ns2.gransy.com ns3.gransy.com ns4.gransy.com ns5.gransy.com.
    #7
  • !
    Software version disclosed
    Nameservers · These nameservers report their software version via version.bind/version.server, which helps attackers find known vulnerabilities: ns.gransy.com: "GLUX-DNS 0.9.2"; ns2.gransy.com: "GLUX-DNS 0.9.2"; ns3.gransy.com: "GLUX-DNS 0.9.2"; ns4.gransy.com: "GLUX-DNS 0.9.2"; ns5.gransy.com: "GLUX-DNS 0.9.2". Hide or replace the version string.
    #17
  • !
    Signed but not delegated securely
    DNSSEC · The zone is signed but the parent has no DS record, so the signatures are not used. Publish the DS record at your registrar.
    #27
  • !
    Deprecated algorithm
    DNSSEC · SHA-1 based algorithms are deprecated and rejected by some validators: RSASHA1-NSEC3-SHA1 (7). Roll over to ECDSAP256SHA256 (13).
    #29

Recent checks

!

Full report

Domain & DNS report for webgarden.com ›

Mail

fail

7 passed 6 warn 2 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
  • ✗
    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
  • !
    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
  • !
    Signed, but no DS at parent
    DNSSEC · The zone is signed (DNSKEY present) but the parent has no DS record, so the chain of trust is incomplete. Publish the DS record at your registrar.
    #8
  • !
    Hosts without IPv6
    MX · The following MX hosts could not be resolved to IPv6 addresses: mx.webgarden.com
    #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
  • !
    Addresses without reverse DNS
    MX · These MX addresses have no PTR record, which many receivers treat as a spam signal: 78.24.14.149 (mx.webgarden.com). Ask your hosting provider to set one.
    #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 webgarden.com ›