Identity
0
F
gitee.com
Posture Score: 57/100
Scanned May 30, 2026 at 5:22 AM UTC
Attack Surface
90
Reputation
80
Identity Findings
External report destination not authorized: oschina.cn
The rua= URI sends reports to oschina.cn, but no authorization record exists at gitee.com._report._dmarc.oschina.cn. Reports will be silently dropped by compliant receivers.
💡 Ask the owner of oschina.cn to publish a TXT record at gitee.com._report._dmarc.oschina.cn containing 'v=DMARC1'.
External report destination not authorized: oschina.cn
The ruf= URI sends reports to oschina.cn, but no authorization record exists at gitee.com._report._dmarc.oschina.cn. Reports will be silently dropped by compliant receivers.
💡 Ask the owner of oschina.cn to publish a TXT record at gitee.com._report._dmarc.oschina.cn containing 'v=DMARC1'.
Does not meet bulk sender requirements
Google and Yahoo require all bulk senders to have SPF+DKIM, DMARC, and one-click unsubscribe. Issues: Neither SPF nor DKIM is configured (at least one required); SPF not published (recommended alongside DKIM)
💡 Publish SPF, DKIM, and DMARC records. Implement RFC 8058 one-click unsubscribe for marketing mail.
FCrDNS mismatch: 47.246.99.195 → reachsmartdwell.com does not resolve back
PTR for 47.246.99.195 is reachsmartdwell.com, but reachsmartdwell.com does not resolve back to 47.246.99.195.
💡 Ensure the PTR hostname resolves back to the original IP address.
FCrDNS failure: no PTR for 47.246.137.47 (mxn.mxhichina.com)
The IP 47.246.137.47 has no PTR record. Forward-confirmed reverse DNS requires a PTR that resolves back to the IP.
💡 Configure a PTR record for the IP that matches the mail server hostname.
FCrDNS mismatch: 47.246.136.231 → reachsmartdwell.com does not resolve back
PTR for 47.246.136.231 is reachsmartdwell.com, but reachsmartdwell.com does not resolve back to 47.246.136.231.
💡 Ensure the PTR hostname resolves back to the original IP address.
Nameserver unresponsive: sv2.bdydns.cn
The nameserver sv2.bdydns.cn is not responding on port 53.
💡 Verify that sv2.bdydns.cn is properly configured and accessible.
Nameserver unresponsive: sv3.bdydns.cn
The nameserver sv3.bdydns.cn is not responding on port 53.
💡 Verify that sv3.bdydns.cn is properly configured and accessible.
Nameserver unresponsive: sv4.bdydns.cn
The nameserver sv4.bdydns.cn is not responding on port 53.
💡 Verify that sv4.bdydns.cn is properly configured and accessible.
Nameserver unresponsive: sv1.bdydns.cn
The nameserver sv1.bdydns.cn is not responding on port 53.
💡 Verify that sv1.bdydns.cn is properly configured and accessible.
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.gitee.com
External DMARC report destination not authorized: oschina.cn
The rua= URI points to oschina.cn but no authorization record exists at gitee.com._report._dmarc.oschina.cn.
💡 Ask the owner of oschina.cn to publish a TXT record at gitee.com._report._dmarc.oschina.cn with 'v=DMARC1'.
No PTR record for MX IP: 47.246.137.47
The IP 47.246.137.47 (for mxn.mxhichina.com) has no reverse DNS record.
💡 Configure a PTR record for the mail server IP.
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.gitee.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"
DMARC percentage is 50% (not fully enforced)
Only 50% 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@gitee.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.
Very low TTL on TXT record: 1s
The TXT record has a TTL of 1s or less (below 300s).
💡 Increase the TTL to at least 300 seconds unless frequent changes are expected.
Very low TTL on DMARC record: 1s
The DMARC record has a TTL of 1s 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 (39 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.
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 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.
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.
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 mxw.mxhichina.com
Detected open mail-related ports: 25
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.
MX IP network diversity
All MX IPs are in the same /16 network. Consider diversifying across networks for resilience.
SOA record parameters
Serial: 2019085450, Refresh: 3600s, Retry: 300s, Expire: 2592000s, Min TTL: 120s
Attack Surface Findings
HINFO record exposes system information
An HINFO record for gitee.com reveals hardware/OS details: CPU=, OS=. This aids attacker reconnaissance.
💡 Remove the HINFO record from public DNS. HINFO records are rarely needed and expose unnecessary system details.
LOC record exposes geographic location
A LOC record for gitee.com reveals the physical location of infrastructure. This aids targeted attacks.
💡 Remove the LOC record from public DNS unless geographic information is intentionally published.
RP record exposes responsible person
An RP (Responsible Person) record for gitee.com reveals contact information: gitee.com-31ba39d0fd3.baiduads.com.. This can be used for social engineering.
💡 Remove the RP record if the contact information is not intended to be public.
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 email autodiscovery endpoints detected
No Microsoft Autodiscover, Mozilla Autoconfig, or email SRV records were found.
3 subdomain(s) discovered for gitee.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 gitee.com and its subdomains. Each certificate reveals subdomain names.
NSEC3 authenticated denial of existence
The domain uses NSEC3 with -1 iteration(s) and salt '-'.
DNSSEC is enabled
DNSKEY and/or DS records are present, indicating DNSSEC is configured.
Reputation Findings
Missing domain locks: clientTransferProhibited, clientDeleteProhibited
Domain gitee.com is missing protective locks: clientTransferProhibited, clientDeleteProhibited.
💡 Enable clientTransferProhibited and clientDeleteProhibited locks through your registrar to prevent unauthorized transfers or deletions.
SMTP banner mismatch: mx1.aliyun-inc.com
The SMTP banner identifies as 'mx1.aliyun-inc.com' but the MX hostname is 'mxn.mxhichina.com'. Microsoft and other receivers flag this mismatch as suspicious infrastructure.
💡 Configure the SMTP server banner to match the MX hostname or PTR record (mxn.mxhichina.com).
Missing Strict-Transport-Security on gitee.com
The Strict-Transport-Security header is not set on https://gitee.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://gitee.com/.well-known/security.txt.
TLS certificate valid for 266 days
Certificate for gitee.com expires on 2027-02-20.
Certificate issued by TrustAsia DV TLS RSA CA 2024
The certificate for gitee.com is issued by a third-party CA.
Signature algorithm: rsa-sha256
The certificate for gitee.com uses an acceptable signature algorithm.
RSA key: 2048 bits
The certificate for gitee.com uses an adequate RSA key of 2048 bits.
SCTs present in certificate
The certificate for gitee.com contains Signed Certificate Timestamps.
No weak ciphers detected
No known weak cipher suites detected on gitee.com.
Domain valid for 644 days
Domain gitee.com expires on 2028-03-04.
No disposable email provider MX records
MX records for gitee.com do not match known disposable email provider patterns.
Domain is 6295 days old
Domain gitee.com was registered 2009-03-04.
No wildcard MX records
No wildcard MX records detected for gitee.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 (mxn.mxhichina.com) uses TLSv1.3 with cipher TLS_AES_256_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.gitee.com
HTTPS request to https://webmail.gitee.com failed or timed out.
WHOIS registration data
Registrar: Alibaba Cloud Computing (Beijing) Co., Ltd. | Created: 2009-03-04 | Expires: 2028-03-04 | Updated: 2025-04-01
WHOIS privacy protection not detected
Domain gitee.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: itee.com (has MX!), gite.com (has MX!), igtee.com (has MX!), fitee.com (has MX!), titee.com (has MX!)
27 registered lookalike domain(s) that could be used for phishing against your brand. Showing top 5 of 27. 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: quarantine
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: quarantine
⚠️ 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: mxn.mxhichina.com
PTR record proves mail server legitimacy
MX: mxn.mxhichina.com
Mail server at 47.246.136.231
→
PTR Record
Reverse DNS: reachsmartdwell.com
Mail Server Identity: mxw.mxhichina.com
PTR record proves mail server legitimacy
MX: mxw.mxhichina.com
Mail server at 47.246.99.195
→
PTR Record
Reverse DNS: reachsmartdwell.com
Mail Server Reputation: mxn.mxhichina.com
RBL check ensures server is not blacklisted
MX: mxn.mxhichina.com
Mail server at 47.246.136.231
→
RBL Status
Not blacklisted
Mail Server Reputation: mxw.mxhichina.com
RBL check ensures server is not blacklisted
MX: mxw.mxhichina.com
Mail server at 47.246.99.195
→
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: quarantine
→
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/gitee.com.svg" alt="Email Security Grade">
Want to re-scan this domain for updated results?
Scan gitee.com Again