← Back to Scanner
F

dcinside.com

Posture Score: 57/100

Scanned May 28, 2026 at 3:14 AM UTC

Identity

20

Attack Surface

91

Reputation

61

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.dcinside.com (e.g. "v=DMARC1; p=reject; rua=mailto:dmarc@dcinside.com").
critical
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.
critical
No STARTTLS support on mail.dcinside.com:25
The mail server does not advertise STARTTLS, meaning email is transmitted in plaintext.
💡 Enable STARTTLS on the mail server.
high
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.
high
Port 465 open but TLS handshake failed on mail.dcinside.com
Port 465 (SMTPS) is open but does not complete a TLS handshake.
💡 Ensure TLS is properly configured on port 465.
high
Cannot check DNS consistency — no NS records
No nameserver records could be retrieved for consistency checking.
💡 Ensure NS records are properly configured.
high
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.dcinside.com
medium
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.dcinside.com/.well-known/mta-sts.txt
medium
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.
medium
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"
medium
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@dcinside.com").
low
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.
low
SPF record is valid
The SPF record is properly configured with valid syntax and within lookup limits.
pass
SPF record length OK (181 bytes)
SPF record is within safe DNS packet size limits.
pass
DKIM cryptographic configuration is compliant
No RFC 8301 compliance issues detected in DKIM key configuration.
pass
SMTP security checks passed
No open relay, VRFY/EXPN, or banner disclosure issues detected.
pass
SMTP RFC 5321 compliance checks passed
The mail server accepts postmaster@ and abuse@ and uses a valid FQDN in EHLO.
pass
DNS TTL values follow best practices
All critical DNS record TTLs are within recommended ranges.
pass
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.
informational
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.
informational
No DANE/TLSA records found
DANE is not configured for any MX server. This is optional but provides strong certificate binding.
informational
No BIMI record found
BIMI is not configured. Your brand logo will not display in supporting email clients.
informational
Open mail ports on mail.dcinside.com
Detected open mail-related ports: 25, 110, 465, 587, 993, 995
informational
Domain is IPv4-only
No AAAA records found for the domain, MX servers, or nameservers. The domain operates on IPv4 only.
informational
RFC 8058 one-click unsubscribe assessment
No DKIM signing detected. RFC 8058 one-click unsubscribe requires DKIM-signed List-Unsubscribe headers.
informational
MX IP network diversity
All MX IPs are in the same /16 network. Consider diversifying across networks for resilience.
informational
SOA record parameters
Serial: 2021052111, Refresh: 1800s, Retry: 600s, Expire: 1209600s, Min TTL: 86400s
informational

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.
medium
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.
medium
DNS ANY query returns 9 record(s)
The DNS server responds to ANY queries with 9 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.
low
No subdomain takeover risks detected
All checked subdomains have valid, responsive targets.
pass
All MX records resolve correctly
No dangling MX records detected — all MX hostnames resolve to valid IP addresses.
pass
Explicit MX records present
The domain has explicit MX records — no implicit A-record fallback delivery.
pass
No internal information leakage detected
No non-routable IP addresses or internal references were found in public DNS records.
pass
No email autodiscovery endpoints detected
No Microsoft Autodiscover, Mozilla Autoconfig, or email SRV records were found.
pass
4 subdomain(s) discovered for dcinside.com
Subdomains were enumerated via Certificate Transparency logs, DNS wordlist brute-forcing, and DNS record analysis.
informational
0 certificate(s) found in CT logs
Certificate Transparency logs contain 0 certificate(s) for dcinside.com and its subdomains. Each certificate reveals subdomain names.
informational

Reputation Findings

Listed on korea.services.net
121.125.60.170 (mail.dcinside.com) is listed on blacklist korea.services.net (response: 127.0.0.2).
💡 Visit the korea.services.net website to request delisting. Investigate the root cause (compromised account, open relay, spam) before requesting removal.
critical
TLS certificate expires in 5 days
Certificate for dcinside.com expires on 2026-06-02 (5 days).
💡 Renew the TLS certificate urgently — it expires within 14 days.
critical
Missing domain locks: clientDeleteProhibited
Domain dcinside.com is missing protective locks: clientDeleteProhibited.
💡 Enable clientTransferProhibited and clientDeleteProhibited locks through your registrar to prevent unauthorized transfers or deletions.
high
HSTS enabled but missing preload directive on dcinside.com
Strict-Transport-Security: max-age=15768000
💡 Add the "preload" directive to the HSTS header and submit the domain to hstspreload.org.
low
security.txt present
Found security.txt at https://dcinside.com/.well-known/security.txt.
pass
Certificate issued by Thawte TLS RSA CA G1
The certificate for dcinside.com is issued by a third-party CA.
pass
Signature algorithm: rsa-sha256
The certificate for dcinside.com uses an acceptable signature algorithm.
pass
RSA key: 2048 bits
The certificate for dcinside.com uses an adequate RSA key of 2048 bits.
pass
SCTs present in certificate
The certificate for dcinside.com contains Signed Certificate Timestamps.
pass
No weak ciphers detected
No known weak cipher suites detected on dcinside.com.
pass
Domain valid for 2881 days
Domain dcinside.com expires on 2034-04-17.
pass
No disposable email provider MX records
MX records for dcinside.com do not match known disposable email provider patterns.
pass
Domain is 9536 days old
Domain dcinside.com was registered 2000-04-17.
pass
No wildcard MX records
No wildcard MX records detected for dcinside.com.
pass
TLD has good reputation
The .com TLD is not on known abuse watchlists.
pass
MX records point to stable infrastructure
No MX records point to known dynamic DNS service domains.
pass
Strong TLS configuration on primary MX
Primary MX (mail.dcinside.com) uses with cipher including Forward Secrecy.
pass
SMTP banner matches infrastructure identity
The SMTP banner (dcinside.com) aligns with the MX hostname (mail.dcinside.com).
pass
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.
informational
Abuse contacts found for MX IPs
Abuse contact information retrieved via abusix.org DNS lookup.
informational
PhishTank — API key required
PhishTank phishing database check requires an API key.
informational
Sender Score — API key required
Sender Score reputation check requires an API key.
informational
Cisco Talos — API key required
Cisco Talos IP reputation check requires an API key.
informational
Could not connect to webmail.dcinside.com
HTTPS request to https://webmail.dcinside.com failed or timed out.
informational
WHOIS registration data
Registrar: Whois Corp. | Created: 2000-04-17 | Expires: 2034-04-17 | Updated: 2024-04-21
informational
WHOIS privacy protection not detected
Domain dcinside.com does not appear to have WHOIS privacy protection. Registrant details may be publicly visible.
informational
Bulletproof Hosting Detection — API key required
Checking IPs against known bulletproof hosting providers requires a threat intelligence API key.
informational
Threat Intelligence Feeds — API key required
Checking domain against threat intelligence feeds requires API keys (e.g., VirusTotal, AbuseIPDB).
informational
Typosquat detected: cinside.com (has MX!), cdinside.com (has MX!), dcinisde.com (has MX!), dcinsdie.com (has MX!), ddinside.com (has MX!)
14 registered lookalike domain(s) that could be used for phishing against your brand. Showing top 5 of 14. Domains with MX records can send and receive email, making them high-risk phishing vectors.
informational

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: mail.dcinside.com
PTR record proves mail server legitimacy
MX: mail.dcinside.com Mail server at 121.125.60.170 PTR Record Reverse DNS: mail.dcinside.com
Mail Server Reputation: mail.dcinside.com
RBL check ensures server is not blacklisted
MX: mail.dcinside.com Mail server at 121.125.60.170 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:

dcinside.com Email Security Grade
<img src="https://scan.ractermx.com/badge/dcinside.com.svg" alt="Email Security Grade">

Want to re-scan this domain for updated results?

Scan dcinside.com Again