Identity
66
C
bttrack.com
Posture Score: 72/100
Scanned May 30, 2026 at 5:16 AM UTC
Attack Surface
75
Reputation
74
Identity Findings
Weak DKIM RSA key (~1296 bits) for selector 'mailo'
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 DMARC aggregate report URI (rua=)
Without rua=, you will not receive aggregate reports about authentication results.
💡 Add rua=mailto:dmarc-reports@bttrack.com to your DMARC 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.bttrack.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: 139.182.36.34.bc.googleusercontent.com
The PTR record for 34.36.182.139 appears to be a generic ISP hostname, which can harm deliverability.
💡 Set a meaningful PTR record like mail.bttrack.com
Generic ISP PTR hostname: 5.254.149.34.bc.googleusercontent.com
The PTR record for 34.149.254.5 appears to be a generic ISP hostname, which can harm deliverability.
💡 Set a meaningful PTR record like mail.bttrack.com
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@bttrack.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.
SPF record is valid
The SPF record is properly configured with valid syntax and within lookup limits.
SPF record length OK (36 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.
No external DMARC report destinations
All DMARC report URIs point to the same domain — no external authorization needed.
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).
MX records are valid
All MX records are properly configured.
Meets bulk sender authentication requirements
Domain has SPF, DKIM, and DMARC — meeting Google/Yahoo 2024 bulk sender requirements for email authentication.
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.
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.
DNS TTL values follow best practices
All critical DNS record TTLs are within recommended ranges.
DKIM key revoked for selector 'selector1'
The DKIM record has an empty p= tag, indicating the key has been revoked.
DKIM key revoked for selector 'selector2'
The DKIM record has an empty p= tag, indicating the key has been revoked.
DKIM key revoked for selector 'google'
The DKIM record has an empty p= tag, indicating the key has been revoked.
DKIM key revoked for selector 'google2048'
The DKIM record has an empty p= tag, indicating the key has been revoked.
DKIM key revoked for selector 's1'
The DKIM record has an empty p= tag, indicating the key has been revoked.
DKIM key revoked for selector 's2'
The DKIM record has an empty p= tag, indicating the key has been revoked.
DKIM key revoked for selector 'proofpoint'
The DKIM record has an empty p= tag, indicating the key has been revoked.
DKIM key revoked for selector 'pphosted'
The DKIM record has an empty p= tag, indicating the key has been revoked.
DKIM key revoked for selector 'mimecast20190322'
The DKIM record has an empty p= tag, indicating the key has been revoked.
DKIM key revoked for selector 'mimecast'
The DKIM record has an empty p= tag, indicating the key has been revoked.
DKIM key revoked for selector 'default'
The DKIM record has an empty p= tag, indicating the key has been revoked.
DKIM key revoked for selector 'dkim'
The DKIM record has an empty p= tag, indicating the key has been revoked.
DKIM key revoked for selector 'dkim1'
The DKIM record has an empty p= tag, indicating the key has been revoked.
DKIM key revoked for selector 'dkim2'
The DKIM record has an empty p= tag, indicating the key has been revoked.
DKIM key revoked for selector 'mail'
The DKIM record has an empty p= tag, indicating the key has been revoked.
DKIM key revoked for selector 'email'
The DKIM record has an empty p= tag, indicating the key has been revoked.
DKIM key revoked for selector 'smtp'
The DKIM record has an empty p= tag, indicating the key has been revoked.
DKIM key revoked for selector 'k1'
The DKIM record has an empty p= tag, indicating the key has been revoked.
DKIM key revoked for selector 'k2'
The DKIM record has an empty p= tag, indicating the key has been revoked.
DKIM key revoked for selector 'smtpapi'
The DKIM record has an empty p= tag, indicating the key has been revoked.
DKIM key revoked for selector 'mandrill'
The DKIM record has an empty p= tag, indicating the key has been revoked.
DKIM key revoked for selector 'k1._domainkey'
The DKIM record has an empty p= tag, indicating the key has been revoked.
DKIM key revoked for selector 'mcdkim'
The DKIM record has an empty p= tag, indicating the key has been revoked.
DKIM key revoked for selector 'amazonses'
The DKIM record has an empty p= tag, indicating the key has been revoked.
DKIM key revoked for selector 'sf'
The DKIM record has an empty p= tag, indicating the key has been revoked.
DKIM key revoked for selector 'sf1'
The DKIM record has an empty p= tag, indicating the key has been revoked.
DKIM key revoked for selector 'sf2'
The DKIM record has an empty p= tag, indicating the key has been revoked.
DKIM key revoked for selector 'salesforce'
The DKIM record has an empty p= tag, indicating the key has been revoked.
DKIM key revoked for selector 'salesforce1'
The DKIM record has an empty p= tag, indicating the key has been revoked.
DKIM key revoked for selector 'salesforce2'
The DKIM record has an empty p= tag, indicating the key has been revoked.
DKIM key revoked for selector 'zendesk1'
The DKIM record has an empty p= tag, indicating the key has been revoked.
DKIM key revoked for selector 'zendesk2'
The DKIM record has an empty p= tag, indicating the key has been revoked.
DKIM key revoked for selector 'hs1'
The DKIM record has an empty p= tag, indicating the key has been revoked.
DKIM key revoked for selector 'hs2'
The DKIM record has an empty p= tag, indicating the key has been revoked.
DKIM key revoked for selector 'hubspot'
The DKIM record has an empty p= tag, indicating the key has been revoked.
DKIM key revoked for selector 'pm'
The DKIM record has an empty p= tag, indicating the key has been revoked.
DKIM key revoked for selector '20230601'
The DKIM record has an empty p= tag, indicating the key has been revoked.
DKIM key revoked for selector 'mg'
The DKIM record has an empty p= tag, indicating the key has been revoked.
DKIM key revoked for selector 'ctct1'
The DKIM record has an empty p= tag, indicating the key has been revoked.
DKIM key revoked for selector 'ctct2'
The DKIM record has an empty p= tag, indicating the key has been revoked.
DKIM key revoked for selector 'ironport'
The DKIM record has an empty p= tag, indicating the key has been revoked.
DKIM key revoked for selector 'cisco'
The DKIM record has an empty p= tag, indicating the key has been revoked.
DKIM key revoked for selector 'barracuda'
The DKIM record has an empty p= tag, indicating the key has been revoked.
DKIM key revoked for selector 'fm1'
The DKIM record has an empty p= tag, indicating the key has been revoked.
DKIM key revoked for selector 'fm2'
The DKIM record has an empty p= tag, indicating the key has been revoked.
DKIM key revoked for selector 'fm3'
The DKIM record has an empty p= tag, indicating the key has been revoked.
DKIM key revoked for selector 'zoho'
The DKIM record has an empty p= tag, indicating the key has been revoked.
DKIM key revoked for selector 'cm'
The DKIM record has an empty p= tag, indicating the key has been revoked.
DKIM key revoked for selector 'sendinblue'
The DKIM record has an empty p= tag, indicating the key has been revoked.
DKIM key revoked for selector 'mx'
The DKIM record has an empty p= tag, indicating the key has been revoked.
DKIM key revoked for selector 'key1'
The DKIM record has an empty p= tag, indicating the key has been revoked.
DKIM key revoked for selector 'key2'
The DKIM record has an empty p= tag, indicating the key has been revoked.
DKIM key revoked for selector 'e'
The DKIM record has an empty p= tag, indicating the key has been revoked.
DKIM key revoked for selector 'a'
The DKIM record has an empty p= tag, indicating the key has been revoked.
DKIM key revoked for selector 'cjis'
The DKIM record has an empty p= tag, indicating the key has been revoked.
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=s, aspf=s
DKIM alignment is strict, SPF alignment is strict.
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.
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 mxa.mailgun.org
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: 1453218067, Refresh: 86400s, Retry: 7200s, Expire: 604800s, Min TTL: 300s
Attack Surface Findings
Weak DNSSEC RSA key: 336 bits
The DNSKEY uses an RSA key of 336 bits, below the recommended 2048 bits.
💡 Generate a new DNSKEY with at least 2048-bit RSA or migrate to ECDSA/Ed25519.
Weak DNSSEC RSA key: 336 bits
The DNSKEY uses an RSA key of 336 bits, below the recommended 2048 bits.
💡 Generate a new DNSKEY with at least 2048-bit RSA or migrate to ECDSA/Ed25519.
DNS ANY query returns 31 record(s)
The DNS server responds to ANY queries with 31 record(s), creating significant DNS amplification risk.
💡 Configure the DNS server to refuse or minimize ANY query responses per RFC 8482.
No NSEC/NSEC3 records found
Neither NSEC nor NSEC3 records were found. Authenticated denial of existence is not configured.
💡 Configure NSEC3 records for authenticated denial of existence while preventing zone enumeration.
Domain enumerability: low
The domain has low enumerability. Proper NSEC3 configuration and limited CT exposure reduce the attack surface.
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.
1 subdomain(s) discovered for bttrack.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 bttrack.com and its subdomains. Each certificate reveals subdomain names.
Wildcard DNS record detected
A wildcard DNS record exists for *.bttrack.com, resolving to 192.132.33.84, 192.132.33.85, 192.132.33.86. Wildcard records make subdomain brute-forcing less effective but may mask misconfigurations.
Microsoft Autodiscover endpoint detected
The Autodiscover endpoint at autodiscover.bttrack.com responded with HTTP 404.
DNSSEC is enabled
DNSKEY and/or DS records are present, indicating DNSSEC is configured.
Reputation Findings
Missing domain locks: clientDeleteProhibited
Domain bttrack.com is missing protective locks: clientDeleteProhibited.
💡 Enable clientTransferProhibited and clientDeleteProhibited locks through your registrar to prevent unauthorized transfers or deletions.
SMTP banner mismatch: mailgun
The SMTP banner identifies as 'mailgun' but the MX hostname is 'mxa.mailgun.org' and PTR resolves to '139.182.36.34.bc.googleusercontent.com'. Microsoft and other receivers flag this mismatch as suspicious infrastructure.
💡 Configure the SMTP server banner to match the MX hostname or PTR record (mxa.mailgun.org).
Missing Strict-Transport-Security on webmail.bttrack.com
The Strict-Transport-Security header is not set on https://webmail.bttrack.com.
💡 Add the Strict-Transport-Security header with a max-age of at least 31536000 (1 year) and include the includeSubDomains directive.
Wildcard MX records detected
Domain bttrack.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.
HSTS enabled but missing preload directive on bttrack.com
Strict-Transport-Security: max-age=31536000;
💡 Add the "preload" directive to the HSTS header and submit the domain to hstspreload.org.
Missing security.txt
No security.txt found at https://bttrack.com/.well-known/security.txt.
💡 Create a /.well-known/security.txt file per RFC 9116 with Contact, Expires, and optionally Encryption and Policy fields.
Not listed on any DNS blacklists
Domain and MX IPs checked against 55 DNSBLs — no listings found.
TLS certificate valid for 133 days
Certificate for bttrack.com expires on 2026-10-10.
Certificate issued by Sectigo Public Server Authentication CA DV R36
The certificate for bttrack.com is issued by a third-party CA.
Signature algorithm: rsa-sha256
The certificate for bttrack.com uses an acceptable signature algorithm.
RSA key: 2048 bits
The certificate for bttrack.com uses an adequate RSA key of 2048 bits.
SCTs present in certificate
The certificate for bttrack.com contains Signed Certificate Timestamps.
No weak ciphers detected
No known weak cipher suites detected on bttrack.com.
Domain valid for 216 days
Domain bttrack.com expires on 2027-01-01.
No disposable email provider MX records
MX records for bttrack.com do not match known disposable email provider patterns.
Domain is 4447 days old
Domain bttrack.com was registered 2014-03-26.
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 (mxb.mailgun.org) uses TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 including Forward Secrecy.
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.
WHOIS registration data
Registrar: 1API GmbH | Created: 2014-03-26 | Expires: 2027-01-01 | Updated: 2026-05-12
WHOIS privacy protection enabled
Domain bttrack.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: btrack.com (has MX!), tbtrack.com (has MX!), httrack.com (has MX!), bytrack.com (has MX!), btrrack.com (has MX!)
11 registered lookalike domain(s) that could be used for phishing against your brand. Showing top 5 of 11. 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 configured
→
DMARC Policy
DMARC policy: reject
Mail Server Identity: mxa.mailgun.org
PTR record proves mail server legitimacy
MX: mxa.mailgun.org
Mail server at 34.36.182.139
→
PTR Record
Reverse DNS: 139.182.36.34.bc.googleusercontent.com
Mail Server Identity: mxb.mailgun.org
PTR record proves mail server legitimacy
MX: mxb.mailgun.org
Mail server at 34.149.254.5
→
PTR Record
Reverse DNS: 5.254.149.34.bc.googleusercontent.com
Mail Server Reputation: mxa.mailgun.org
RBL check ensures server is not blacklisted
MX: mxa.mailgun.org
Mail server at 34.36.182.139
→
RBL Status
Not blacklisted
Mail Server Reputation: mxb.mailgun.org
RBL check ensures server is not blacklisted
MX: mxb.mailgun.org
Mail server at 34.149.254.5
→
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
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 failure reporting configured
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/bttrack.com.svg" alt="Email Security Grade">
Want to re-scan this domain for updated results?
Scan bttrack.com Again