Identity
8
F
moneycontrol.com
Posture Score: 56/100
Scanned May 28, 2026 at 12:32 AM UTC
Attack Surface
83
Reputation
77
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.
SPF exceeds 10-lookup limit (17 lookups)
RFC 7208 limits SPF to 10 DNS lookups. Exceeding this causes PermError and SPF failures.
💡 Flatten your SPF record by replacing includes with direct ip4/ip6 mechanisms.
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.
Weak DKIM RSA key (~1296 bits) for selector 'dkim'
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.
External report destination not authorized: nw18.com
The rua= URI sends reports to nw18.com, but no authorization record exists at moneycontrol.com._report._dmarc.nw18.com. Reports will be silently dropped by compliant receivers.
💡 Ask the owner of nw18.com to publish a TXT record at moneycontrol.com._report._dmarc.nw18.com containing 'v=DMARC1'.
TLS certificate hostname mismatch on mx1.hc1534-53.ap.iphmx.com
Certificate subject '*.nw18.com' does not match hostname 'mx1.hc1534-53.ap.iphmx.com'. SANs: *.nw18.com, nw18.com
💡 Obtain a TLS certificate that matches the mail server hostname.
TLS certificate hostname mismatch on mx2.hc1534-53.ap.iphmx.com
Certificate subject '*.nw18.com' does not match hostname 'mx2.hc1534-53.ap.iphmx.com'. SANs: *.nw18.com, nw18.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.
External DMARC report destination not authorized: nw18.com
The rua= URI points to nw18.com but no authorization record exists at moneycontrol.com._report._dmarc.nw18.com.
💡 Ask the owner of nw18.com to publish a TXT record at moneycontrol.com._report._dmarc.nw18.com with 'v=DMARC1'.
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.moneycontrol.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@moneycontrol.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 MX records: 30s
2 MX records have a TTL of 30s or less (below 300s).
💡 Increase the TTL to at least 300 seconds unless frequent changes are expected.
Very low TTL on SPF record: 30s
The SPF record has a TTL of 30s or less (below 300s).
💡 Increase the TTL to at least 300 seconds unless frequent changes are expected.
Very low TTL on TXT records: 30s
11 TXT records have a TTL of 30s or less (below 300s).
💡 Increase the TTL to at least 300 seconds unless frequent changes are expected.
SPF record length OK (127 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.
Subdomains protected (sp=reject)
DMARC subdomain policy enforces quarantine or reject on unauthenticated subdomain mail.
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.
IPv6 readiness is good
IPv6 records are present and properly configured.
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.hc1534-53.ap.iphmx.com
Detected open mail-related ports: 25
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
All MX IPs are in the same /16 network. Consider diversifying across networks for resilience.
SOA record parameters
Serial: 2020083865, Refresh: 3600s, Retry: 600s, Expire: 604800s, Min TTL: 300s
Attack Surface Findings
Non-responsive IP for www.moneycontrol.com: 2a02:26f0:9b00:48c::3393
The subdomain www.moneycontrol.com resolves to 2a02:26f0:9b00:48c::3393 which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2a02:26f0:9b00:48c::3393 is operational or remove the DNS record for www.moneycontrol.com.
Non-responsive IP for www.moneycontrol.com: 2a02:26f0:9b00:49c::3393
The subdomain www.moneycontrol.com resolves to 2a02:26f0:9b00:49c::3393 which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2a02:26f0:9b00:49c::3393 is operational or remove the DNS record for www.moneycontrol.com.
Non-responsive IP for api.moneycontrol.com: 2a02:26f0:9b00:480::3379
The subdomain api.moneycontrol.com resolves to 2a02:26f0:9b00:480::3379 which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2a02:26f0:9b00:480::3379 is operational or remove the DNS record for api.moneycontrol.com.
Non-responsive IP for api.moneycontrol.com: 2a02:26f0:9b00:495::3379
The subdomain api.moneycontrol.com resolves to 2a02:26f0:9b00:495::3379 which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2a02:26f0:9b00:495::3379 is operational or remove the DNS record for api.moneycontrol.com.
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.
No email autodiscovery endpoints detected
No Microsoft Autodiscover, Mozilla Autoconfig, or email SRV records were found.
2 subdomain(s) discovered for moneycontrol.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 moneycontrol.com and its subdomains. Each certificate reveals subdomain names.
NSEC3 authenticated denial of existence
The domain uses NSEC3 with 0 iteration(s) and salt '-'.
DNSSEC is enabled
DNSKEY and/or DS records are present, indicating DNSSEC is configured.
Reputation Findings
TLS certificate expires in 12 days
Certificate for moneycontrol.com expires on 2026-06-09 (12 days).
💡 Renew the TLS certificate urgently — it expires within 14 days.
Missing domain locks: clientTransferProhibited, clientDeleteProhibited
Domain moneycontrol.com is missing protective locks: clientTransferProhibited, clientDeleteProhibited.
💡 Enable clientTransferProhibited and clientDeleteProhibited locks through your registrar to prevent unauthorized transfers or deletions.
Not listed on any DNS blacklists
Domain and MX IPs checked against 55 DNSBLs — no listings found.
HSTS enabled with preload on moneycontrol.com
Strict-Transport-Security: max-age=86400 ; preload
security.txt present
Found security.txt at https://moneycontrol.com/.well-known/security.txt.
Certificate issued by R13
The certificate for moneycontrol.com is issued by a third-party CA.
Signature algorithm: rsa-sha256
The certificate for moneycontrol.com uses an acceptable signature algorithm.
RSA key: 2048 bits
The certificate for moneycontrol.com uses an adequate RSA key of 2048 bits.
SCTs present in certificate
The certificate for moneycontrol.com contains Signed Certificate Timestamps.
No weak ciphers detected
No known weak cipher suites detected on moneycontrol.com.
Domain valid for 1372 days
Domain moneycontrol.com expires on 2030-02-28.
No disposable email provider MX records
MX records for moneycontrol.com do not match known disposable email provider patterns.
Domain is 9950 days old
Domain moneycontrol.com was registered 1999-02-28.
No wildcard MX records
No wildcard MX records detected for moneycontrol.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 (mx1.hc1534-53.ap.iphmx.com) uses TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 including Forward Secrecy.
SMTP banner from hosted mail provider
The MX (mx1.hc1534-53.ap.iphmx.com) is a hosted mail service. Banner alignment is managed by the provider and not actionable by the domain owner.
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.moneycontrol.com
HTTPS request to https://webmail.moneycontrol.com failed or timed out.
WHOIS registration data
Registrar: PDR Ltd. d/b/a PublicDomainRegistry.com | Created: 1999-02-28 | Expires: 2030-02-28 | Updated: 2025-10-31
WHOIS privacy protection enabled
Domain moneycontrol.com has WHOIS privacy/redaction enabled.
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: moeycontrol.com (has MX!), moneycntrol.com (has MX!), moneycotrol.com (has MX!), moneycontol.com (has MX!), moneycontrl.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: 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.hc1534-53.ap.iphmx.com
PTR record proves mail server legitimacy
MX: mx1.hc1534-53.ap.iphmx.com
Mail server at 139.138.31.187
→
PTR Record
Reverse DNS: 187.31.138.139.in-addr.arpa.ap.iphmx.com
Mail Server Identity: mx2.hc1534-53.ap.iphmx.com
PTR record proves mail server legitimacy
MX: mx2.hc1534-53.ap.iphmx.com
Mail server at 139.138.42.102
→
PTR Record
Reverse DNS: 102.42.138.139.in-addr.arpa.ap.iphmx.com
Mail Server Reputation: mx1.hc1534-53.ap.iphmx.com
RBL check ensures server is not blacklisted
MX: mx1.hc1534-53.ap.iphmx.com
Mail server at 139.138.31.187
→
RBL Status
Not blacklisted
Mail Server Reputation: mx2.hc1534-53.ap.iphmx.com
RBL check ensures server is not blacklisted
MX: mx2.hc1534-53.ap.iphmx.com
Mail server at 139.138.42.102
→
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/moneycontrol.com.svg" alt="Email Security Grade">
Want to re-scan this domain for updated results?
Scan moneycontrol.com Again