SurfaceMap › h › hogeschoolrotterdam.nl

hogeschoolrotterdam.nl

Checked 2026-10-21 21:21 UTC · first added 2026-10-21
!Check could not complete

Domain & DNS

error

25 passed 1 warn 2 failed 1 errors

lookups failed for rdap; results are incomplete

Areas

iRegistration ✗Delegation ✗Nameservers iSOA ✓DNSSEC ✓Records

Problems

  • ✗
    Nameserver names don't resolve
    Delegation · These nameservers have no A or AAAA record, so they can't be reached (lame delegation): dns-03.hro.nl.
    #9
  • ✗
    Nameservers not responding
    Nameservers · These addresses did not answer, so resolvers waste time on timeouts: tasarov.hro.nl (46.19.32.138): read udp 46.225.38.91:34269->46.19.32.138:53: read: connection refused; tasarov.hro.nl (2a02:2770:3:0:21a:4aff:fece:8edf): read udp [2a01:4f8:1c1c:eebf::1]:52009->[2a02:2770:3:0:21a:4aff:fece:8edf]:53: read: connection refused.
    #14
  • !
    NS sets differ
    Delegation · The nameservers at the parent and in the zone should be the same. Only at the parent: dns-03.hro.nl; only in the zone: tasarov.hro.nl. dns-01.hro.nl, dns-02.hro.nl report NS dns-01.hro.nl dns-02.hro.nl tasarov.hro.nl.
    #7

Recent checks

!

Full report

Domain & DNS report for hogeschoolrotterdam.nl ›

Mail

fail

22 passed 6 warn 1 failed

Areas

iSPF ✗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
  • !
    Hosts without IPv6
    MX · The following MX hosts could not be resolved to IPv6 addresses: suffix05.hro.nl, suffix06.hro.nl
    #11
  • !
    Signatures expire in 79h0m0s
    DNSSEC · DNSKEY signatures expire at 2026-10-25T04:45:03Z (in 79h0m0s). Check that re-signing works.
    #21
  • !
    1024-bit DKIM key
    DKIM · 1024-bit RSA keys are the minimum and are considered weak today: mail (1024 bits). Rotate to a 2048-bit key.
    #23
  • !
    Report address not authorized
    DMARC · These report addresses are in another domain that has not agreed to receive your reports, so receivers will not send them: mailto:dmarc-reports@hr.nl (needs hogeschoolrotterdam.nl._report._dmarc.hr.nl). Ask the report provider to publish the record, or check the address.
    #29
  • !
    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
  • !
    Not configured
    TLS · MTA-STS or DANE is used without TLS-RPT, so you get no reports when senders fail to deliver because of TLS problems. Publish _smtp._tls TXT "v=TLSRPTv1; rua=mailto:...".
    #35

Recent checks

✗

Full report

Mail report for hogeschoolrotterdam.nl ›