revolve.com

Nameservers · These nameservers report their software version via version.bind/version.server, which helps attackers find known vulnerabilities: a1-123.akam.net: "41824.4"; a1-123.akam.net: "41824.7"; a10-66.akam.net: "48878.33"; a10-66.akam.net: "48878.27"; a3-64.akam.net: "41824.5"; a3-64.akam.net: "41824.9"; a4-67.akam.net: "48878.32"; a4-67.akam.net: "48878.31"; a6-66.akam.net: "48878.27"; a6-66.akam.net: "48878.31"; a9-66.akam.net: "41824.10"; a9-66.akam.net: "41824.5". Hide or replace the version string.

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.

DMARC · DMARC policy is set to 'quarantine'. Consider upgrading to 'reject' for stronger protection once you've verified legitimate emails are passing authentication.

DNSSEC · DNSSEC is not enabled for this domain. Consider enabling DNSSEC to protect against DNS spoofing attacks.

DKIM · 1024-bit RSA keys are the minimum and are considered weak today: dkim (1024 bits), mail (1024 bits), k1 (1024 bits), google (1024 bits), s2 (1024 bits). Rotate to a 2048-bit key.

DMARC · These report addresses are in another domain that has not agreed to receive your reports, so receivers will not send them: mailto:devops.notification@revolveclothing.com (needs revolve.com._report._dmarc.revolveclothing.com). Ask the report provider to publish the record, or check the address.

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.