SurfaceMap › l › levante-emv.com

levante-emv.com

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

Domain & DNS

fail

23 passed 5 warn 1 failed

Areas

iRegistration !Delegation ✗Nameservers !SOA !DNSSEC iRecords

Problems

  • ✗
    No DNS over TCP
    Nameservers · DNS over TCP is required (RFC 7766); without it, large answers such as DNSSEC responses fail. Not answering over TCP: ns1.epi.es (213.0.95.2): dial tcp 213.0.95.2:53: connect: connection refused; ns1.epi.es (213.0.95.2): dial tcp 213.0.95.2:53: connect: connection refused; ns1.epi.es (213.0.95.2): dial tcp 213.0.95.2:53: connect: connection refused; ns1.epi.es (213.0.95.2): dial tcp 213.0.95.2:53: connect: connection refused; ns1.epi.es (213.0.95.2): dial tcp 213.0.95.2:53: connect: connection refused; ns1.epi.es (213.0.95.2): dial tcp 213.0.95.2:53: connect: connection refused; ns1.epi.es (213.0.95.2): dial tcp 213.0.95.2:53: connect: connection refused; ns1.epi.es (213.0.95.2): dial tcp 213.0.95.2:53: connect: connection refused; ns2.epi.es (213.4.119.2): dial tcp 213.4.119.2:53: connect: connection refused; ns2.epi.es (213.4.119.2): dial tcp 213.4.119.2:53: connect: connection refused; ns2.epi.es (213.4.119.2): dial tcp 213.4.119.2:53: connect: connection refused; ns2.epi.es (213.4.119.2): dial tcp 213.4.119.2:53: connect: connection refused; ns2.epi.es (213.4.119.2): dial tcp 213.4.119.2:53: connect: connection refused; ns2.epi.es (213.4.119.2): dial tcp 213.4.119.2:53: connect: connection refused; ns2.epi.es (213.4.119.2): dial tcp 213.4.119.2:53: connect: connection refused; ns2.epi.es (213.4.119.2): dial tcp 213.4.119.2:53: connect: connection refused; ns3.prensaiberica.net (34.175.122.60): dial tcp 34.175.122.60:53: i/o timeout; ns4.prensaiberica.net (34.175.171.102): dial tcp 34.175.171.102:53: i/o timeout.
    #19
  • !
    NS sets differ
    Delegation · The nameservers at the parent and in the zone should be the same. Only at the parent: ns3.prensaiberica.net, ns4.prensaiberica.net. ns1.epi.es, ns2.epi.es, ns3.prensaiberica.net, ns4.prensaiberica.net report NS ns1.epi.es ns2.epi.es.
    #7
  • !
    No IPv6
    Delegation · None of the nameservers has an IPv6 address, so IPv6-only resolvers can't reach them.
    #13
  • !
    No EDNS
    Nameservers · These nameservers don't support EDNS(0), needed for DNSSEC and answers larger than 512 bytes: ns1.epi.es (213.0.95.2), ns1.epi.es (213.0.95.2), ns1.epi.es (213.0.95.2), ns1.epi.es (213.0.95.2), ns1.epi.es (213.0.95.2), ns1.epi.es (213.0.95.2), ns1.epi.es (213.0.95.2), ns1.epi.es (213.0.95.2), ns2.epi.es (213.4.119.2), ns2.epi.es (213.4.119.2), ns2.epi.es (213.4.119.2), ns2.epi.es (213.4.119.2), ns2.epi.es (213.4.119.2), ns2.epi.es (213.4.119.2), ns2.epi.es (213.4.119.2), ns2.epi.es (213.4.119.2), ns3.prensaiberica.net (34.175.122.60), ns4.prensaiberica.net (34.175.171.102).
    #20
  • !
    Serials differ
    SOA · The nameservers serve different versions of the zone: 1792508549 on ns1.epi.es (213.0.95.2), ns1.epi.es (213.0.95.2), ns1.epi.es (213.0.95.2), ns1.epi.es (213.0.95.2), ns1.epi.es (213.0.95.2), ns2.epi.es (213.4.119.2), ns2.epi.es (213.4.119.2), ns2.epi.es (213.4.119.2), ns2.epi.es (213.4.119.2), ns2.epi.es (213.4.119.2); 1792508550 on ns1.epi.es (213.0.95.2), ns1.epi.es (213.0.95.2), ns1.epi.es (213.0.95.2), ns2.epi.es (213.4.119.2), ns2.epi.es (213.4.119.2), ns2.epi.es (213.4.119.2); 1792508587 on ns3.prensaiberica.net (34.175.122.60); 1792508591 on ns4.prensaiberica.net (34.175.171.102). 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 levante-emv.com ›

Mail

warn

25 passed 4 warn 0 failed

Areas

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

Problems

  • !
    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.renr.es
    #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 levante-emv.com ›