SurfaceMap › w › worldpay.com

worldpay.com

Checked 2026-10-22 11:33 UTC · first added 2026-10-21
!Passed with warnings Score 76 of 100

Domain & DNS

warn

23 passed 4 warn 0 failed

Areas

iRegistration iDelegation !Nameservers !SOA !DNSSEC !Records

Problems

  • !
    Software version disclosed
    Nameservers · These nameservers report their software version via version.bind/version.server, which helps attackers find known vulnerabilities: a1-135.akam.net: "41824.11"; a1-135.akam.net: "41824.9"; a11-66.akam.net: "41824.4"; a16-67.akam.net: "48878.31"; a16-67.akam.net: "48878.30"; a18-64.akam.net: "48878.32"; a26-65.akam.net: "48878.32"; a26-65.akam.net: "48878.27"; a7-66.akam.net: "41824.8"; a7-66.akam.net: "41824.4". Hide or replace the version string.
    #17
  • !
    Unusual SOA timers
    SOA · negative caching TTL (minimum) 1m is outside 5m–1d (RFC 2308 recommends 1–3 hours). Current values: refresh 3h, retry 1h, expire 28d, negative TTL 1m.
    #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
  • !
    Very low TTLs
    Records · These records have a TTL below 5m, causing extra queries and slower lookups: A (20s), AAAA (20s). Low TTLs are useful just before a planned change. The NS TTL at the parent is 2d and in the zone 10m; resolvers may use either.
    #32

Recent checks

!

Full report

Domain & DNS report for worldpay.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: mxa-00327201.gslb.pphosted.com, mxb-00327201.gslb.pphosted.com
    #11
  • !
    1024-bit DKIM key
    DKIM · 1024-bit RSA keys are the minimum and are considered weak today: 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 worldpay.com ›