Identity
54
D
kaspersky-labs.com
Posture Score: 68/100
Scanned May 27, 2026 at 7:20 PM UTC
Attack Surface
57
Reputation
92
Identity Findings
No MX records found
The domain has no MX records and cannot receive email.
💡 Publish MX records pointing to your mail server(s).
Subdomains have no DMARC enforcement
sp=none explicitly allows unauthenticated mail from subdomains.
💡 Add sp=reject (or sp=quarantine) to your DMARC record to protect subdomains.
No DKIM records found
No DKIM records were found after probing 56 common selectors. The domain may use a custom selector not discoverable via external scan.
💡 Configure DKIM signing and publish the public key at <selector>._domainkey.kaspersky-labs.com
DMARC policy is monitoring-only (p=none)
The p=none policy only monitors; it does not instruct receivers to quarantine or reject unauthenticated mail.
💡 Upgrade to p=quarantine or p=reject after reviewing aggregate reports.
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-labs.com/.well-known/mta-sts.txt
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.
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"
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-labs.com").
ARC check skipped — no MX records
Cannot assess ARC support without MX records.
Slow DNS response from ns3.kasperskylabs.org: 2253.4ms
The nameserver ns3.kasperskylabs.org responded in 2253.4ms, exceeding the 2000ms threshold.
💡 Investigate network latency or performance issues on ns3.kasperskylabs.org.
SPF record is valid
The SPF record is properly configured with valid syntax and within lookup limits.
SPF record length OK (29 bytes)
SPF record is within safe DNS packet size limits.
DKIM cryptographic configuration is compliant
No RFC 8301 compliance issues detected in DKIM key configuration.
All external report destinations authorized
External DMARC report destinations have valid authorization records per RFC 7489 §7.1.
No deprecated DMARCbis tags present
The DMARC record does not use any tags deprecated in DMARCbis (pct, rf, ri).
Meets bulk sender authentication requirements
Domain has SPF, DKIM, and DMARC — meeting Google/Yahoo 2024 bulk sender requirements for email authentication.
IPv6 readiness is good
IPv6 records are present and properly configured.
NS delegation is properly configured
All nameservers are responsive, consistent, and properly secured.
DNS TTL values follow best practices
All critical DNS record TTLs are within recommended ranges.
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.
DMARC alignment: adkim=r, aspf=r
DKIM alignment is relaxed, SPF alignment is relaxed.
DMARC failure reporting: fo=1
Failure reports generated when any authentication mechanism fails.
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.
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.
DANE check skipped — no MX records
Cannot check DANE/TLSA without MX records.
No BIMI record found
BIMI is not configured. Your brand logo will not display in supporting email clients.
Open relay check skipped — no MX records
Cannot test for open relay without MX records.
SMTP compliance check skipped — no MX records
Cannot test SMTP compliance without MX records.
Port exposure check skipped — no MX records
Cannot scan ports without MX records.
STARTTLS downgrade check skipped — no MX records
Cannot test STARTTLS without MX records.
RFC 8058 one-click unsubscribe assessment
No DKIM signing detected. RFC 8058 one-click unsubscribe requires DKIM-signed List-Unsubscribe headers.
FCrDNS check skipped — no MX records
Cannot perform FCrDNS without MX records.
SOA record parameters
Serial: 2026052726, Refresh: 7200s, Retry: 3600s, Expire: 8640000s, Min TTL: 3600s
Attack Surface Findings
Non-routable IPv4 in public DNS: 127.0.0.1
The A record for kaspersky-labs.com contains the non-routable IP address 127.0.0.1. This leaks internal network topology to the public internet.
💡 Implement split-horizon DNS so internal addresses are only served to internal clients. Remove non-routable IPs from public DNS.
Non-routable IPv4 in public DNS: git.kaspersky-labs.com → 10.73.35.4
The subdomain git.kaspersky-labs.com resolves to non-routable IP 10.73.35.4, leaking internal network information.
💡 Remove non-routable IPs from public DNS or implement split-horizon DNS.
Non-routable IPv4 in public DNS: jenkins.kaspersky-labs.com → 10.75.35.130
The subdomain jenkins.kaspersky-labs.com resolves to non-routable IP 10.75.35.130, leaking internal network information.
💡 Remove non-routable IPs from public DNS or implement split-horizon DNS.
Non-routable IPv4 in public DNS: grafana.kaspersky-labs.com → 10.70.112.21
The subdomain grafana.kaspersky-labs.com resolves to non-routable IP 10.70.112.21, leaking internal network information.
💡 Remove non-routable IPs from public DNS or implement split-horizon DNS.
Domain enumerability: medium
The domain has moderate enumerability. CT logs and DNS records reveal significant information about the domain structure.
💡 Restrict zone transfers, use NSEC3 instead of NSEC, consider wildcard certificates to reduce CT log exposure, and implement rate limiting on DNS queries.
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.
No MX records — A-record fallback active
The domain has no MX records but has an A record. Per RFC 5321, mail servers will attempt delivery to the A record IP. This domain may be silently accepting mail without SPF/DKIM/DMARC protection.
💡 If this domain should not receive mail, publish a Null MX record (RFC 7505): "0 ." as the MX. If it should receive mail, add proper MX records.
Non-mail domain SPF does not use -all
This domain has no MX but its SPF record does not end with -all (hard fail). Consider tightening to prevent spoofing.
💡 Change SPF to "v=spf1 -all" for domains that never send mail.
DNS ANY query returns 10 record(s)
The DNS server responds to ANY queries with 10 record(s). The low record count limits amplification risk, but ANY responses still aid reconnaissance.
💡 Configure the DNS server to refuse or minimize ANY query responses per RFC 8482.
No email autodiscovery endpoints detected
No Microsoft Autodiscover, Mozilla Autoconfig, or email SRV records were found.
8 subdomain(s) discovered for kaspersky-labs.com
Subdomains were enumerated via Certificate Transparency logs, DNS wordlist brute-forcing, and DNS record analysis.
0 certificate(s) found in CT logs
Certificate Transparency logs contain 0 certificate(s) for kaspersky-labs.com and its subdomains. Each certificate reveals subdomain names.
Reputation Findings
Missing domain locks: clientDeleteProhibited
Domain kaspersky-labs.com is missing protective locks: clientDeleteProhibited.
💡 Enable clientTransferProhibited and clientDeleteProhibited locks through your registrar to prevent unauthorized transfers or deletions.
Not listed on any DNS blacklists
Domain and MX IPs checked against 55 DNSBLs — no listings found.
HSTS enabled with preload on kaspersky-labs.com
Strict-Transport-Security: max-age=31536000; includeSubDomains; preload
security.txt present
Found security.txt at https://kaspersky-labs.com/.well-known/security.txt.
TLS certificate valid for 46 days
Certificate for kaspersky-labs.com expires on 2026-07-13.
Certificate issued by E8
The certificate for kaspersky-labs.com is issued by a third-party CA.
Signature algorithm: ecdsa-with-sha384
The certificate for kaspersky-labs.com uses an acceptable signature algorithm.
ECC key: 256 bits
The certificate for kaspersky-labs.com uses an adequate ECC key of 256 bits.
SCTs present in certificate
The certificate for kaspersky-labs.com contains Signed Certificate Timestamps.
No weak ciphers detected
No known weak cipher suites detected on kaspersky-labs.com.
Domain valid for 108 days
Domain kaspersky-labs.com expires on 2026-09-13.
No disposable email provider MX records
MX records for kaspersky-labs.com do not match known disposable email provider patterns.
Domain is 9753 days old
Domain kaspersky-labs.com was registered 1999-09-13.
No wildcard MX records
No wildcard MX records detected for kaspersky-labs.com.
TLD has good reputation
The .com TLD is not on known abuse watchlists.
DMARC reporting destinations look legitimate
DMARC rua/ruf addresses do not point to known URL shortener services.
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.
No abuse contacts resolved
Could not resolve abuse contact information for MX IPs via abusix.org.
PhishTank — API key required
PhishTank phishing database check requires an API key.
Sender Score — API key required
Sender Score reputation check requires an API key.
Cisco Talos — API key required
Cisco Talos IP reputation check requires an API key.
Could not connect to webmail.kaspersky-labs.com
HTTPS request to https://webmail.kaspersky-labs.com failed or timed out.
WHOIS registration data
Registrar: Regional Network Information Center, JSC dba RU-CENTER | Created: 1999-09-13 | Expires: 2026-09-13 | Updated: 2025-09-12
WHOIS privacy protection not detected
Domain kaspersky-labs.com does not appear to have WHOIS privacy protection. Registrant details may be publicly visible.
Bulletproof Hosting Detection — API key required
Checking IPs against known bulletproof hosting providers requires a threat intelligence API key.
Threat Intelligence Feeds — API key required
Checking domain against threat intelligence feeds requires API keys (e.g., VirusTotal, AbuseIPDB).
Typosquat detected: kaspersky-lab.com (has MX!), kasperskylabs.com
2 registered lookalike domain(s) that could be used for phishing against your brand. Domains with MX records can send and receive email, making them high-risk phishing vectors.
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: none
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: none
⚠️ DKIM signature is missing. DMARC relies on DKIM to verify email integrity and prevent tampering. Without DKIM, DMARC alignment will fail for cryptographic verification.
Enforced Encryption Chain
MTA-STS enforces TLS encryption to prevent man-in-the-middle attacks
TLS Support
TLS not verified or unsupported
→
MTA-STS Policy
MTA-STS not configured
⚠️ TLS support could not be verified. MTA-STS requires TLS to enforce encrypted connections. Without TLS, MTA-STS cannot function.
Brand Identity Chain
BIMI displays your logo in email clients, but requires DMARC enforcement
DMARC Enforcement
DMARC not enforced (p=none or missing)
→
BIMI Record
BIMI not configured
⚠️ DMARC is not enforced. BIMI requires a DMARC policy of "quarantine" or "reject" to prove you have strong email authentication. Without enforcement, email clients will not display your logo.
TLS Monitoring Chain
TLS-RPT provides reports about TLS connection failures
TLS Support
TLS not verified or unsupported
→
TLS-RPT Reporting
TLS-RPT not configured
⚠️ TLS support could not be verified. TLS-RPT reports on TLS connection failures, but without TLS support, there's nothing to monitor. You need working TLS encryption before TLS-RPT can provide value.
Security Checks
MX Records
✗
SPF Record
✓
DKIM Record
✗
DMARC Policy
✓
BIMI Record
✗
CAA Records
✗
DNSSEC
✗
MTA-STS
✗
TLS-RPT
✗
Embed Badge
Display your domain's security grade on your website or README:
<img src="https://scan.ractermx.com/badge/kaspersky-labs.com.svg" alt="Email Security Grade">
Want to re-scan this domain for updated results?
Scan kaspersky-labs.com Again