SurfaceMap › l › lazaworx.com

lazaworx.com

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

Domain & DNS

warn

23 passed 3 warn 0 failed

Areas

iRegistration !Delegation !Nameservers ✓SOA !DNSSEC iRecords

Problems

  • !
    Glue differs from the zone
    Delegation · The addresses at the parent (glue) differ from the addresses in the zone: cns1.rackforest.com (glue 185.80.48.191, zone 185.80.48.191, 2a01:6ee0:1:0:80:48:191:1); cns2.rackforest.com (glue 185.43.204.31, zone 185.43.204.31, 2a01:6ee0::31). Update the glue at your registrar.
    #8
  • !
    Software version disclosed
    Nameservers · These nameservers report their software version via version.bind/version.server, which helps attackers find known vulnerabilities: cns1.rackforest.com: "PowerDNS Authoritative Server 5.1.4 (built Aug 10 2026 13:38:30 by root@bh-centos-8.dev.cpanel.net)"; cns2.rackforest.com: "PowerDNS Authoritative Server 5.1.4 (built Aug 10 2026 13:38:30 by root@bh-centos-8.dev.cpanel.net)". Hide or replace the version string.
    #17
  • !
    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 lazaworx.com ›

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
  • !
    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: mail.lazaworx.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
  • !
    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 lazaworx.com ›