Identity
23
F
sankuai.com
Posture Score: 50/100
Scanned May 30, 2026 at 3:25 AM UTC
Attack Surface
30
Reputation
96
Identity Findings
No DMARC record found
The domain has no DMARC record, providing no policy for handling unauthenticated email.
💡 Publish a DMARC TXT record at _dmarc.sankuai.com (e.g. "v=DMARC1; p=reject; rua=mailto:dmarc@sankuai.com").
MX hostname does not resolve: mx02.meituan.com
The MX hostname has no A or AAAA records.
💡 Ensure the MX hostname resolves to a valid IP address.
MX hostname does not resolve: mail3.sankuai.info
The MX hostname has no A or AAAA records.
💡 Ensure the MX hostname resolves to a valid IP address.
MX hostname does not resolve: mx01.meituan.com
The MX hostname has no A or AAAA records.
💡 Ensure the MX hostname resolves to a valid IP address.
Does not meet bulk sender requirements
Google and Yahoo require all bulk senders to have SPF+DKIM, DMARC, and one-click unsubscribe. Issues: No DMARC record published (required since Feb 2024)
💡 Publish SPF, DKIM, and DMARC records. Implement RFC 8058 one-click unsubscribe for marketing mail.
Zone contains undelegated nameservers
The zone advertises nameservers not present in the parent delegation: dns1.sankuai.com
💡 Remove unauthorized NS records from the zone or add them to the parent delegation at the registrar.
No DKIM records found
No DKIM records were found after probing 56 common selectors. The domain may use a custom selector not discoverable via external scan.
💡 Configure DKIM signing and publish the public key at <selector>._domainkey.sankuai.com
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.sankuai.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.
SOA expire value too short
The SOA expire value is 72000s (<604,800s / 7 days). Secondary nameservers may stop serving the zone prematurely.
💡 Increase the SOA expire value to at least 604800 seconds (7 days).
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@sankuai.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 (99 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.
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.
Mail server port configuration is acceptable
No concerning port exposure detected.
FCrDNS checks passed
All MX server IPs have valid forward-confirmed reverse DNS.
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.
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.
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.
Domain is IPv4-only
No AAAA records found for the domain, MX servers, or nameservers. The domain operates on IPv4 only.
RFC 8058 one-click unsubscribe assessment
No DKIM signing detected. RFC 8058 one-click unsubscribe requires DKIM-signed List-Unsubscribe headers.
SOA record parameters
Serial: 2016151838, Refresh: 18000s, Retry: 400s, Expire: 72000s, Min TTL: 1800s
Attack Surface Findings
Dangling MX: mx02.meituan.com does not resolve
The MX record points to mx02.meituan.com which has no A record. This may indicate a decommissioned mail provider (Unknown). Attackers can potentially re-register this hostname to hijack inbound mail.
💡 Remove the stale MX record pointing to mx02.meituan.com or update it to your current mail provider.
Dangling MX: mail3.sankuai.info does not resolve
The MX record points to mail3.sankuai.info which has no A record. This may indicate a decommissioned mail provider (Unknown). Attackers can potentially re-register this hostname to hijack inbound mail.
💡 Remove the stale MX record pointing to mail3.sankuai.info or update it to your current mail provider.
Dangling MX: mx01.meituan.com does not resolve
The MX record points to mx01.meituan.com which has no A record. This may indicate a decommissioned mail provider (Unknown). Attackers can potentially re-register this hostname to hijack inbound mail.
💡 Remove the stale MX record pointing to mx01.meituan.com or update it to your current mail provider.
Non-routable IPv4 in public DNS: git.sankuai.com → 10.217.129.182
The subdomain git.sankuai.com resolves to non-routable IP 10.217.129.182, leaking internal network information.
💡 Remove non-routable IPs from public DNS or implement split-horizon DNS.
Non-routable IPv4 in public DNS: git.sankuai.com → 10.192.16.34
The subdomain git.sankuai.com resolves to non-routable IP 10.192.16.34, 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 19 record(s)
The DNS server responds to ANY queries with 19 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.
Explicit MX records present
The domain has explicit MX records — no implicit A-record fallback delivery.
No email autodiscovery endpoints detected
No Microsoft Autodiscover, Mozilla Autoconfig, or email SRV records were found.
7 subdomain(s) discovered for sankuai.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 sankuai.com and its subdomains. Each certificate reveals subdomain names.
Reputation Findings
Missing Strict-Transport-Security on sankuai.com
The Strict-Transport-Security header is not set on https://sankuai.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://sankuai.com/.well-known/security.txt.
TLS certificate valid for 124 days
Certificate for sankuai.com expires on 2026-10-02.
Certificate issued by GlobalSign GCC R46 OV TLS CA 2025
The certificate for sankuai.com is issued by a third-party CA.
Signature algorithm: rsa-sha256
The certificate for sankuai.com uses an acceptable signature algorithm.
RSA key: 2048 bits
The certificate for sankuai.com uses an adequate RSA key of 2048 bits.
SCTs present in certificate
The certificate for sankuai.com contains Signed Certificate Timestamps.
No weak ciphers detected
No known weak cipher suites detected on sankuai.com.
Domain valid for 535 days
Domain sankuai.com expires on 2027-11-16.
Domain transfer and delete locks enabled
Domain sankuai.com has clientTransferProhibited and clientDeleteProhibited locks.
No disposable email provider MX records
MX records for sankuai.com do not match known disposable email provider patterns.
Domain is 7134 days old
Domain sankuai.com was registered 2006-11-16.
No wildcard MX records
No wildcard MX records detected for sankuai.com.
TLD has good reputation
The .com TLD is not on known abuse watchlists.
MX records point to stable infrastructure
No MX records point to known dynamic DNS service domains.
Strong TLS configuration on primary MX
Primary MX (mx01.meituan.com) uses with cipher 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.
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.sankuai.com
HTTPS request to https://webmail.sankuai.com failed or timed out.
WHOIS registration data
Registrar: eName Technology Co., Ltd. | Created: 2006-11-16 | Expires: 2027-11-16 | Updated: 2026-02-18
WHOIS privacy protection not detected
Domain sankuai.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: sankui.com (has MX!), sakuai.com, sanuai.com, sankua.com, sanukai.com
10 registered lookalike domain(s) that could be used for phishing against your brand. Showing top 5 of 10. 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 missing
⚠️ DMARC policy is missing. Even with SPF configured, you lack the policy layer that tells receiving servers what to do with authentication failures.
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 missing
⚠️ 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: mail3.sankuai.info
PTR record proves mail server legitimacy
MX: mail3.sankuai.info
Mail server at mail3.sankuai.info
→
PTR Record
No PTR record
⚠️ Mail server mail3.sankuai.info (mail3.sankuai.info) lacks a PTR record. Many receiving servers require matching forward and reverse DNS for spam prevention.
Mail Server Identity: mx01.meituan.com
PTR record proves mail server legitimacy
MX: mx01.meituan.com
Mail server at mx01.meituan.com
→
PTR Record
No PTR record
⚠️ Mail server mx01.meituan.com (mx01.meituan.com) lacks a PTR record. Many receiving servers require matching forward and reverse DNS for spam prevention.
Mail Server Identity: mx02.meituan.com
PTR record proves mail server legitimacy
MX: mx02.meituan.com
Mail server at mx02.meituan.com
→
PTR Record
No PTR record
⚠️ Mail server mx02.meituan.com (mx02.meituan.com) lacks a PTR record. Many receiving servers require matching forward and reverse DNS for spam prevention.
Mail Server Reputation: mail3.sankuai.info
RBL check ensures server is not blacklisted
MX: mail3.sankuai.info
Mail server at mail3.sankuai.info
→
RBL Status
Not blacklisted
Mail Server Reputation: mx01.meituan.com
RBL check ensures server is not blacklisted
MX: mx01.meituan.com
Mail server at mx01.meituan.com
→
RBL Status
Not blacklisted
Mail Server Reputation: mx02.meituan.com
RBL check ensures server is not blacklisted
MX: mx02.meituan.com
Mail server at mx02.meituan.com
→
RBL Status
Not blacklisted
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 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
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/sankuai.com.svg" alt="Email Security Grade">
Want to re-scan this domain for updated results?
Scan sankuai.com Again