← Back to Scanner

averydennison.com

Name: averydennison.com Email Security Posture Assessment
Creator: RacterMX

Posture Score: 62/100

Scanned May 17, 2026 at 6:07 PM UTC

Identity

Attack Surface

Reputation

Identity Findings

Overly broad CIDR range: 144.93.0.0/16

The /16 CIDR block authorizes a very large IP range to send email as this domain.

💡 Narrow the IP range to only the specific servers that send email.

high

Overly broad CIDR range: 147.121.0.0/16

The /16 CIDR block authorizes a very large IP range to send email as this domain.

💡 Narrow the IP range to only the specific servers that send email.

high

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

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

MX hostname does not resolve: ms30228538.msv1.invalid

The MX hostname has no A or AAAA records.

💡 Ensure the MX hostname resolves to a valid IP address.

high

No STARTTLS support on ms30228538.msv1.invalid

The mail server does not support STARTTLS. All email is transmitted in plaintext.

💡 Enable STARTTLS on the mail server.

high

NS delegation mismatch

The registrar-delegated nameservers do not match the zone NS records.

💡 Update either the registrar NS delegation or the zone NS records to match.

high

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

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

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

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

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

low

SPF has ip4 mechanisms but no ip6

The SPF record authorizes IPv4 addresses but not IPv6. Your MX servers have AAAA records, so IPv6 mail delivery is possible without SPF authorization.

💡 Add ip6: mechanisms to the SPF record for your IPv6 mail server addresses.

low

Shared IP 142.250.102.26 used by multiple MX servers

The IP 142.250.102.26 is shared across 2 MX hostnames, reducing redundancy.

💡 Use unique IP addresses for each MX server for better redundancy.

low

Very low TTL on TXT records: 39s

26 TXT records have a TTL of 39s or less (below 300s).

💡 Increase the TTL to at least 300 seconds unless frequent changes are expected.

low

Very low TTL on SPF record: 39s

The SPF record has a TTL of 39s or less (below 300s).

💡 Increase the TTL to at least 300 seconds unless frequent changes are expected.

low

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

All external report destinations authorized

External DMARC report destinations have valid authorization records per RFC 7489 §7.1.

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 responses are consistent across all nameservers

All authoritative nameservers return consistent answers with proper AA flags.

pass

SPF record is 298 bytes (multi-string TXT)

The SPF record exceeds 255 bytes and requires multi-string TXT encoding. Most modern resolvers handle this correctly.

informational

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, ri

The DMARC record contains tags deprecated in DMARCbis: pct, 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

Shared/free email hosting detected: aspmx.l.google.com

The MX record points to a known shared or free email hosting provider.

informational

Shared/free email hosting detected: alt1.aspmx.l.google.com

The MX record points to a known shared or free email hosting provider.

informational

Shared/free email hosting detected: alt2.aspmx.l.google.com

The MX record points to a known shared or free email hosting provider.

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

Detected open mail-related ports: 25

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 3 different /16 networks, providing good diversity.

informational

SOA record parameters

Serial: 2015077385, Refresh: 3600s, Retry: 900s, Expire: 864000s, Min TTL: 1800s

informational

Attack Surface Findings

Dangling MX: ms30228538.msv1.invalid does not resolve

The MX record points to ms30228538.msv1.invalid which has no A record. This may indicate a decommissioned mail provider (Unknown). Attackers can potentially re-register this hostname to hijack inbound mail.

💡 Remove the stale MX record pointing to ms30228538.msv1.invalid or update it to your current mail provider.

critical

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

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 averydennison.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 averydennison.com and its subdomains. Each certificate reveals subdomain names.

informational

Reputation Findings

Could not retrieve TLS certificate

Failed to connect to averydennison.com:443 or retrieve the peer certificate.

💡 Ensure the domain has a valid TLS certificate installed and port 443 is accessible.

critical

Not listed on any DNS blacklists

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

pass

Domain valid for 493 days

Domain averydennison.com expires on 2027-09-23.

pass

Domain transfer and delete locks enabled

Domain averydennison.com has clientTransferProhibited and clientDeleteProhibited locks.

pass

No disposable email provider MX records

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

pass

Domain is 11923 days old

Domain averydennison.com was registered 1993-09-24.

pass

No wildcard MX records

No wildcard MX records detected for averydennison.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 averydennison.com

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

informational

Could not connect to webmail.averydennison.com

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

informational

WHOIS registration data

Registrar: MarkMonitor Inc. | Created: 1993-09-24 | Expires: 2027-09-23 | Updated: 2025-08-22

informational

WHOIS privacy protection not detected

Domain averydennison.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: aveydennison.com (has MX!), averydenison.com (has MX!), avreydennison.com (has MX!), averydennson.com, averydeninson.com

6 registered lookalike domain(s) that could be used for phishing against your brand. Showing top 5 of 6. 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 74.125.193.26 → PTR Record Reverse DNS: di-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 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 Identity: ms30228538.msv1.invalid

PTR record proves mail server legitimacy

MX: ms30228538.msv1.invalid Mail server at ms30228538.msv1.invalid → PTR Record No PTR record

⚠️ Mail server ms30228538.msv1.invalid (ms30228538.msv1.invalid) lacks a PTR record. Many receiving servers require matching forward and reverse DNS for spam prevention.

Mail Server Reputation: aspmx.l.google.com