pndsn.com

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

Posture Score: 74/100

Scanned May 29, 2026 at 1:16 PM UTC

Score History

Identity

Attack Surface

Reputation

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

External report destination not authorized: pubnub.com

The rua= URI sends reports to pubnub.com, but no authorization record exists at pndsn.com._report._dmarc.pubnub.com. Reports will be silently dropped by compliant receivers.

💡 Ask the owner of pubnub.com to publish a TXT record at pndsn.com._report._dmarc.pubnub.com containing 'v=DMARC1'.

high

External report destination not authorized: pubnub.com

The ruf= URI sends reports to pubnub.com, but no authorization record exists at pndsn.com._report._dmarc.pubnub.com. Reports will be silently dropped by compliant receivers.

💡 Ask the owner of pubnub.com to publish a TXT record at pndsn.com._report._dmarc.pubnub.com containing 'v=DMARC1'.

high

External DMARC report destination not authorized: pubnub.com

The rua= URI points to pubnub.com but no authorization record exists at pndsn.com._report._dmarc.pubnub.com.

💡 Ask the owner of pubnub.com to publish a TXT record at pndsn.com._report._dmarc.pubnub.com with 'v=DMARC1'.

medium

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.pndsn.com/.well-known/mta-sts.txt

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@pndsn.com").

low

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 (211 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

Subdomains protected (sp=quarantine)

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

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: pct, rf, ri

The DMARC record contains tags deprecated in DMARCbis: pct, rf, 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: 1655241267, Refresh: 3600s, Retry: 600s, Expire: 604800s, Min TTL: 300s

informational

Attack Surface Findings

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

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

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

informational

Wildcard DNS record detected

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

informational

Microsoft Autodiscover endpoint detected

The Autodiscover endpoint at autodiscover.pndsn.com responded with HTTP 404.

informational

Reputation Findings

Missing domain locks: clientDeleteProhibited

Domain pndsn.com is missing protective locks: clientDeleteProhibited.

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

high

Missing Strict-Transport-Security on pndsn.com

The Strict-Transport-Security header is not set on https://pndsn.com.

💡 Add the Strict-Transport-Security header with a max-age of at least 31536000 (1 year) and include the includeSubDomains directive.

medium

Missing Strict-Transport-Security on webmail.pndsn.com

The Strict-Transport-Security header is not set on https://webmail.pndsn.com.

💡 Add the Strict-Transport-Security header with a max-age of at least 31536000 (1 year) and include the includeSubDomains directive.

medium

Wildcard MX records detected

Domain pndsn.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

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://pndsn.com/.well-known/security.txt.

pass

TLS certificate valid for 61 days

Certificate for pndsn.com expires on 2026-07-30.

pass

Certificate issued by R13

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

pass

Signature algorithm: rsa-sha256

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

pass

RSA key: 2048 bits

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

pass

SCTs present in certificate

The certificate for pndsn.com contains Signed Certificate Timestamps.

pass

No weak ciphers detected

No known weak cipher suites detected on pndsn.com.

pass

Domain valid for 197 days

Domain pndsn.com expires on 2026-12-12.

pass

No disposable email provider MX records

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

pass

Domain is 3454 days old

Domain pndsn.com was registered 2016-12-12.

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

WHOIS registration data

Registrar: Amazon Registrar, Inc. | Created: 2016-12-12 | Expires: 2026-12-12 | Updated: 2026-05-14

informational

WHOIS privacy protection enabled

Domain pndsn.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: ndsn.com (has MX!), pdsn.com (has MX!), pnsn.com (has MX!), pndn.com (has MX!), ondsn.com (has MX!)

9 registered lookalike domain(s) that could be used for phishing against your brand. Showing top 5 of 9. 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: quarantine

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: quarantine

⚠️ 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: aspmx.l.google.com

PTR record proves mail server legitimacy

MX: aspmx.l.google.com Mail server at 209.85.203.27 → PTR Record Reverse DNS: dh-in-f27.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 Identity: alt2.aspmx.l.google.com

PTR record proves mail server legitimacy

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

Mail Server Identity: aspmx2.googlemail.com

PTR record proves mail server legitimacy

MX: aspmx2.googlemail.com Mail server at 173.194.76.27 → PTR Record Reverse DNS: ws-in-f27.1e100.net

Mail Server Identity: aspmx3.googlemail.com

PTR record proves mail server legitimacy

MX: aspmx3.googlemail.com Mail server at 142.250.102.27 → PTR Record Reverse DNS: rb-in-f27.1e100.net

Mail Server Reputation: aspmx.l.google.com