SurfaceMap › v › vrs.de

vrs.de

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

Domain & DNS

warn

22 passed 2 warn 0 failed

Areas

iRegistration iDelegation ✓Nameservers !SOA !DNSSEC iRecords

Problems

  • !
    Serials differ
    SOA · The nameservers serve different versions of the zone: 2026091401 on dns3.netcologne.de (213.196.239.187), dns3.netcologne.de (2001:4dd0:100:1029:53:3:0:3), dns4.netcologne.de (195.14.247.116), dns4.netcologne.de (2001:4dd0:100:4220:53:4:0:4), dns5.netcologne.de (134.95.100.211); 2026101600 on dns11.netcologne.de (134.0.30.178), dns11.netcologne.de (2a03:2900:3:1::2), dns12.netcologne.de (194.50.113.2), dns12.netcologne.de (2001:4d8f:2::2), dns13.netcologne.de (194.126.196.2), dns13.netcologne.de (2a03:2902:3:1::2), dns14.netcologne.de (185.11.139.126). This is normal for a few minutes after a change; if it lasts, zone transfers to the secondaries are failing.
    #22
  • !
    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 vrs.de ›

Mail

fail

19 passed 5 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: vrs.in.tmes.trendmicro.eu
    #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
  • !
    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 vrs.de ›