kaspersky.com

Name: kaspersky.com Email Security Posture Assessment
Creator: RacterMX
License: https://creativecommons.org/licenses/by-nc/4.0/

Posture Score: 61/100

Scanned May 27, 2026 at 1:58 PM UTC

Identity

Attack Surface

Reputation

Identity Findings

No NS records found

No nameserver records could be retrieved for this domain.

💡 Ensure NS records are properly configured at your registrar and in your zone file.

critical

Weak DKIM RSA key (~1296 bits) for selector 'k1'

RSA keys shorter than 2048 bits are considered weak. Current key is approximately 1296 bits.

💡 Generate a new 2048-bit (or larger) RSA key pair and update the DKIM record.

high

No STARTTLS support on mx12.kaspersky-labs.com:25

The mail server does not advertise STARTTLS, meaning email is transmitted in plaintext.

💡 Enable STARTTLS on the mail server.

high

No STARTTLS support on mx9.kaspersky-labs.com:25

The mail server does not advertise STARTTLS, meaning email is transmitted in plaintext.

💡 Enable STARTTLS on the mail server.

high

No STARTTLS support on mx14.kaspersky-labs.com:25

The mail server does not advertise STARTTLS, meaning email is transmitted in plaintext.

💡 Enable STARTTLS on the mail server.

high

No STARTTLS support on mx11.kaspersky-labs.com:25

The mail server does not advertise STARTTLS, meaning email is transmitted in plaintext.

💡 Enable STARTTLS on the mail server.

high

No STARTTLS support on mx13.kaspersky-labs.com:25

The mail server does not advertise STARTTLS, meaning email is transmitted in plaintext.

💡 Enable STARTTLS on the mail server.

high

Cannot check DNS consistency — no NS records

No nameserver records could be retrieved for consistency checking.

💡 Ensure NS records are properly configured.

high

No MTA-STS record found

Without MTA-STS, mail transport encryption cannot be enforced and is vulnerable to downgrade attacks.

💡 Publish a _mta-sts TXT record and host a policy file at https://mta-sts.kaspersky.com/.well-known/mta-sts.txt

medium

STARTTLS without MTA-STS or DANE protection

STARTTLS alone is vulnerable to downgrade attacks. Neither MTA-STS nor DANE is configured to enforce encryption.

💡 Deploy MTA-STS and/or DANE to protect against STARTTLS stripping attacks.

medium

SOA MNAME is not authoritative

The primary nameserver (MNAME) 'dnsmaster.kasperskylabs.net' does not return authoritative answers.

💡 Update the MNAME field to point to an authoritative nameserver for this zone.

medium

No CAA records found

No CAA records are configured. Any certificate authority can issue certificates for this domain.

💡 Add CAA records to restrict certificate issuance. Example: 0 issue "letsencrypt.org"

medium

No TLS-RPT record found

Without TLS-RPT, you will not receive reports about TLS negotiation failures.

💡 Publish a _smtp._tls TXT record (e.g. "v=TLSRPTv1; rua=mailto:tls-reports@kaspersky.com").

low

SPF record is valid

The SPF record is properly configured with valid syntax and within lookup limits.

pass

SPF record length OK (123 bytes)

SPF record is within safe DNS packet size limits.

pass

DKIM cryptographic configuration is compliant

No RFC 8301 compliance issues detected in DKIM key configuration.

pass

DKIM key strength indicates modern key management

All DKIM keys use RSA-2048+ or Ed25519, consistent with current best practices.

pass

No external DMARC report destinations

All DMARC report URIs point to the same domain — no external authorization needed.

pass

Subdomains protected (sp=reject)

DMARC subdomain policy enforces quarantine or reject on unauthenticated subdomain mail.

pass

No deprecated DMARCbis tags present

The DMARC record does not use any tags deprecated in DMARCbis (pct, rf, ri).

pass

ARC support likely available

MX server software appears to support ARC headers for authentication preservation.

pass

Meets bulk sender authentication requirements

Domain has SPF, DKIM, and DMARC — meeting Google/Yahoo 2024 bulk sender requirements for email authentication.

pass

SMTP security checks passed

No open relay, VRFY/EXPN, or banner disclosure issues detected.

pass

SMTP RFC 5321 compliance checks passed

The mail server accepts postmaster@ and abuse@ and uses a valid FQDN in EHLO.

pass

DNS TTL values follow best practices

All critical DNS record TTLs are within recommended ranges.

pass

DKIM2 not detected

No DKIM key record with v=2 was found across common selectors. DKIM2 is an emerging standard and not yet widely deployed.

informational

DMARC alignment: adkim=r, aspf=r

DKIM alignment is relaxed, SPF alignment is relaxed.

informational

DMARC failure reporting: fo=0

Failure reports generated when all authentication mechanisms fail.

informational

DMARCbis np tag absent

The DMARC record does not include the np (non-existent subdomain policy) tag. Consider adding np=reject to protect non-existent subdomains under DMARCbis.

informational

DMARCbis psd tag absent

The DMARC record does not include the psd (public suffix domain) indicator. Consider adding psd=n to explicitly identify this as an organizational domain.

informational

REQUIRETLS not advertised

The primary MX does not advertise REQUIRETLS (RFC 8689). This is an emerging standard — MTA-STS and DANE provide adequate TLS enforcement for most deployments.

informational

No DANE/TLSA records found

DANE is not configured for any MX server. This is optional but provides strong certificate binding.

informational

No BIMI record found

BIMI is not configured. Your brand logo will not display in supporting email clients.

informational

Open mail ports on mx12.kaspersky-labs.com

Detected open mail-related ports: 25

informational

Domain is IPv4-only

No AAAA records found for the domain, MX servers, or nameservers. The domain operates on IPv4 only.

informational

RFC 8058 one-click unsubscribe assessment

DKIM signing is configured. RFC 8058 compliance depends on List-Unsubscribe and List-Unsubscribe-Post headers being included in outbound messages and DKIM signatures.

informational

MX IP network diversity

MX IPs span 4 different /16 networks, providing good diversity.

informational

SOA record parameters

Serial: 2026052710, Refresh: 7200s, Retry: 3600s, Expire: 8640000s, Min TTL: 3600s

informational

Attack Surface Findings

Non-routable IPv4 in public DNS: ftp.kaspersky.com → 127.0.0.1

The subdomain ftp.kaspersky.com resolves to non-routable IP 127.0.0.1, leaking internal network information.

💡 Remove non-routable IPs from public DNS or implement split-horizon DNS.

high

DNS ANY query returns 33 record(s)

The DNS server responds to ANY queries with 33 record(s), creating significant DNS amplification risk.

💡 Configure the DNS server to refuse or minimize ANY query responses per RFC 8482.

medium

DNSSEC is not enabled

No DNSKEY or DS records were found. DNS responses are not cryptographically authenticated.

💡 Enable DNSSEC by generating DNSKEY records and publishing DS records at the registrar.

medium

Domain enumerability: low

The domain has low enumerability. Proper NSEC3 configuration and limited CT exposure reduce the attack surface.

low

All MX records resolve correctly

No dangling MX records detected — all MX hostnames resolve to valid IP addresses.

pass

Explicit MX records present

The domain has explicit MX records — no implicit A-record fallback delivery.

pass

13 subdomain(s) discovered for kaspersky.com

Subdomains were enumerated via Certificate Transparency logs, DNS wordlist brute-forcing, and DNS record analysis.

informational

0 certificate(s) found in CT logs

Certificate Transparency logs contain 0 certificate(s) for kaspersky.com and its subdomains. Each certificate reveals subdomain names.

informational

Wildcard DNS record detected

A wildcard DNS record exists for *.kaspersky.com, resolving to 93.159.228.22. Wildcard records make subdomain brute-forcing less effective but may mask misconfigurations.

informational

Mozilla Autoconfig endpoint detected

The Autoconfig endpoint at autoconfig.kaspersky.com is publicly accessible.

informational

Reputation Findings

Missing domain locks: clientDeleteProhibited

Domain kaspersky.com is missing protective locks: clientDeleteProhibited.

💡 Enable clientTransferProhibited and clientDeleteProhibited locks through your registrar to prevent unauthorized transfers or deletions.

high

Wildcard MX records detected

Domain kaspersky.com has wildcard MX records, which can be abused for spam or phishing.

💡 Remove wildcard MX records and configure explicit MX entries only for legitimate mail-handling subdomains.

medium

HSTS enabled but missing preload directive on kaspersky.com

Strict-Transport-Security: max-age=31536000; includeSubDomains

💡 Add the "preload" directive to the HSTS header and submit the domain to hstspreload.org.

low

Not listed on any DNS blacklists

Domain and MX IPs checked against 55 DNSBLs — no listings found.

pass

security.txt present

Found security.txt at https://kaspersky.com/.well-known/security.txt.

pass

TLS certificate valid for 268 days

Certificate for kaspersky.com expires on 2027-02-19.

pass

Certificate issued by DigiCert Global G2 TLS RSA SHA256 2020 CA1

The certificate for kaspersky.com is issued by a third-party CA.

pass

Signature algorithm: rsa-sha256

The certificate for kaspersky.com uses an acceptable signature algorithm.

pass

RSA key: 2048 bits

The certificate for kaspersky.com uses an adequate RSA key of 2048 bits.

pass

SCTs present in certificate

The certificate for kaspersky.com contains Signed Certificate Timestamps.

pass

No weak ciphers detected

No known weak cipher suites detected on kaspersky.com.

pass

Domain valid for 133 days

Domain kaspersky.com expires on 2026-10-08.

pass

No disposable email provider MX records

MX records for kaspersky.com do not match known disposable email provider patterns.

pass

Domain is 10457 days old

Domain kaspersky.com was registered 1997-10-09.

pass

TLD has good reputation

The .com TLD is not on known abuse watchlists.

pass

DMARC reporting destinations look legitimate

DMARC rua/ruf addresses do not point to known URL shortener services.

pass

MX records point to stable infrastructure

No MX records point to known dynamic DNS service domains.

pass

Strong TLS configuration on primary MX

Primary MX (mx11.kaspersky-labs.com) uses with cipher including Forward Secrecy.

pass

Google Safe Browsing DNS check — no flag detected

DNS-based Safe Browsing lookup returned no results. Full verification requires the Google Safe Browsing API key.

informational

Abuse contacts found for MX IPs

Abuse contact information retrieved via abusix.org DNS lookup.

informational

PhishTank — API key required

PhishTank phishing database check requires an API key.

informational

Sender Score — API key required

Sender Score reputation check requires an API key.

informational

Cisco Talos — API key required

Cisco Talos IP reputation check requires an API key.

informational

Could not connect to webmail.kaspersky.com

HTTPS request to https://webmail.kaspersky.com failed or timed out.

informational

WHOIS registration data

Registrar: Regional Network Information Center, JSC dba RU-CENTER | Created: 1997-10-09 | Expires: 2026-10-08 | Updated: 2025-10-07

informational

WHOIS privacy protection not detected

Domain kaspersky.com does not appear to have WHOIS privacy protection. Registrant details may be publicly visible.

informational

Bulletproof Hosting Detection — API key required

Checking IPs against known bulletproof hosting providers requires a threat intelligence API key.

informational

Threat Intelligence Feeds — API key required

Checking domain against threat intelligence feeds requires API keys (e.g., VirusTotal, AbuseIPDB).

informational

Typosquat detected: kspersky.com (has MX!), kasersky.com (has MX!), kaspersk.com (has MX!), kaspresky.com (has MX!), kaspesrky.com (has MX!)

11 registered lookalike domain(s) that could be used for phishing against your brand. Showing top 5 of 11. Domains with MX records can send and receive email, making them high-risk phishing vectors.

informational

Dependency Chains

DMARC Authentication Chain (SPF)

DMARC uses SPF to verify that emails come from authorized servers

SPF Record SPF record found and configured → DMARC Policy DMARC policy: reject

DMARC Authentication Chain (DKIM)

DMARC uses DKIM to verify that emails have not been tampered with

DKIM Signature DKIM signature missing → DMARC Policy DMARC policy: reject

⚠️ DKIM signature is missing. DMARC relies on DKIM to verify email integrity and prevent tampering. Without DKIM, DMARC alignment will fail for cryptographic verification.

Mail Server Identity: mx12.kaspersky-labs.com

PTR record proves mail server legitimacy

MX: mx12.kaspersky-labs.com Mail server at 91.103.66.155 → PTR Record Reverse DNS: mx12.kaspersky-labs.com

Mail Server Identity: mx9.kaspersky-labs.com

PTR record proves mail server legitimacy

MX: mx9.kaspersky-labs.com Mail server at 195.122.169.44 → PTR Record Reverse DNS: 44.0-63.169.122.195.in-addr.arpa

Mail Server Identity: mx14.kaspersky-labs.com

PTR record proves mail server legitimacy

MX: mx14.kaspersky-labs.com Mail server at 93.159.230.123 → PTR Record Reverse DNS: mx14.kaspersky-labs.com

Mail Server Identity: mx11.kaspersky-labs.com

PTR record proves mail server legitimacy

MX: mx11.kaspersky-labs.com Mail server at 81.19.104.122 → PTR Record Reverse DNS: mx11.kaspersky-labs.com

Mail Server Identity: mx13.kaspersky-labs.com

PTR record proves mail server legitimacy

MX: mx13.kaspersky-labs.com Mail server at 91.103.66.164 → PTR Record Reverse DNS: mx13.kaspersky-labs.com

Mail Server Reputation: mx12.kaspersky-labs.com