Identity
28
F
ruliweb.com
Posture Score: 44/100
Scanned May 29, 2026 at 3:11 AM UTC
Attack Surface
95
Reputation
8
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.ruliweb.com (e.g. "v=DMARC1; p=reject; rua=mailto:dmarc@ruliweb.com").
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.
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.
TLS certificate hostname mismatch on mailapp.hiworks.co.kr
Certificate subject '*.hiworks.com' does not match hostname 'mailapp.hiworks.co.kr'. SANs: *.hiworks.com, hiworks.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.
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.ruliweb.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.ruliweb.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@ruliweb.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 (38 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.
MX records are valid
All MX records are properly configured.
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.
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 mailapp.hiworks.co.kr
Detected open mail-related ports: 25, 110, 465, 587, 995
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
MX IPs span 3 different /16 networks, providing good diversity.
SOA record parameters
Serial: 1, Refresh: 7200s, Retry: 900s, Expire: 1209600s, Min TTL: 86400s
Attack Surface Findings
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 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 ruliweb.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 ruliweb.com and its subdomains. Each certificate reveals subdomain names.
Wildcard DNS record detected
A wildcard DNS record exists for *.ruliweb.com, resolving to 103.24.8.4. Wildcard records make subdomain brute-forcing less effective but may mask misconfigurations.
Microsoft Autodiscover endpoint detected
The Autodiscover endpoint at autodiscover.ruliweb.com responded with HTTP 404.
Reputation Findings
Listed on dnsbl.spfbl.net
121.254.168.55 (mailapp.hiworks.co.kr) 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.
Listed on korea.services.net
121.254.168.55 (mailapp.hiworks.co.kr) 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.
Listed on korea.services.net
211.47.76.59 (mailapp.hiworks.co.kr) 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.
Listed on dnsbl.spfbl.net
45.120.71.59 (mailapp.hiworks.co.kr) is listed on blacklist dnsbl.spfbl.net (response: 127.0.0.5).
💡 Visit the dnsbl.spfbl.net website to request delisting. Investigate the root cause (compromised account, open relay, spam) before requesting removal.
Listed on korea.services.net
45.120.71.59 (mailapp.hiworks.co.kr) 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.
SMTP banner mismatch: hi
The SMTP banner identifies as 'hi' but the MX hostname is 'mailapp.hiworks.co.kr' and PTR resolves to 'mailapp.hiworks.co.kr'. Microsoft and other receivers flag this mismatch as suspicious infrastructure.
💡 Configure the SMTP server banner to match the MX hostname or PTR record (mailapp.hiworks.co.kr).
Missing Strict-Transport-Security on webmail.ruliweb.com
The Strict-Transport-Security header is not set on https://webmail.ruliweb.com.
💡 Add the Strict-Transport-Security header with a max-age of at least 31536000 (1 year) and include the includeSubDomains directive.
Weak TLS configuration on primary MX
The primary MX server supports deprecated TLS versions or weak cipher suites: No Forward Secrecy (PFS): AES128-GCM-SHA256. Modern receivers penalize reputation for lack of strong encryption.
💡 Disable TLS 1.0/1.1, remove weak ciphers (RC4, 3DES), and ensure Forward Secrecy (ECDHE) is preferred.
HSTS enabled but missing preload directive on ruliweb.com
Strict-Transport-Security: max-age=63072000
💡 Add the "preload" directive to the HSTS header and submit the domain to hstspreload.org.
security.txt present
Found security.txt at https://ruliweb.com/.well-known/security.txt.
TLS certificate valid for 58 days
Certificate for ruliweb.com expires on 2026-07-26.
Certificate issued by Sectigo RSA Organization Validation Secure Server CA
The certificate for ruliweb.com is issued by a third-party CA.
Signature algorithm: rsa-sha256
The certificate for ruliweb.com uses an acceptable signature algorithm.
RSA key: 2048 bits
The certificate for ruliweb.com uses an adequate RSA key of 2048 bits.
SCTs present in certificate
The certificate for ruliweb.com contains Signed Certificate Timestamps.
No weak ciphers detected
No known weak cipher suites detected on ruliweb.com.
No disposable email provider MX records
MX records for ruliweb.com do not match known disposable email provider patterns.
No wildcard MX records
No wildcard MX records detected for ruliweb.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.
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 lookup failed
Could not retrieve WHOIS data for ruliweb.com.
Could not determine domain age
WHOIS creation date could not be parsed for ruliweb.com.
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: uliweb.com (has MX!), rulieb.com (has MX!), ruliwb.com (has MX!), ruliwe.com (has MX!), rulwieb.com (has MX!)
11 registered lookalike domain(s) that could be used for phishing against your brand. Showing top 5 of 11. 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: mailapp.hiworks.co.kr
PTR record proves mail server legitimacy
MX: mailapp.hiworks.co.kr
Mail server at 211.47.76.59
→
PTR Record
Reverse DNS: mailapp.hiworks.co.kr
Mail Server Reputation: mailapp.hiworks.co.kr
RBL check ensures server is not blacklisted
MX: mailapp.hiworks.co.kr
Mail server at 211.47.76.59
→
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-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/ruliweb.com.svg" alt="Email Security Grade">
Want to re-scan this domain for updated results?
Scan ruliweb.com Again