ajio.com

Name: ajio.com Email Security Posture Assessment
Creator: RacterMX
License: https://creativecommons.org/licenses/by-nc/4.0/

Posture Score: 48/100

Scanned May 27, 2026 at 9:52 PM UTC

Identity

Attack Surface

Reputation

Identity Findings

Weak DKIM RSA key (~1296 bits) for selector 's2'

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.

high

MX hostname does not resolve: au-mail.em.sdlproducts.com

The MX hostname has no A or AAAA records.

💡 Ensure the MX hostname resolves to a valid IP address.

high

TLS certificate hostname mismatch on mx01.ajio.com

Certificate subject 'gwsmtp012.ril.com' does not match hostname 'mx01.ajio.com'. SANs: mx02.relbio.com, mx01.relbio.com, relay03.ril.com, mx06.rfhospital.org, relay01.ril.com, mail06.visionexpress.in, mx01.recron.com, gwsmtp011.ril.com, mx03.resq.in, mx05.rfhospital.org, mx02.resq.in, mx04.reliancefoundation.org, mx05.resq.in, mx01.rfhospital.org, mx03.relbio.com, mx06.relbio.com, mx01.jiobp.com, mx04.recron.com, mx01.reliancefoundation.org, relay04.ril.com, mta3.gcptcl.in, mx02.qwik.co.in, mx03.rfhospital.org, relay06.ril.com, mta4.gcptcl.in, mx04.jiobp.com, mx06.recron.com, mail01.visionexpress.in, mail04.visionexpress.in, mx03.reliancefoundation.org, mx03.jiobp.com, mx03.recron.com, mx05.recron.com, gwhydsmtp013.ril.com, mx06.qwik.co.in, mx03.qwik.co.in, gwjgsmtp014.ril.com, mx05.reliancefoundation.org, relay02.ril.com, mx05.relbio.com, mx04.qwik.co.in, mx02.jiobp.com, mta5.gcptcl.in, gwsmtp012.ril.com, www.gwsmtp012.ril.com, gwsmtp015.ril.com, mx01.qwik.co.in, mail03.visionexpress.in, mx04.resq.in, mx06.resq.in, mx04.rfhospital.org

💡 Obtain a TLS certificate that matches the mail server hostname.

high

TLS certificate hostname mismatch on mx03.ajio.com

Certificate subject 'gwsmtp012.ril.com' does not match hostname 'mx03.ajio.com'. SANs: mx02.relbio.com, mx01.relbio.com, relay03.ril.com, mx06.rfhospital.org, relay01.ril.com, mail06.visionexpress.in, mx01.recron.com, gwsmtp011.ril.com, mx03.resq.in, mx05.rfhospital.org, mx02.resq.in, mx04.reliancefoundation.org, mx05.resq.in, mx01.rfhospital.org, mx03.relbio.com, mx06.relbio.com, mx01.jiobp.com, mx04.recron.com, mx01.reliancefoundation.org, relay04.ril.com, mta3.gcptcl.in, mx02.qwik.co.in, mx03.rfhospital.org, relay06.ril.com, mta4.gcptcl.in, mx04.jiobp.com, mx06.recron.com, mail01.visionexpress.in, mail04.visionexpress.in, mx03.reliancefoundation.org, mx03.jiobp.com, mx03.recron.com, mx05.recron.com, gwhydsmtp013.ril.com, mx06.qwik.co.in, mx03.qwik.co.in, gwjgsmtp014.ril.com, mx05.reliancefoundation.org, relay02.ril.com, mx05.relbio.com, mx04.qwik.co.in, mx02.jiobp.com, mta5.gcptcl.in, gwsmtp012.ril.com, www.gwsmtp012.ril.com, gwsmtp015.ril.com, mx01.qwik.co.in, mail03.visionexpress.in, mx04.resq.in, mx06.resq.in, mx04.rfhospital.org

💡 Obtain a TLS certificate that matches the mail server hostname.

high

TLS certificate hostname mismatch on mx04.ajio.com

Certificate subject 'gwsmtp012.ril.com' does not match hostname 'mx04.ajio.com'. SANs: mx02.relbio.com, mx01.relbio.com, relay03.ril.com, mx06.rfhospital.org, relay01.ril.com, mail06.visionexpress.in, mx01.recron.com, gwsmtp011.ril.com, mx03.resq.in, mx05.rfhospital.org, mx02.resq.in, mx04.reliancefoundation.org, mx05.resq.in, mx01.rfhospital.org, mx03.relbio.com, mx06.relbio.com, mx01.jiobp.com, mx04.recron.com, mx01.reliancefoundation.org, relay04.ril.com, mta3.gcptcl.in, mx02.qwik.co.in, mx03.rfhospital.org, relay06.ril.com, mta4.gcptcl.in, mx04.jiobp.com, mx06.recron.com, mail01.visionexpress.in, mail04.visionexpress.in, mx03.reliancefoundation.org, mx03.jiobp.com, mx03.recron.com, mx05.recron.com, gwhydsmtp013.ril.com, mx06.qwik.co.in, mx03.qwik.co.in, gwjgsmtp014.ril.com, mx05.reliancefoundation.org, relay02.ril.com, mx05.relbio.com, mx04.qwik.co.in, mx02.jiobp.com, mta5.gcptcl.in, gwsmtp012.ril.com, www.gwsmtp012.ril.com, gwsmtp015.ril.com, mx01.qwik.co.in, mail03.visionexpress.in, mx04.resq.in, mx06.resq.in, mx04.rfhospital.org

💡 Obtain a TLS certificate that matches the mail server hostname.

high

TLS certificate hostname mismatch on mx05.ajio.com

Certificate subject 'gwsmtp012.ril.com' does not match hostname 'mx05.ajio.com'. SANs: mx02.relbio.com, mx01.relbio.com, relay03.ril.com, mx06.rfhospital.org, relay01.ril.com, mail06.visionexpress.in, mx01.recron.com, gwsmtp011.ril.com, mx03.resq.in, mx05.rfhospital.org, mx02.resq.in, mx04.reliancefoundation.org, mx05.resq.in, mx01.rfhospital.org, mx03.relbio.com, mx06.relbio.com, mx01.jiobp.com, mx04.recron.com, mx01.reliancefoundation.org, relay04.ril.com, mta3.gcptcl.in, mx02.qwik.co.in, mx03.rfhospital.org, relay06.ril.com, mta4.gcptcl.in, mx04.jiobp.com, mx06.recron.com, mail01.visionexpress.in, mail04.visionexpress.in, mx03.reliancefoundation.org, mx03.jiobp.com, mx03.recron.com, mx05.recron.com, gwhydsmtp013.ril.com, mx06.qwik.co.in, mx03.qwik.co.in, gwjgsmtp014.ril.com, mx05.reliancefoundation.org, relay02.ril.com, mx05.relbio.com, mx04.qwik.co.in, mx02.jiobp.com, mta5.gcptcl.in, gwsmtp012.ril.com, www.gwsmtp012.ril.com, gwsmtp015.ril.com, mx01.qwik.co.in, mail03.visionexpress.in, mx04.resq.in, mx06.resq.in, mx04.rfhospital.org

💡 Obtain a TLS certificate that matches the mail server hostname.

high

TLS certificate hostname mismatch on mx06.ajio.com

Certificate subject 'gwsmtp012.ril.com' does not match hostname 'mx06.ajio.com'. SANs: mx02.relbio.com, mx01.relbio.com, relay03.ril.com, mx06.rfhospital.org, relay01.ril.com, mail06.visionexpress.in, mx01.recron.com, gwsmtp011.ril.com, mx03.resq.in, mx05.rfhospital.org, mx02.resq.in, mx04.reliancefoundation.org, mx05.resq.in, mx01.rfhospital.org, mx03.relbio.com, mx06.relbio.com, mx01.jiobp.com, mx04.recron.com, mx01.reliancefoundation.org, relay04.ril.com, mta3.gcptcl.in, mx02.qwik.co.in, mx03.rfhospital.org, relay06.ril.com, mta4.gcptcl.in, mx04.jiobp.com, mx06.recron.com, mail01.visionexpress.in, mail04.visionexpress.in, mx03.reliancefoundation.org, mx03.jiobp.com, mx03.recron.com, mx05.recron.com, gwhydsmtp013.ril.com, mx06.qwik.co.in, mx03.qwik.co.in, gwjgsmtp014.ril.com, mx05.reliancefoundation.org, relay02.ril.com, mx05.relbio.com, mx04.qwik.co.in, mx02.jiobp.com, mta5.gcptcl.in, gwsmtp012.ril.com, www.gwsmtp012.ril.com, gwsmtp015.ril.com, mx01.qwik.co.in, mail03.visionexpress.in, mx04.resq.in, mx06.resq.in, mx04.rfhospital.org

💡 Obtain a TLS certificate that matches the mail server hostname.

high

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.ajio.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@ajio.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 (36 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

DKIM key strength indicates modern key management

All DKIM keys use RSA-2048+ or Ed25519, consistent with current best practices.

pass

All external report destinations authorized

External DMARC report destinations have valid authorization records per RFC 7489 §7.1.

pass

Subdomains protected (sp=reject)

DMARC subdomain policy enforces quarantine or reject on unauthenticated subdomain mail.

pass

No deprecated DMARCbis tags present

The DMARC record does not use any tags deprecated in DMARCbis (pct, rf, ri).

pass

Meets bulk sender authentication requirements

Domain has SPF, DKIM, and DMARC — meeting Google/Yahoo 2024 bulk sender requirements for email authentication.

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

IPv6 readiness is good

IPv6 records are present and properly configured.

pass

NS delegation is properly configured

All nameservers are responsive, consistent, and properly secured.

pass

DNS responses are consistent across all nameservers

All authoritative nameservers return consistent answers with proper AA flags.

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

DMARC alignment: adkim=r, aspf=r

DKIM alignment is relaxed, SPF alignment is relaxed.

informational

DMARC failure reporting: fo=1

Failure reports generated when any authentication mechanism fails.

informational

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.

informational

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.

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 mx01.ajio.com

Detected open mail-related ports: 25

informational

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.

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: 2022113054, Refresh: 10800s, Retry: 900s, Expire: 1209600s, Min TTL: 86400s

informational

Attack Surface Findings

Dangling MX: au-mail.em.sdlproducts.com does not resolve

The MX record points to au-mail.em.sdlproducts.com which has no A record. This may indicate a decommissioned mail provider (Unknown). Attackers can potentially re-register this hostname to hijack inbound mail.

💡 Remove the stale MX record pointing to au-mail.em.sdlproducts.com or update it to your current mail provider.

critical

NSEC records enable zone walking

The domain uses NSEC records for DNSSEC authenticated denial of existence. NSEC records can be walked to enumerate all names in the zone, effectively disclosing the entire zone contents.

💡 Switch from NSEC to NSEC3 with opt-out to prevent zone enumeration. Use NSEC3 with a random salt and sufficient iterations.

high

Domain enumerability: high

The domain is highly enumerable. Zone transfers, NSEC zone walking, or a combination of factors make it easy to discover all DNS records.

💡 Restrict zone transfers, use NSEC3 instead of NSEC, consider wildcard certificates to reduce CT log exposure, and implement rate limiting on DNS queries.

high

Non-responsive IP for www.ajio.com: 2a02:26f0:9d00::1748:251a

The subdomain www.ajio.com resolves to 2a02:26f0:9d00::1748:251a which is not responding on ports 80 or 443. This may indicate a decommissioned server.

💡 Verify the server at 2a02:26f0:9d00::1748:251a is operational or remove the DNS record for www.ajio.com.

medium

Non-responsive IP for www.ajio.com: 2a02:26f0:9d00::1748:2560

The subdomain www.ajio.com resolves to 2a02:26f0:9d00::1748:2560 which is not responding on ports 80 or 443. This may indicate a decommissioned server.

💡 Verify the server at 2a02:26f0:9d00::1748:2560 is operational or remove the DNS record for www.ajio.com.

medium

Non-responsive IP for ftp.ajio.com: 116.50.83.240

The subdomain ftp.ajio.com resolves to 116.50.83.240 which is not responding on ports 80 or 443. This may indicate a decommissioned server.

💡 Verify the server at 116.50.83.240 is operational or remove the DNS record for ftp.ajio.com.

medium

Non-responsive IP for ns1.ajio.com: 49.45.43.42

The subdomain ns1.ajio.com resolves to 49.45.43.42 which is not responding on ports 80 or 443. This may indicate a decommissioned server.

💡 Verify the server at 49.45.43.42 is operational or remove the DNS record for ns1.ajio.com.

medium

Non-responsive IP for ns1.ajio.com: 2405:200:800:0:49:45:43:42

The subdomain ns1.ajio.com resolves to 2405:200:800:0:49:45:43:42 which is not responding on ports 80 or 443. This may indicate a decommissioned server.

💡 Verify the server at 2405:200:800:0:49:45:43:42 is operational or remove the DNS record for ns1.ajio.com.

medium

Non-responsive IP for ns2.ajio.com: 49.45.43.43

The subdomain ns2.ajio.com resolves to 49.45.43.43 which is not responding on ports 80 or 443. This may indicate a decommissioned server.

💡 Verify the server at 49.45.43.43 is operational or remove the DNS record for ns2.ajio.com.

medium

Non-responsive IP for ns2.ajio.com: 2405:200:800:0:49:45:43:43

The subdomain ns2.ajio.com resolves to 2405:200:800:0:49:45:43:43 which is not responding on ports 80 or 443. This may indicate a decommissioned server.

💡 Verify the server at 2405:200:800:0:49:45:43:43 is operational or remove the DNS record for ns2.ajio.com.

medium

Non-responsive IP for api.ajio.com: 49.40.59.11

The subdomain api.ajio.com resolves to 49.40.59.11 which is not responding on ports 80 or 443. This may indicate a decommissioned server.

💡 Verify the server at 49.40.59.11 is operational or remove the DNS record for api.ajio.com.

medium

Non-responsive IP for store.ajio.com: 49.40.59.16

The subdomain store.ajio.com resolves to 49.40.59.16 which is not responding on ports 80 or 443. This may indicate a decommissioned server.

💡 Verify the server at 49.40.59.16 is operational or remove the DNS record for store.ajio.com.

medium

NSEC used instead of NSEC3 (zone enumeration possible)

The domain uses NSEC records for authenticated denial of existence. NSEC allows zone walking.

💡 Migrate from NSEC to NSEC3 to prevent zone enumeration.

medium

Software/version information in TXT record

A TXT record contains a software identifier or version string: "103.20.18".

💡 Review TXT records and remove unnecessary software version information.

low

DNS ANY query returns 1 record(s)

The DNS server responds to ANY queries with 1 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

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

16 subdomain(s) discovered for ajio.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 ajio.com and its subdomains. Each certificate reveals subdomain names.

informational

DNSSEC is enabled

DNSKEY and/or DS records are present, indicating DNSSEC is configured.

informational

Reputation Findings

SMTP banner mismatch: mx05.rgtil.com

The SMTP banner identifies as 'mx05.rgtil.com' but the MX hostname is 'mx05.ajio.com' and PTR resolves to 'mx05.reputare.co.in'. Microsoft and other receivers flag this mismatch as suspicious infrastructure.

💡 Configure the SMTP server banner to match the MX hostname or PTR record (mx05.ajio.com).

high

Missing Strict-Transport-Security on ajio.com

The Strict-Transport-Security header is not set on https://ajio.com.

💡 Add the Strict-Transport-Security header with a max-age of at least 31536000 (1 year) and include the includeSubDomains directive.

medium

Not listed on any DNS blacklists

Domain and MX IPs checked against 55 DNSBLs — no listings found.

pass

security.txt present

Found security.txt at https://ajio.com/.well-known/security.txt.

pass

TLS certificate valid for 149 days

Certificate for ajio.com expires on 2026-10-24.

pass

Certificate issued by Go Daddy Secure Certificate Authority - G2

The certificate for ajio.com is issued by a third-party CA.

pass

Signature algorithm: rsa-sha256

The certificate for ajio.com uses an acceptable signature algorithm.

pass

RSA key: 2048 bits

The certificate for ajio.com uses an adequate RSA key of 2048 bits.

pass

SCTs present in certificate

The certificate for ajio.com contains Signed Certificate Timestamps.

pass

No weak ciphers detected

No known weak cipher suites detected on ajio.com.

pass

Domain valid for 3310 days

Domain ajio.com expires on 2035-06-20.

pass

Domain transfer and delete locks enabled

Domain ajio.com has clientTransferProhibited and clientDeleteProhibited locks.

pass

No disposable email provider MX records

MX records for ajio.com do not match known disposable email provider patterns.

pass

Domain is 6550 days old

Domain ajio.com was registered 2008-06-20.

pass

No wildcard MX records

No wildcard MX records detected for ajio.com.

pass

TLD has good reputation

The .com TLD is not on known abuse watchlists.

pass

DMARC reporting destinations look legitimate

DMARC rua/ruf addresses do not point to known URL shortener services.

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 (mx03.ajio.com) uses TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 including Forward Secrecy.

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.ajio.com

HTTPS request to https://webmail.ajio.com failed or timed out.

informational

WHOIS registration data

Registrar: GoDaddy.com, LLC | Created: 2008-06-20 | Expires: 2035-06-20 | Updated: 2026-05-12

informational

WHOIS privacy protection enabled

Domain ajio.com has WHOIS privacy/redaction enabled.

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: jio.com (has MX!), aio.com (has MX!), aji.com (has MX!), jaio.com (has MX!), wjio.com (has MX!)

26 registered lookalike domain(s) that could be used for phishing against your brand. Showing top 5 of 26. 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: reject

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: reject

⚠️ 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: mx01.ajio.com

PTR record proves mail server legitimacy

MX: mx01.ajio.com Mail server at 116.50.78.65 → PTR Record Reverse DNS: mx01.reliancetrends.com

Mail Server Identity: mx03.ajio.com

PTR record proves mail server legitimacy

MX: mx03.ajio.com Mail server at 116.50.80.159 → PTR Record Reverse DNS: mx02.reliancebrands.in

Mail Server Identity: mx04.ajio.com

PTR record proves mail server legitimacy

MX: mx04.ajio.com Mail server at 116.50.90.44 → PTR Record Reverse DNS: mx03.reputare.co.in

Mail Server Identity: mx05.ajio.com

PTR record proves mail server legitimacy

MX: mx05.ajio.com Mail server at 116.50.64.35 → PTR Record Reverse DNS: mx01.stevemadden.in

Mail Server Identity: mx06.ajio.com

PTR record proves mail server legitimacy

MX: mx06.ajio.com Mail server at 116.50.82.21 → PTR Record Reverse DNS: mx06.RGTIL.com

Mail Server Identity: au-mail.em.sdlproducts.com

PTR record proves mail server legitimacy

MX: au-mail.em.sdlproducts.com Mail server at au-mail.em.sdlproducts.com → PTR Record No PTR record

⚠️ Mail server au-mail.em.sdlproducts.com (au-mail.em.sdlproducts.com) lacks a PTR record. Many receiving servers require matching forward and reverse DNS for spam prevention.

Mail Server Reputation: mx01.ajio.com