SurfaceMap › r › renfe.com

renfe.com

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

Domain & DNS

fail

23 passed 3 warn 1 failed

Areas

iRegistration !Delegation ✗Nameservers ✓SOA !DNSSEC iRecords

Problems

  • ✗
    Nameservers not responding
    Nameservers · These addresses did not answer, so resolvers waste time on timeouts: dns1.renfe.es (213.144.49.35): read udp 46.225.38.91:60689->213.144.49.35:53: i/o timeout; dns2.renfe.es (213.144.49.43): read udp 46.225.38.91:60506->213.144.49.43:53: i/o timeout.
    #14
  • !
    NS sets differ
    Delegation · The nameservers at the parent and in the zone should be the same. Only in the zone: dns1.renfe.es, dns2.renfe.es. a1-90.akam.net, a13-65.akam.net, a22-66.akam.net, a24-67.akam.net, a7-64.akam.net, a8-65.akam.net report NS a1-90.akam.net a13-65.akam.net a22-66.akam.net a24-67.akam.net a7-64.akam.net a8-65.akam.net dns1.renfe.es dns2.renfe.es.
    #7
  • !
    Software version disclosed
    Nameservers · These nameservers report their software version via version.bind/version.server, which helps attackers find known vulnerabilities: a1-90.akam.net: "41824.4"; a1-90.akam.net: "41824.7"; a13-65.akam.net: "41824.4"; a13-65.akam.net: "41824.8"; a22-66.akam.net: "48878.27"; a22-66.akam.net: "48878.30"; a24-67.akam.net: "48878.30"; a24-67.akam.net: "48878.33"; a7-64.akam.net: "41824.11"; a7-64.akam.net: "41824.5"; a8-65.akam.net: "48878.26"; a8-65.akam.net: "48878.32". 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 renfe.com ›

Mail

warn

14 passed 4 warn 0 failed

Areas

✓SPF !DMARC !DKIM !DNSSEC !MX iBIMI

Problems

  • !
    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
  • !
    No MX records
    MX · No MX records found. If this domain is used for email, add MX records to specify mail servers. If it never receives mail, publish a null MX ("MX 0 .").
    #9
  • !
    No aggregate reports (rua)
    DMARC · DMARC record has no rua tag, so you receive no aggregate reports about who sends mail as your domain. Add rua=mailto:...
    #19

Recent checks

!

Full report

Mail report for renfe.com ›