Identity
3
F
trip.com
Posture Score: 56/100
Scanned May 29, 2026 at 12:45 PM UTC
Score History
Attack Surface
92
Reputation
73
Identity Findings
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 'selector1'
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 'google'
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 'default'
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.
Subdomains have no DMARC enforcement
sp=none explicitly allows unauthenticated mail from subdomains.
💡 Add sp=reject (or sp=quarantine) to your DMARC record to protect subdomains.
TLS certificate hostname mismatch on mx1.trip.com.ctripgslb.com
Certificate subject '*.ctrip.com' does not match hostname 'mx1.trip.com.ctripgslb.com'. SANs: *.ctrip.com, *.b2b.vipdlt.com, *.c-ctrip.com, *.ctrip-ttd.hk, *.ctrip.cn, *.ctrip.co.kr, *.ctrip.com.hk, *.ctrip.my, *.ctrip.sg, *.ctripbiz.com, *.english.c-ctrip.com, *.flightai.aero, *.hhtravel.com, *.hotelwholesaler.net, *.joyfuljourneysgp.com, *.lvtds.com, *.shuntu.cn, *.suanya.cn, *.suanya.com, *.tieyou.com, *.toptown.cn, *.toursbms.com, *.tripcdn.cn, *.vipdlt.com, *.ctrip.co.id, *.ctrip.net, *.ctripbuy.hk, *.hhtravel.com.tw, *.xiecheng.com, *.corporatetravel.ctrip.com, *.english.ctrip.com, *.flights.ctrip.com, *.payment.ctrip.com, *.secure.ctrip.com, *.ws.ctrip.com, *.antianbaoche.com, *.gangtaihuochepiao.com, *.guojihuochepiao.com, *.guoneihuochepiao.com, *.guoneijiudian.com, *.guoneizuche.com, *.haiwaijiudian.com, *.haiwaiminsukezhan.com, *.jiesongjizhan.com, *.lvyougouwushangcheng.com, ctrip.com
💡 Obtain a TLS certificate that matches the mail server hostname.
TLS certificate hostname mismatch on mx2.trip.com.ctripgslb.com
Certificate subject '*.ctrip.com' does not match hostname 'mx2.trip.com.ctripgslb.com'. SANs: *.ctrip.com, *.b2b.vipdlt.com, *.c-ctrip.com, *.ctrip-ttd.hk, *.ctrip.cn, *.ctrip.co.kr, *.ctrip.com.hk, *.ctrip.my, *.ctrip.sg, *.ctripbiz.com, *.english.c-ctrip.com, *.flightai.aero, *.hhtravel.com, *.hotelwholesaler.net, *.joyfuljourneysgp.com, *.lvtds.com, *.shuntu.cn, *.suanya.cn, *.suanya.com, *.tieyou.com, *.toptown.cn, *.toursbms.com, *.tripcdn.cn, *.vipdlt.com, *.ctrip.co.id, *.ctrip.net, *.ctripbuy.hk, *.hhtravel.com.tw, *.xiecheng.com, *.corporatetravel.ctrip.com, *.english.ctrip.com, *.flights.ctrip.com, *.payment.ctrip.com, *.secure.ctrip.com, *.ws.ctrip.com, *.antianbaoche.com, *.gangtaihuochepiao.com, *.guojihuochepiao.com, *.guoneihuochepiao.com, *.guoneijiudian.com, *.guoneizuche.com, *.haiwaijiudian.com, *.haiwaiminsukezhan.com, *.jiesongjizhan.com, *.lvyougouwushangcheng.com, ctrip.com
💡 Obtain a TLS certificate that matches the mail server hostname.
TLS certificate hostname mismatch on mx3.trip.com.ctripgslb.com
Certificate subject '*.ctrip.com' does not match hostname 'mx3.trip.com.ctripgslb.com'. SANs: *.ctrip.com, *.b2b.vipdlt.com, *.c-ctrip.com, *.ctrip-ttd.hk, *.ctrip.cn, *.ctrip.co.kr, *.ctrip.com.hk, *.ctrip.my, *.ctrip.sg, *.ctripbiz.com, *.english.c-ctrip.com, *.flightai.aero, *.hhtravel.com, *.hotelwholesaler.net, *.joyfuljourneysgp.com, *.lvtds.com, *.shuntu.cn, *.suanya.cn, *.suanya.com, *.tieyou.com, *.toptown.cn, *.toursbms.com, *.tripcdn.cn, *.vipdlt.com, *.ctrip.co.id, *.ctrip.net, *.ctripbuy.hk, *.hhtravel.com.tw, *.xiecheng.com, *.corporatetravel.ctrip.com, *.english.ctrip.com, *.flights.ctrip.com, *.payment.ctrip.com, *.secure.ctrip.com, *.ws.ctrip.com, *.antianbaoche.com, *.gangtaihuochepiao.com, *.guojihuochepiao.com, *.guoneihuochepiao.com, *.guoneijiudian.com, *.guoneizuche.com, *.haiwaijiudian.com, *.haiwaiminsukezhan.com, *.jiesongjizhan.com, *.lvyougouwushangcheng.com, ctrip.com
💡 Obtain a TLS certificate that matches the mail server hostname.
Cannot check DNS consistency — no NS records
No nameserver records could be retrieved for consistency checking.
💡 Ensure NS records are properly configured.
Subdomain policy (sp=none) is weaker than domain policy (p=reject)
The subdomain policy is less restrictive than the organizational domain policy, leaving subdomains more vulnerable.
💡 Set sp=reject or remove sp= to inherit the domain policy.
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.trip.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.
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@trip.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 (32 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.
No external DMARC report destinations
All DMARC report URIs point to the same domain — no external authorization needed.
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.
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.
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 mx1.trip.com.ctripgslb.com
Detected open mail-related ports: 25, 587
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
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 3 different /16 networks, providing good diversity.
SOA record parameters
Serial: 2019127835, Refresh: 60s, Retry: 300s, Expire: 604800s, Min TTL: 900s
Attack Surface Findings
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.
3 subdomain(s) discovered for trip.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 trip.com and its subdomains. Each certificate reveals subdomain names.
Microsoft Autodiscover endpoint detected (authenticated)
The Autodiscover endpoint at autodiscover.trip.com is active and requires authentication.
1 email SRV record(s) found
Email service SRV records expose mail server configuration for automatic client setup.
Reputation Findings
Listed on dnsbl.spfbl.net
103.158.15.8 (mx2.trip.com.ctripgslb.com) is listed on blacklist dnsbl.spfbl.net (response: 127.0.0.4).
💡 Visit the dnsbl.spfbl.net website to request delisting. Investigate the root cause (compromised account, open relay, spam) before requesting removal.
SMTP banner mismatch: overseasmx1.ctrip.com
The SMTP banner identifies as 'overseasmx1.ctrip.com' but the MX hostname is 'mx1.trip.com.ctripgslb.com' and PTR resolves to 'overseamail51.trip.com'. Microsoft and other receivers flag this mismatch as suspicious infrastructure.
💡 Configure the SMTP server banner to match the MX hostname or PTR record (mx1.trip.com.ctripgslb.com).
Missing Strict-Transport-Security on trip.com
The Strict-Transport-Security header is not set on https://trip.com.
💡 Add the Strict-Transport-Security header with a max-age of at least 31536000 (1 year) and include the includeSubDomains directive.
security.txt present
Found security.txt at https://trip.com/.well-known/security.txt.
TLS certificate valid for 92 days
Certificate for trip.com expires on 2026-08-30.
Certificate issued by GlobalSign RSA OV SSL CA 2018
The certificate for trip.com is issued by a third-party CA.
Signature algorithm: rsa-sha256
The certificate for trip.com uses an acceptable signature algorithm.
RSA key: 2048 bits
The certificate for trip.com uses an adequate RSA key of 2048 bits.
SCTs present in certificate
The certificate for trip.com contains Signed Certificate Timestamps.
No weak ciphers detected
No known weak cipher suites detected on trip.com.
Domain valid for 568 days
Domain trip.com expires on 2027-12-19.
Domain transfer and delete locks enabled
Domain trip.com has clientTransferProhibited and clientDeleteProhibited locks.
No disposable email provider MX records
MX records for trip.com do not match known disposable email provider patterns.
Domain is 10336 days old
Domain trip.com was registered 1998-02-09.
No wildcard MX records
No wildcard MX records detected for trip.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 (mx2.trip.com.ctripgslb.com) uses TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 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.
Could not connect to webmail.trip.com
HTTPS request to https://webmail.trip.com failed or timed out.
WHOIS registration data
Registrar: MarkMonitor Inc. | Created: 1998-02-09 | Expires: 2027-12-19 | Updated: 2019-06-13
WHOIS privacy protection not detected
Domain trip.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: rip.com (has MX!), tip.com (has MX!), trp.com (has MX!), rtip.com (has MX!), trpi.com (has MX!)
26 registered lookalike domain(s) that could be used for phishing against your brand. Showing top 5 of 26. 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: mx1.trip.com.ctripgslb.com
PTR record proves mail server legitimacy
MX: mx1.trip.com.ctripgslb.com
Mail server at 103.143.160.136
→
PTR Record
Reverse DNS: overseamail51.trip.com
Mail Server Identity: mx2.trip.com.ctripgslb.com
PTR record proves mail server legitimacy
MX: mx2.trip.com.ctripgslb.com
Mail server at 103.158.15.8
→
PTR Record
Reverse DNS: overseamail53.trip.com
Mail Server Identity: mx3.trip.com.ctripgslb.com
PTR record proves mail server legitimacy
MX: mx3.trip.com.ctripgslb.com
Mail server at 60.204.73.120
→
PTR Record
Reverse DNS: mail57.ctrip.com
Mail Server Reputation: mx1.trip.com.ctripgslb.com
RBL check ensures server is not blacklisted
MX: mx1.trip.com.ctripgslb.com
Mail server at 103.143.160.136
→
RBL Status
Not blacklisted
Mail Server Reputation: mx2.trip.com.ctripgslb.com
RBL check ensures server is not blacklisted
MX: mx2.trip.com.ctripgslb.com
Mail server at 103.158.15.8
→
RBL Status
Not blacklisted
Mail Server Reputation: mx3.trip.com.ctripgslb.com
RBL check ensures server is not blacklisted
MX: mx3.trip.com.ctripgslb.com
Mail server at 60.204.73.120
→
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-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/trip.com.svg" alt="Email Security Grade">
Want to re-scan this domain for updated results?
Scan trip.com Again