SurfaceMap › i › infor.com

infor.com

Checked 2026-10-22 09:20 UTC · first added 2026-10-21
!Passed with warnings Score 82 of 100

Domain & DNS

warn

31 passed 1 warn 0 failed

Areas

iRegistration iDelegation ✓Nameservers ✓SOA iDNSSEC !Records

Problems

  • !
    Very low TTLs
    Records · These records have a TTL below 5m, causing extra queries and slower lookups: A (1m). Low TTLs are useful just before a planned change.
    #32

Recent checks

!

Full report

Domain & DNS report for infor.com ›

Mail

warn

26 passed 5 warn 0 failed

Areas

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

Problems

  • !
    Hosts without IPv6
    MX · The following MX hosts could not be resolved to IPv6 addresses: mx1.hc3692-74.iphmx.com, mx2.hc3692-74.iphmx.com, cloudironport.infor.com
    #11
  • !
    Signatures expire in 9h0m0s
    DNSSEC · DNSKEY signatures expire at 2026-10-22T18:00:00Z (in 9h0m0s). Check that re-signing works.
    #21
  • !
    Hosts are CNAMEs
    MX · MX records must point to a host name with A/AAAA records, not to a CNAME: cloudironport.infor.com -> mx1.hc3692-74.iphmx.com
    #22
  • !
    1024-bit DKIM key
    DKIM · 1024-bit RSA keys are the minimum and are considered weak today: k1 (1024 bits), s2 (1024 bits). Rotate to a 2048-bit key.
    #23
  • !
    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 infor.com ›