Identity
19
D
freshchat.com
Posture Score: 61/100
Scanned May 30, 2026 at 7:04 AM UTC
Attack Surface
87
Reputation
78
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).
No NS records found
No nameserver records could be retrieved for this domain.
💡 Ensure NS records are properly configured at your registrar and in your zone file.
Weak DKIM RSA key (~1296 bits) for selector 'smtpapi'
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.
External report destination not authorized: freshworks.com
The rua= URI sends reports to freshworks.com, but no authorization record exists at freshchat.com._report._dmarc.freshworks.com. Reports will be silently dropped by compliant receivers.
💡 Ask the owner of freshworks.com to publish a TXT record at freshchat.com._report._dmarc.freshworks.com containing 'v=DMARC1'.
External report destination not authorized: freshworks.com
The ruf= URI sends reports to freshworks.com, but no authorization record exists at freshchat.com._report._dmarc.freshworks.com. Reports will be silently dropped by compliant receivers.
💡 Ask the owner of freshworks.com to publish a TXT record at freshchat.com._report._dmarc.freshworks.com containing 'v=DMARC1'.
Cannot check DNS consistency — no NS records
No nameserver records could be retrieved for consistency checking.
💡 Ensure NS records are properly configured.
DMARC policy is monitoring-only (p=none)
The p=none policy only monitors; it does not instruct receivers to quarantine or reject unauthenticated mail.
💡 Upgrade to p=quarantine or p=reject after reviewing aggregate reports.
External DMARC report destination not authorized: freshworks.com
The rua= URI points to freshworks.com but no authorization record exists at freshchat.com._report._dmarc.freshworks.com.
💡 Ask the owner of freshworks.com to publish a TXT record at freshchat.com._report._dmarc.freshworks.com with 'v=DMARC1'.
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.freshchat.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"
DMARC percentage is 20% (not fully enforced)
Only 20% of messages are subject to the DMARC policy. The remaining messages are treated as p=none.
💡 Increase pct to 100 once confident in SPF/DKIM alignment.
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@freshchat.com").
ARC check skipped — no MX records
Cannot assess ARC support without MX records.
SPF record is valid
The SPF record is properly configured with valid syntax and within lookup limits.
SPF record length OK (84 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.
Subdomains protected (sp=quarantine)
DMARC subdomain policy enforces quarantine or reject on unauthenticated subdomain mail.
Meets bulk sender authentication requirements
Domain has SPF, DKIM, and DMARC — meeting Google/Yahoo 2024 bulk sender requirements for email authentication.
DNS TTL values follow best practices
All critical DNS record TTLs are within recommended ranges.
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.
Deprecated DMARCbis tags found: pct
The DMARC record contains tags deprecated in DMARCbis: pct. 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.
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 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.
Domain is IPv4-only
No AAAA records found for the domain, MX servers, or nameservers. The domain operates on IPv4 only.
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: 1, Refresh: 7200s, Retry: 900s, Expire: 1209600s, Min TTL: 86400s
Attack Surface Findings
Microsoft Autodiscover accessible without authentication
The Autodiscover endpoint at https://autodiscover.freshchat.com/autodiscover/autodiscover.xml returns configuration data without requiring authentication. This exposes email server details to unauthenticated users.
💡 Configure the Autodiscover endpoint to require authentication before returning configuration data.
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.
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.
No excessive DNS information exposure detected
No HINFO, LOC, RP records, version disclosures, or zone walking vulnerabilities were found.
4 subdomain(s) discovered for freshchat.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 freshchat.com and its subdomains. Each certificate reveals subdomain names.
Wildcard DNS record detected
A wildcard DNS record exists for *.freshchat.com, resolving to 162.159.140.147, 172.66.0.145. Wildcard records make subdomain brute-forcing less effective but may mask misconfigurations.
Mozilla Autoconfig endpoint detected
The Autoconfig endpoint at autoconfig.freshchat.com is publicly accessible.
Reputation Findings
Domain expires in 36 days
Domain freshchat.com expires on 2026-07-05 (36 days).
💡 Renew the domain registration soon — it expires within 60 days. Enable auto-renewal if available.
Missing domain locks: clientDeleteProhibited
Domain freshchat.com is missing protective locks: clientDeleteProhibited.
💡 Enable clientTransferProhibited and clientDeleteProhibited locks through your registrar to prevent unauthorized transfers or deletions.
Wildcard MX records detected
Domain freshchat.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 freshchat.com
Strict-Transport-Security: max-age=31536000; includeSubDomains
💡 Add the "preload" directive to the HSTS header and submit the domain to hstspreload.org.
HSTS enabled but missing preload directive on webmail.freshchat.com
Strict-Transport-Security: max-age=31536000; includeSubDomains
💡 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://freshchat.com/.well-known/security.txt.
TLS certificate valid for 197 days
Certificate for freshchat.com expires on 2026-12-13.
Certificate issued by Amazon RSA 2048 M04
The certificate for freshchat.com is issued by a third-party CA.
Signature algorithm: rsa-sha256
The certificate for freshchat.com uses an acceptable signature algorithm.
RSA key: 2048 bits
The certificate for freshchat.com uses an adequate RSA key of 2048 bits.
SCTs present in certificate
The certificate for freshchat.com contains Signed Certificate Timestamps.
No weak ciphers detected
No known weak cipher suites detected on freshchat.com.
No disposable email provider MX records
MX records for freshchat.com do not match known disposable email provider patterns.
Domain is 9094 days old
Domain freshchat.com was registered 2001-07-05.
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 (aspmx.l.google.com) uses TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 including Forward Secrecy.
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.
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: Amazon Registrar, Inc. | Created: 2001-07-05 | Expires: 2026-07-05 | Updated: 2026-05-13
WHOIS privacy protection enabled
Domain freshchat.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: frshchat.com (has MX!), freshhat.com (has MX!), freshcat.com (has MX!), freschat.com, freshcha.com
8 registered lookalike domain(s) that could be used for phishing against your brand. Showing top 5 of 8. 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: none
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: none
⚠️ 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 209.85.203.27
→
PTR Record
Reverse DNS: dh-in-f27.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.26
→
PTR Record
Reverse DNS: ws-in-f26.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 Reputation: aspmx.l.google.com
RBL check ensures server is not blacklisted
MX: aspmx.l.google.com
Mail server at 209.85.203.27
→
RBL Status
Not blacklisted
Mail Server Reputation: alt1.aspmx.l.google.com
RBL check ensures server is not blacklisted
MX: alt1.aspmx.l.google.com
Mail server at 173.194.76.26
→
RBL Status
Not blacklisted
Mail Server Reputation: alt2.aspmx.l.google.com
RBL check ensures server is not blacklisted
MX: alt2.aspmx.l.google.com
Mail server at 142.250.102.27
→
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
Mode:
Brand Identity Chain
BIMI displays your logo in email clients, but requires DMARC enforcement
DMARC Enforcement
DMARC not enforced (p=none or missing)
→
BIMI Record
BIMI not configured
⚠️ DMARC is not enforced. BIMI requires a DMARC policy of "quarantine" or "reject" to prove you have strong email authentication. Without enforcement, email clients will not display your logo.
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/freshchat.com.svg" alt="Email Security Grade">
Want to re-scan this domain for updated results?
Scan freshchat.com Again