Identity
35
F
bbrown.com
Posture Score: 54/100
Scanned May 17, 2026 at 6:41 PM UTC
Attack Surface
38
Reputation
88
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).
Weak DKIM RSA key (~1296 bits) for selector 'k1'
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.
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.
Weak DKIM RSA key (~1296 bits) for selector 'mandrill'
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.
Weak DKIM RSA key (~1296 bits) for selector 'cm'
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.
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.bbrown.com/.well-known/mta-sts.txt
BIMI logo may not be SVG Tiny PS
The logo URL returns Content-Type: text/html; charset=UTF-8. BIMI requires SVG Tiny PS format.
💡 Ensure the logo is in SVG Tiny PS format.
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@bbrown.com").
ARC check skipped — no MX records
Cannot assess ARC support without MX records.
Very low TTL on MX record: 297s
The MX record has a TTL of 297s or less (below 300s).
💡 Increase the TTL to at least 300 seconds unless frequent changes are expected.
Very low TTL on TXT records: 291s
30 TXT records have a TTL of 291s or less (below 300s).
💡 Increase the TTL to at least 300 seconds unless frequent changes are expected.
Very low TTL on SPF record: 291s
The SPF record has a TTL of 291s or less (below 300s).
💡 Increase the TTL to at least 300 seconds unless frequent changes are expected.
Very low TTL on DMARC record: 297s
The DMARC record has a TTL of 297s 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.
SPF record length OK (50 bytes)
SPF record is within safe DNS packet size limits.
DKIM cryptographic configuration is compliant
No RFC 8301 compliance issues detected in DKIM key configuration.
DKIM key strength indicates modern key management
All DKIM keys use RSA-2048+ or Ed25519, consistent with current best practices.
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).
Meets bulk sender authentication requirements
Domain has SPF, DKIM, and DMARC — meeting Google/Yahoo 2024 bulk sender requirements for email authentication.
IPv6 readiness is good
IPv6 records are present and properly configured.
NS delegation is properly configured
All nameservers are responsive, consistent, and properly secured.
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.
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.
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.
DANE check skipped — no MX records
Cannot check DANE/TLSA without MX records.
No VMC authority URL in BIMI record
The BIMI record does not specify a VMC (a= tag). Gmail and Apple Mail require a VMC to display brand logos.
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
DKIM signing is configured. RFC 8058 compliance depends on List-Unsubscribe and List-Unsubscribe-Post headers being included in outbound messages and DKIM signatures.
FCrDNS check skipped — no MX records
Cannot perform FCrDNS without MX records.
SOA record parameters
Serial: 2404257244, Refresh: 10000s, Retry: 2400s, Expire: 604800s, Min TTL: 1800s
Attack Surface Findings
Non-responsive nameserver:
The nameserver delegated for bbrown.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 bbrown.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 IP for www.bbrown.com: 2606:4700:440b::6812:2741
The subdomain www.bbrown.com resolves to 2606:4700:440b::6812:2741 which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2606:4700:440b::6812:2741 is operational or remove the DNS record for www.bbrown.com.
Non-responsive IP for www.bbrown.com: 2a06:98c1:310d::ac40:94bf
The subdomain www.bbrown.com resolves to 2a06:98c1:310d::ac40:94bf which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2a06:98c1:310d::ac40:94bf is operational or remove the DNS record for www.bbrown.com.
Non-responsive IP for dev.bbrown.com: 2606:4700:440b::6812:2741
The subdomain dev.bbrown.com resolves to 2606:4700:440b::6812:2741 which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2606:4700:440b::6812:2741 is operational or remove the DNS record for dev.bbrown.com.
Non-responsive IP for dev.bbrown.com: 2a06:98c1:310d::ac40:94bf
The subdomain dev.bbrown.com resolves to 2a06:98c1:310d::ac40:94bf which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2a06:98c1:310d::ac40:94bf is operational or remove the DNS record for dev.bbrown.com.
Non-responsive IP for test.bbrown.com: 2606:4700:440b::6812:2741
The subdomain test.bbrown.com resolves to 2606:4700:440b::6812:2741 which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2606:4700:440b::6812:2741 is operational or remove the DNS record for test.bbrown.com.
Non-responsive IP for test.bbrown.com: 2a06:98c1:310d::ac40:94bf
The subdomain test.bbrown.com resolves to 2a06:98c1:310d::ac40:94bf which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2a06:98c1:310d::ac40:94bf is operational or remove the DNS record for test.bbrown.com.
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.
All MX records resolve correctly
No dangling MX records detected — all MX hostnames resolve to valid IP addresses.
Explicit MX records present
The domain has explicit MX records — no implicit A-record fallback delivery.
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.
3 subdomain(s) discovered for bbrown.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 bbrown.com and its subdomains. Each certificate reveals subdomain names.
Reputation Findings
Missing domain locks: clientDeleteProhibited
Domain bbrown.com is missing protective locks: clientDeleteProhibited.
💡 Enable clientTransferProhibited and clientDeleteProhibited locks through your registrar to prevent unauthorized transfers or deletions.
Missing Strict-Transport-Security on bbrown.com
The Strict-Transport-Security header is not set on https://bbrown.com.
💡 Add the Strict-Transport-Security header with a max-age of at least 31536000 (1 year) and include the includeSubDomains directive.
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://bbrown.com/.well-known/security.txt.
TLS certificate valid for 49 days
Certificate for bbrown.com expires on 2026-07-05.
Certificate issued by E8
The certificate for bbrown.com is issued by a third-party CA.
Signature algorithm: ecdsa-with-sha384
The certificate for bbrown.com uses an acceptable signature algorithm.
ECC key: 256 bits
The certificate for bbrown.com uses an adequate ECC key of 256 bits.
SCTs present in certificate
The certificate for bbrown.com contains Signed Certificate Timestamps.
No weak ciphers detected
No known weak cipher suites detected on bbrown.com.
Domain valid for 83 days
Domain bbrown.com expires on 2026-08-09.
No disposable email provider MX records
MX records for bbrown.com do not match known disposable email provider patterns.
Domain is 9048 days old
Domain bbrown.com was registered 2001-08-08.
No wildcard MX records
No wildcard MX records detected for bbrown.com.
TLD has good reputation
The .com TLD is not on known abuse watchlists.
DMARC reporting destinations look legitimate
DMARC rua/ruf addresses do not point to known URL shortener services.
MX records point to stable infrastructure
No MX records point to known dynamic DNS service domains.
Strong TLS configuration on primary MX
Primary MX (bbrown-com.mail.protection.outlook.com) uses TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 including Forward Secrecy.
SMTP banner from hosted mail provider
The MX (bbrown-com.mail.protection.outlook.com) is a hosted mail service. Banner alignment is managed by the provider and not actionable by the domain owner.
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 contacts found for MX IPs
Abuse contact information retrieved via abusix.org DNS lookup.
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.bbrown.com
HTTPS request to https://webmail.bbrown.com failed or timed out.
WHOIS registration data
Registrar: Cloudflare, Inc. | Created: 2001-08-08 | Expires: 2026-08-09 | Updated: 2025-07-10
WHOIS privacy protection enabled
Domain bbrown.com has WHOIS privacy/redaction enabled.
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: brown.com (has MX!), bbown.com (has MX!), bbron.com (has MX!), bbrwon.com (has MX!), bbronw.com (has MX!)
14 registered lookalike domain(s) that could be used for phishing against your brand. Showing top 5 of 14. 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 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: bbrown-com.mail.protection.outlook.com
PTR record proves mail server legitimacy
MX: bbrown-com.mail.protection.outlook.com
Mail server at 52.101.41.26
→
PTR Record
Reverse DNS: mail-sj0pr03cu01702.inbound.protection.outlook.com
Mail Server Reputation: bbrown-com.mail.protection.outlook.com
RBL check ensures server is not blacklisted
MX: bbrown-com.mail.protection.outlook.com
Mail server at 52.101.41.26
→
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: reject
→
BIMI Record
Brand logo configured
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/bbrown.com.svg" alt="Email Security Grade">
Want to re-scan this domain for updated results?
Scan bbrown.com Again