mixpanel.com

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

Posture Score: 73/100

Scanned May 27, 2026 at 7:41 PM UTC

Identity

Attack Surface

Reputation

100

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).

critical

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

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

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

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

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

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

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

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

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.

high

Subdomain policy (sp=none) is weaker than domain policy (p=reject)

The subdomain policy is less restrictive than the organizational domain policy, leaving subdomains more vulnerable.

💡 Set sp=reject or remove sp= to inherit the domain policy.

medium

TLS-RPT report destination unreachable

The TLS-RPT rua= URI points to an external domain that does not resolve. TLS failure reports will not be delivered.

💡 Verify the TLS-RPT rua= address is correct and the destination domain is active.

medium

SOA expire value too short

The SOA expire value is 259200s (<604,800s / 7 days). Secondary nameservers may stop serving the zone prematurely.

💡 Increase the SOA expire value to at least 604800 seconds (7 days).

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

ARC check skipped — no MX records

Cannot assess ARC support without MX records.

low

SPF record is valid

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

pass

SPF record length OK (161 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

MTA-STS and TLS-RPT are properly configured

MTA-STS policy is enforced and TLS reporting is configured.

pass

Meets bulk sender authentication requirements

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

pass

IPv6 readiness is good

IPv6 records are present and properly configured.

pass

NS delegation is properly configured

All nameservers are responsive, consistent, and properly secured.

pass

DNS responses are consistent across all nameservers

All authoritative nameservers return consistent answers with proper AA flags.

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=1

Failure reports generated when any authentication mechanism fails.

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

Deprecated DMARCbis tags found: ri

The DMARC record contains tags deprecated in DMARCbis: ri. Consider removing these for forward compatibility.

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

DANE check skipped — no MX records

Cannot check DANE/TLSA without MX records.

informational

No BIMI record found

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

informational

Open relay check skipped — no MX records

Cannot test for open relay without MX records.

informational

SMTP compliance check skipped — no MX records

Cannot test SMTP compliance without MX records.

informational

Port exposure check skipped — no MX records

Cannot scan ports without MX records.

informational

STARTTLS downgrade check skipped — no MX records

Cannot test STARTTLS without MX records.

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

FCrDNS check skipped — no MX records

Cannot perform FCrDNS without MX records.

informational

SOA record parameters

Serial: 2021042726, Refresh: 21600s, Retry: 3600s, Expire: 259200s, Min TTL: 300s

informational

Attack Surface Findings

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.

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

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

No internal information leakage detected

No non-routable IP addresses or internal references were found in public DNS records.

pass

No excessive DNS information exposure detected

No HINFO, LOC, RP records, version disclosures, or zone walking vulnerabilities were found.

pass

No email autodiscovery endpoints detected

No Microsoft Autodiscover, Mozilla Autoconfig, or email SRV records were found.

pass

8 subdomain(s) discovered for mixpanel.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 mixpanel.com and its subdomains. Each certificate reveals subdomain names.

informational

Reputation Findings

Not listed on any DNS blacklists

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

pass

HSTS enabled with preload on mixpanel.com

Strict-Transport-Security: max-age=63072000; includeSubDomains; preload

pass

security.txt present

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

pass

TLS certificate valid for 231 days

Certificate for mixpanel.com expires on 2027-01-13.

pass

Certificate issued by GeoTrust TLS RSA CA G1

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

pass

Signature algorithm: rsa-sha256

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

pass

RSA key: 2048 bits

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

pass

SCTs present in certificate

The certificate for mixpanel.com contains Signed Certificate Timestamps.

pass

No weak ciphers detected

No known weak cipher suites detected on mixpanel.com.

pass

Domain valid for 289 days

Domain mixpanel.com expires on 2027-03-13.

pass

Domain transfer and delete locks enabled

Domain mixpanel.com has clientTransferProhibited and clientDeleteProhibited locks.

pass

No disposable email provider MX records

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

pass

Domain is 7015 days old

Domain mixpanel.com was registered 2007-03-13.

pass

No wildcard MX records

No wildcard MX records detected for mixpanel.com.

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 (aspmx.l.google.com) uses TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 including Forward Secrecy.

pass

SMTP banner from hosted mail provider

The MX (aspmx.l.google.com) is a hosted mail service. Banner alignment is managed by the provider and not actionable by the domain owner.

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.mixpanel.com

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

informational

WHOIS registration data

Registrar: Squarespace Domains II LLC | Created: 2007-03-13 | Expires: 2027-03-13 | Updated: 2026-02-26

informational

WHOIS privacy protection enabled

Domain mixpanel.com has WHOIS privacy/redaction enabled.

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: ixpanel.com (has MX!), mxpanel.com (has MX!), mipanel.com (has MX!), nixpanel.com (has MX!), mispanel.com (has MX!)

10 registered lookalike domain(s) that could be used for phishing against your brand. Showing top 5 of 10. 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: alt3.aspmx.l.google.com

PTR record proves mail server legitimacy

MX: alt3.aspmx.l.google.com Mail server at 192.178.213.26 → PTR Record Reverse DNS: yugrqzs-in-f26.1e100.net

Mail Server Identity: alt4.aspmx.l.google.com

PTR record proves mail server legitimacy

MX: alt4.aspmx.l.google.com Mail server at 142.251.127.27 → PTR Record Reverse DNS: lcfrai-in-f27.1e100.net

Mail Server Identity: aspmx.l.google.com

PTR record proves mail server legitimacy

MX: aspmx.l.google.com Mail server at 74.125.193.26 → PTR Record Reverse DNS: di-in-f26.1e100.net

Mail Server Identity: alt2.aspmx.l.google.com

PTR record proves mail server legitimacy

MX: alt2.aspmx.l.google.com Mail server at 142.250.102.26 → PTR Record Reverse DNS: rb-in-f26.1e100.net

Mail Server Identity: alt1.aspmx.l.google.com

PTR record proves mail server legitimacy

MX: alt1.aspmx.l.google.com Mail server at 173.194.76.27 → PTR Record Reverse DNS: ws-in-f27.1e100.net

Mail Server Reputation: alt3.aspmx.l.google.com