Identity
35
C
walgreens.com
Posture Score: 71/100
Scanned May 8, 2026 at 11:11 PM UTC
Attack Surface
83
Reputation
96
Identity Findings
Malformed DKIM public key for selector 'mandrill'
The public key in the DKIM record is not valid base64.
💡 Regenerate and publish a valid DKIM key pair.
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.
Inconsistent DNS responses across nameservers
Authoritative nameservers return different answers for the same query.
💡 Verify zone transfers are working correctly and all nameservers serve the same zone data.
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.
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.walgreens.com/.well-known/mta-sts.txt
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.
Generic ISP PTR hostname: esa.hc2985-66.iphmx.com
The PTR record for 139.138.32.112 appears to be a generic ISP hostname, which can harm deliverability.
💡 Set a meaningful PTR record like mail.walgreens.com
Generic ISP PTR hostname: esa.hc2985-66.iphmx.com
The PTR record for 216.71.138.235 appears to be a generic ISP hostname, which can harm deliverability.
💡 Set a meaningful PTR record like mail.walgreens.com
Generic ISP PTR hostname: esa.hc2985-66.iphmx.com
The PTR record for 216.71.138.235 appears to be a generic ISP hostname, which can harm deliverability.
💡 Set a meaningful PTR record like mail.walgreens.com
Generic ISP PTR hostname: esa.hc2985-66.iphmx.com
The PTR record for 139.138.32.112 appears to be a generic ISP hostname, which can harm deliverability.
💡 Set a meaningful PTR record like mail.walgreens.com
SOA MNAME does not resolve
The primary nameserver (MNAME) 'corp-eqix-ch4-dnscr-001.walgreens.com' does not resolve to any IP address.
💡 Ensure the MNAME field points to a resolvable, authoritative nameserver.
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@walgreens.com").
ARC support not detected
No evidence of ARC (Authenticated Received Chain) support on MX servers. Forwarded messages may lose authentication.
💡 Consider enabling ARC signing on your mail servers to preserve authentication through forwarding.
Shared IP 139.138.32.112 used by multiple MX servers
The IP 139.138.32.112 is shared across 2 MX hostnames, reducing redundancy.
💡 Use unique IP addresses for each MX server for better redundancy.
Shared IP 216.71.138.235 used by multiple MX servers
The IP 216.71.138.235 is shared across 2 MX hostnames, reducing redundancy.
💡 Use unique IP addresses for each MX server for better redundancy.
Very low TTL on A records: 60s
4 A records have a TTL of 60s or less (below 300s).
💡 Increase the TTL to at least 300 seconds unless frequent changes are expected.
SPF record is valid
The SPF record is properly configured with valid syntax and within lookup limits.
DKIM cryptographic configuration is compliant
No RFC 8301 compliance issues detected in DKIM key configuration.
MX records are valid
All MX records are properly configured.
SMTP security checks passed
No open relay, VRFY/EXPN, or banner disclosure issues detected.
SMTP RFC 5321 compliance checks passed
The mail server accepts postmaster@ and abuse@ and uses a valid FQDN in EHLO.
IPv6 readiness is good
IPv6 records are present and properly configured.
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.
Deprecated DMARCbis tags found: ri
The DMARC record contains tags deprecated in DMARCbis: ri. Consider removing these for forward compatibility.
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.
No DANE/TLSA records found
DANE is not configured for any MX server. This is optional but provides strong certificate binding.
No BIMI record found
BIMI is not configured. Your brand logo will not display in supporting email clients.
Open mail ports on mx1.hc2985-66.iphmx.com
Detected open mail-related ports: 25
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.
MX IP network diversity
MX IPs span 2 different /16 networks, providing good diversity.
SOA record parameters
Serial: 715321670, Refresh: 1200s, Retry: 180s, Expire: 1209600s, Min TTL: 3600s
Attack Surface Findings
Non-routable IPv4 in public DNS: ns2.walgreens.com → 172.20.4.39
The subdomain ns2.walgreens.com resolves to non-routable IP 172.20.4.39, 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.
DNS ANY query returns 1 record(s)
The DNS server responds to ANY queries with 1 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.
9 subdomain(s) discovered for walgreens.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 walgreens.com and its subdomains. Each certificate reveals subdomain names.
Reputation Findings
Missing Strict-Transport-Security on walgreens.com
The Strict-Transport-Security header is not set on https://walgreens.com.
💡 Add the Strict-Transport-Security header with a max-age of at least 31536000 (1 year) and include the includeSubDomains directive.
security.txt present
Found security.txt at https://walgreens.com/.well-known/security.txt.
TLS certificate valid for 77 days
Certificate for walgreens.com expires on 2026-07-24.
Certificate issued by DigiCert Global G3 TLS ECC SHA384 2020 CA1
The certificate for walgreens.com is issued by a third-party CA.
Signature algorithm: ecdsa-with-sha384
The certificate for walgreens.com uses an acceptable signature algorithm.
ECC key: 256 bits
The certificate for walgreens.com uses an adequate ECC key of 256 bits.
SCTs present in certificate
The certificate for walgreens.com contains Signed Certificate Timestamps.
No weak ciphers detected
No known weak cipher suites detected on walgreens.com.
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.
Abuse contact lookup failed
Could not query abuse contact information.
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.walgreens.com
HTTPS request to https://webmail.walgreens.com failed or timed out.
WHOIS lookup failed
Could not retrieve WHOIS data for walgreens.com.
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: mx1.hc2985-66.iphmx.com
PTR record proves mail server legitimacy
MX: mx1.hc2985-66.iphmx.com
Mail server at 139.138.32.112
→
PTR Record
Reverse DNS: esa.hc2985-66.iphmx.com
Mail Server Identity: mx2.hc2985-66.iphmx.com
PTR record proves mail server legitimacy
MX: mx2.hc2985-66.iphmx.com
Mail server at 216.71.138.235
→
PTR Record
Reverse DNS: esa.hc2985-66.iphmx.com
Mail Server Reputation: mx1.hc2985-66.iphmx.com
RBL check ensures server is not blacklisted
MX: mx1.hc2985-66.iphmx.com
Mail server at 139.138.32.112
→
RBL Status
Not blacklisted
Mail Server Reputation: mx2.hc2985-66.iphmx.com
RBL check ensures server is not blacklisted
MX: mx2.hc2985-66.iphmx.com
Mail server at 216.71.138.235
→
RBL Status
Not blacklisted
Enforced Encryption Chain
MTA-STS enforces TLS encryption to prevent man-in-the-middle attacks
TLS Support
Mail servers support TLS encryption
→
MTA-STS Policy
MTA-STS not configured
⚠️ MTA-STS policy is missing. Even with TLS support, you lack the enforcement layer that prevents attackers from stripping encryption (downgrade attacks).
Brand Identity Chain
BIMI displays your logo in email clients, but requires DMARC enforcement
DMARC Enforcement
DMARC policy: quarantine
→
BIMI Record
BIMI not configured
⚠️ BIMI record is missing. Even with DMARC enforcement, you need to configure BIMI to display your brand logo in supported email clients.
TLS Monitoring Chain
TLS-RPT provides reports about TLS connection failures
TLS Support
Mail servers support TLS encryption
→
TLS-RPT Reporting
TLS-RPT not configured
⚠️ TLS-RPT is not configured. Without TLS reporting, you have no visibility into TLS connection failures that may be impacting email delivery.
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/walgreens.com.svg" alt="Email Security Grade">
Want to re-scan this domain for updated results?
Scan walgreens.com Again