Identity
44
D
tistory.com
Posture Score: 69/100
Scanned May 30, 2026 at 2:08 PM UTC
Attack Surface
87
Reputation
75
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.tistory.com (e.g. "v=DMARC1; p=reject; rua=mailto:dmarc@tistory.com").
No MX records found
The domain has no MX records and cannot receive email.
💡 Publish MX records pointing to your mail server(s).
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.
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.tistory.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.tistory.com/.well-known/mta-sts.txt
SOA MNAME does not resolve
The primary nameserver (MNAME) 'ns.kakaocorp.com' does not resolve to any IP address.
💡 Ensure the MNAME field points to a resolvable, authoritative nameserver.
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@tistory.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 (33 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.
NS delegation is properly configured
All nameservers are responsive, consistent, and properly secured.
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.
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
No DKIM signing detected. RFC 8058 one-click unsubscribe requires DKIM-signed List-Unsubscribe headers.
FCrDNS check skipped — no MX records
Cannot perform FCrDNS without MX records.
SOA record parameters
Serial: 1668574855, Refresh: 1800s, Retry: 600s, Expire: 2419200s, Min TTL: 300s
Attack Surface Findings
Non-routable IPv4 in public DNS: dev.tistory.com → 10.19.240.242
The subdomain dev.tistory.com resolves to non-routable IP 10.19.240.242, leaking internal network information.
💡 Remove non-routable IPs from public DNS or implement split-horizon DNS.
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 excessive DNS information exposure detected
No HINFO, LOC, RP records, version disclosures, or zone walking vulnerabilities were found.
4 subdomain(s) discovered for tistory.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 tistory.com and its subdomains. Each certificate reveals subdomain names.
Wildcard DNS record detected
A wildcard DNS record exists for *.tistory.com, resolving to 121.53.204.130. Wildcard records make subdomain brute-forcing less effective but may mask misconfigurations.
Microsoft Autodiscover endpoint detected
The Autodiscover endpoint at autodiscover.tistory.com responded with HTTP 404.
Reputation Findings
Missing domain locks: clientDeleteProhibited
Domain tistory.com is missing protective locks: clientDeleteProhibited.
💡 Enable clientTransferProhibited and clientDeleteProhibited locks through your registrar to prevent unauthorized transfers or deletions.
SMTP banner mismatch: dmail-kairos-ayvm10
The SMTP banner identifies as 'dmail-kairos-ayvm10' but the MX hostname is 'aspmx.daum.net'. Microsoft and other receivers flag this mismatch as suspicious infrastructure.
💡 Configure the SMTP server banner to match the MX hostname or PTR record (aspmx.daum.net).
HSTS effectively disabled on tistory.com (max-age=0)
The HSTS header has max-age=0, which instructs browsers to forget the HSTS policy. This provides no transport security enforcement.
💡 Set max-age to at least 31536000 (1 year) to enforce HTTPS.
Wildcard MX records detected
Domain tistory.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 webmail.tistory.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://tistory.com/.well-known/security.txt.
TLS certificate valid for 137 days
Certificate for tistory.com expires on 2026-10-14.
Certificate issued by Thawte TLS RSA CA G1
The certificate for tistory.com is issued by a third-party CA.
Signature algorithm: rsa-sha256
The certificate for tistory.com uses an acceptable signature algorithm.
RSA key: 2048 bits
The certificate for tistory.com uses an adequate RSA key of 2048 bits.
SCTs present in certificate
The certificate for tistory.com contains Signed Certificate Timestamps.
No weak ciphers detected
No known weak cipher suites detected on tistory.com.
Domain valid for 124 days
Domain tistory.com expires on 2026-10-01.
No disposable email provider MX records
MX records for tistory.com do not match known disposable email provider patterns.
Domain is 7545 days old
Domain tistory.com was registered 2005-10-01.
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 (aspmx.daum.net) uses TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 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.
WHOIS registration data
Registrar: Megazone Corp., dba HOSTING.KR | Created: 2005-10-01 | Expires: 2026-10-01 | Updated: 2025-09-23
WHOIS privacy protection not detected
Domain tistory.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: titory.com (has MX!), tisory.com (has MX!), tistoy.com (has MX!), tistroy.com (has MX!), ristory.com (has MX!)
19 registered lookalike domain(s) that could be used for phishing against your brand. Showing top 5 of 19. 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: aspmx.daum.net
PTR record proves mail server legitimacy
MX: aspmx.daum.net
Mail server at 121.53.85.23
→
PTR Record
No PTR record
⚠️ Mail server aspmx.daum.net (121.53.85.23) lacks a PTR record. Many receiving servers require matching forward and reverse DNS for spam prevention.
Mail Server Identity: alt.aspmx.daum.net
PTR record proves mail server legitimacy
MX: alt.aspmx.daum.net
Mail server at 121.53.85.23
→
PTR Record
No PTR record
⚠️ Mail server alt.aspmx.daum.net (121.53.85.23) lacks a PTR record. Many receiving servers require matching forward and reverse DNS for spam prevention.
Mail Server Reputation: aspmx.daum.net
RBL check ensures server is not blacklisted
MX: aspmx.daum.net
Mail server at 121.53.85.23
→
RBL Status
Not blacklisted
Mail Server Reputation: alt.aspmx.daum.net
RBL check ensures server is not blacklisted
MX: alt.aspmx.daum.net
Mail server at 121.53.85.23
→
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 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 failure reporting configured
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/tistory.com.svg" alt="Email Security Grade">
Want to re-scan this domain for updated results?
Scan tistory.com Again