Identity
33
F
conagrabrands.com
Posture Score: 41/100
Scanned May 17, 2026 at 6:56 AM UTC
Score History
Attack Surface
0
Reputation
91
Identity Findings
No SPF record found
The domain has no SPF record, allowing anyone to send email as this domain.
💡 Publish an SPF TXT record (e.g. "v=spf1 include:_spf.google.com -all").
No MX records found
The domain has no MX records and cannot receive email.
💡 Publish MX records pointing to your mail server(s).
No DKIM records found
No DKIM records were found for any common selector. Email may not be authenticated.
💡 Configure DKIM signing and publish the public key at <selector>._domainkey.conagrabrands.com
Does not meet bulk sender requirements
Google and Yahoo require all bulk senders to have SPF+DKIM, DMARC, and one-click unsubscribe. Issues: Neither SPF nor DKIM is configured (at least one required); SPF not published (recommended alongside DKIM)
💡 Publish SPF, DKIM, and DMARC records. Implement RFC 8058 one-click unsubscribe for marketing mail.
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.
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.conagrabrands.com/.well-known/mta-sts.txt
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@conagrabrands.com").
ARC check skipped — no MX records
Cannot assess ARC support without MX records.
Very low TTL on TXT records: 295s
3 TXT records have a TTL of 295s or less (below 300s).
💡 Increase the TTL to at least 300 seconds unless frequent changes are expected.
Very low TTL on DMARC record: 296s
The DMARC record has a TTL of 296s or less (below 300s).
💡 Increase the TTL to at least 300 seconds unless frequent changes are expected.
NS TTL mismatch between parent and authoritative zone
The NS record TTL in the parent zone (~7199s) differs significantly from the authoritative zone (~86400s).
💡 Align NS record TTLs between the parent zone delegation and the authoritative zone.
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.
Subdomains protected (sp=reject)
DMARC subdomain policy enforces quarantine or reject on unauthenticated subdomain mail.
No deprecated DMARCbis tags present
The DMARC record does not use any tags deprecated in DMARCbis (pct, rf, ri).
IPv6 readiness is good
IPv6 records are present and properly configured.
DNS responses are consistent across all nameservers
All authoritative nameservers return consistent answers with proper AA flags.
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: 2026050501, Refresh: 86400s, Retry: 3600s, Expire: 2592000s, Min TTL: 172800s
Attack Surface Findings
Non-responsive nameserver:
The nameserver delegated for conagrabrands.com is not responding on port 53. An attacker who gains control of this hostname could hijack the entire zone.
💡 Remove the NS delegation to or ensure the nameserver is operational.
Non-responsive nameserver:
The nameserver delegated for conagrabrands.com is not responding on port 53. An attacker who gains control of this hostname could hijack the entire zone.
💡 Remove the NS delegation to or ensure the nameserver is operational.
Non-responsive nameserver:
The nameserver delegated for conagrabrands.com is not responding on port 53. An attacker who gains control of this hostname could hijack the entire zone.
💡 Remove the NS delegation to or ensure the nameserver is operational.
Non-responsive nameserver:
The nameserver delegated for conagrabrands.com is not responding on port 53. An attacker who gains control of this hostname could hijack the entire zone.
💡 Remove the NS delegation to or ensure the nameserver is operational.
Non-responsive nameserver:
The nameserver delegated for conagrabrands.com is not responding on port 53. An attacker who gains control of this hostname could hijack the entire zone.
💡 Remove the NS delegation to or ensure the nameserver is operational.
Non-responsive nameserver:
The nameserver delegated for conagrabrands.com is not responding on port 53. An attacker who gains control of this hostname could hijack the entire zone.
💡 Remove the NS delegation to or ensure the nameserver is operational.
Non-responsive nameserver:
The nameserver delegated for conagrabrands.com is not responding on port 53. An attacker who gains control of this hostname could hijack the entire zone.
💡 Remove the NS delegation to or ensure the nameserver is operational.
AXFR zone transfer allowed on
The nameserver allows AXFR zone transfers, exposing the complete zone contents to anyone. This is the most severe enumerability issue.
💡 Restrict AXFR transfers on to authorized secondary nameservers only using allow-transfer ACLs.
AXFR zone transfer allowed on
The nameserver allows AXFR zone transfers, exposing the complete zone contents to anyone. This is the most severe enumerability issue.
💡 Restrict AXFR transfers on to authorized secondary nameservers only using allow-transfer ACLs.
Domain enumerability: high
The domain is highly enumerable. Zone transfers, NSEC zone walking, or a combination of factors make it easy to discover all DNS records.
💡 Restrict zone transfers, use NSEC3 instead of NSEC, consider wildcard certificates to reduce CT log exposure, and implement rate limiting on DNS queries.
Non-mail domain has no SPF record
This domain has no MX records (does not receive mail) but also has no SPF record. Without "v=spf1 -all", attackers can spoof this domain in phishing emails.
💡 Publish "v=spf1 -all" to explicitly declare this domain sends no mail.
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.
No internal information leakage detected
No non-routable IP addresses or internal references were found in public DNS records.
No excessive DNS information exposure detected
No HINFO, LOC, RP records, version disclosures, or zone walking vulnerabilities were found.
No email autodiscovery endpoints detected
No Microsoft Autodiscover, Mozilla Autoconfig, or email SRV records were found.
1 subdomain(s) discovered for conagrabrands.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 conagrabrands.com and its subdomains. Each certificate reveals subdomain names.
Reputation Findings
DMARC reports sent to URL shortener domain
DMARC aggregate or forensic reports contain sensitive authentication metadata. Sending them to URL shortener domains indicates misconfiguration or a compromised record.
💡 Change DMARC rua/ruf addresses to a domain you control.
HSTS enabled but missing preload directive on conagrabrands.com
Strict-Transport-Security: max-age=31536000
💡 Add the "preload" directive to the HSTS header and submit the domain to hstspreload.org.
Not listed on any DNS blacklists
Domain and MX IPs checked against 55 DNSBLs — no listings found.
security.txt present
Found security.txt at https://conagrabrands.com/.well-known/security.txt.
TLS certificate valid for 77 days
Certificate for conagrabrands.com expires on 2026-08-02.
Certificate issued by E8
The certificate for conagrabrands.com is issued by a third-party CA.
Signature algorithm: ecdsa-with-sha384
The certificate for conagrabrands.com uses an acceptable signature algorithm.
ECC key: 256 bits
The certificate for conagrabrands.com uses an adequate ECC key of 256 bits.
SCTs present in certificate
The certificate for conagrabrands.com contains Signed Certificate Timestamps.
No weak ciphers detected
No known weak cipher suites detected on conagrabrands.com.
Domain valid for 265 days
Domain conagrabrands.com expires on 2027-02-06.
Domain transfer and delete locks enabled
Domain conagrabrands.com has clientTransferProhibited and clientDeleteProhibited locks.
No disposable email provider MX records
MX records for conagrabrands.com do not match known disposable email provider patterns.
Domain is 8865 days old
Domain conagrabrands.com was registered 2002-02-06.
No wildcard MX records
No wildcard MX records detected for conagrabrands.com.
TLD has good reputation
The .com TLD is not on known abuse watchlists.
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.conagrabrands.com
HTTPS request to https://webmail.conagrabrands.com failed or timed out.
WHOIS registration data
Registrar: MarkMonitor Inc. | Created: 2002-02-06 | Expires: 2027-02-06 | Updated: 2026-01-05
WHOIS privacy protection not detected
Domain conagrabrands.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: congrabrands.com, conagrabrand.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 missing
→
DMARC Policy
DMARC policy: reject
⚠️ SPF record is missing. DMARC relies on SPF to verify sender authorization. Without SPF, DMARC alignment will fail, reducing email deliverability and brand protection.
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.
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 policy: reject
→
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
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/conagrabrands.com.svg" alt="Email Security Grade">
Want to re-scan this domain for updated results?
Scan conagrabrands.com Again