SurfaceMap › y › ya.com

ya.com

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

Domain & DNS

warn

20 passed 5 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 at the parent: dns2.wanadoo.es; only in the zone: dns4.wanadoo.es. dns1.wanadoo.es, dns2.wanadoo.es, dns4.wanadoo.es report NS dns1.wanadoo.es dns4.wanadoo.es.
    #7
  • !
    No IPv6
    Delegation · None of the nameservers has an IPv6 address, so IPv6-only resolvers can't reach them.
    #13
  • !
    Software version disclosed
    Nameservers · These nameservers report their software version via version.bind/version.server, which helps attackers find known vulnerabilities: dns1.wanadoo.es: "Akamai ANSPremier 5.5.0.1"; dns2.wanadoo.es: "Akamai ANSPremier 5.5.0.1"; dns4.wanadoo.es: "Akamai ANSPremier 5.5.0.1". Hide or replace the version string.
    #17
  • !
    Unusual SOA timers
    SOA · refresh 5m is outside 20m–1d; retry 4h should be shorter than refresh 5m. Current values: refresh 5m, retry 4h, expire 7d, negative TTL 20m.
    #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 ya.com ›

Mail

fail

13 passed 5 warn 3 failed

Areas

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

Problems

  • ✗
    11 DNS lookups, over the limit of 10
    SPF · SPF record needs 11 DNS lookups (including nested includes), more than the limit of 10. Receivers will return a permerror; reduce includes or flatten the record.
    #2
  • ✗
    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 DKIM keys published
    DKIM · _domainkey.ya.com does not exist (NXDOMAIN), so no DKIM keys are published. DKIM helps prevent email spoofing. Configure DKIM with your email service provider.
    #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: mx.ya.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
  • !
    Reverse DNS does not match
    MX · The PTR name of these addresses does not resolve back to the same address: 62.36.20.73 -> 62.36.20.73.static.abi.uni2.es.
    #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 ya.com ›