Back to results

Digital exposure report

iitm.ac.in

High exposure. Significant weaknesses put the brand, customers and email at risk.

Scanned: 2026-11-18 01:55 UTC

Partial coverage: the score is based on 88% of applicable check weight. 1 unverified check(s) are excluded, not counted as failures.

D
60/100

What to do first

  1. 1.

    Turn on DNS signing for your domain

    Signing helps resolvers detect forged answers about your domain.

    Who can fix it: Your domain registrar or DNS provider

    How to verify after the fix

    dig +short DS iitm.ac.in
  2. 2.

    Choose which companies may issue certificates for your domain

    This reduces the chance of a certificate being issued by a provider you did not choose.

    Who can fix it: Your domain registrar or DNS provider

    How to verify after the fix

    dig +short CAA iitm.ac.in

A starting point, not a security guarantee.

What this grade means

Tested hostname
iitm.ac.in
Website request
GET https://iitm.ac.in/(no HTTPS response)
Scan time
2026-11-18 01:55:58 UTC
Grading method
Version 2How grading works
Unverified or excluded checks
  • DKIM — digital signature on email · Not detected (common selectors only)
  • HTTPS available · Not applicable
  • HTTP → HTTPS redirect · Not applicable
  • SSL/TLS certificate validity · Not applicable
  • HSTS — enforce encryption in the browser · Not applicable
  • CSP — protection from script injection · Not applicable
  • Clickjacking protection · Not applicable
  • X-Content-Type-Options · Not applicable
  • Referrer-Policy · Not applicable
  • Permissions-Policy · Not applicable

This is a snapshot of the public configuration checks listed in this report. It does not verify the site's owner, business legitimacy, application security, or absence of vulnerabilities. It is not a security certification.

Score by category

Email security21/25Spoofing email from this domain is hard.
Encryption & certificate—Not applicable to this domain.
Browser protections—Not applicable to this domain.
DNS infrastructure3/15The domain's infrastructure lacks basic protections.

Fix priorities

  1. 1.MediumDNSSEC — signed DNS records · Hardening gap+18
  2. 2.LowCAA — who may issue certificates · Hardening gap+13
  3. 3.LowDMARC — anti-spoofing policy · Hardening gap+8

To verify

Couldn't be confirmed from public data, so excluded from the score. Checking them clarifies your posture; it doesn't guarantee a score change.

  • DKIM — digital signature on email

Findings

SPF — who may send mail for the domain

Passed · Severity: OK · 9/10

An authorized sender list is defined; mail from other servers is flagged as suspicious.

~all (softfail) — acceptable when combined with enforced DMARC. 0 of 10 DNS lookups.

Source data: DNS TXT iitm.ac.in
v=spf1 ip4:103.158.42.46/32 ip4:103.158.42.47/32 ip4:103.158.42.48/32 ip4:103.158.42.50/32 ip4:103.158.42.51/32 ~all
$ dig +short TXT iitm.ac.in
Documentation: RFC 7208 — SPF (https://www.rfc-editor.org/rfc/rfc7208) · M3AAWG — Email Authentication Best Practices (https://www.m3aawg.org/sites/default/files/m3aawg-email-authentication-recommended-best-practices-09-2020.pdf)

DMARC — anti-spoofing policy

Needs attention · Severity: Low · Hardening gap · 12/15

Forged email in the company's name is sent to the spam folder.

Policy p=quarantine. p=quarantine — consider moving to p=reject. sp=none — subdomains are exposed to spoofing.

Source data: DNS TXT _dmarc.iitm.ac.in
v=DMARC1;p=quarantine;sp=none;pct=100;fo=1;rua=mailto:admin@iitm.ac.in;ruf=mailto:admin@iitm.ac.in
$ dig +short TXT _dmarc.iitm.ac.in
Fix recommendation (effort: Easy)
  1. Keep your current p=quarantine enforcement and edit the existing record in place — do not replace it with p=none.
  2. Set sp to match p so subdomains get the same enforcement.
  3. Optional: once reports show all legitimate senders pass, move from p=quarantine to p=reject.
_dmarc.iitm.ac.in.  TXT  "v=DMARC1; p=quarantine; sp=quarantine; pct=100; fo=1; rua=mailto:admin@iitm.ac.in; ruf=mailto:admin@iitm.ac.in"

Safety: DNS changes are made only at your DNS provider. This tool only reads public data and changes nothing on the domain. Your domain already enforces DMARC. Edit the record in place; never roll back to p=none.

Documentation: RFC 7489 — DMARC (https://www.rfc-editor.org/rfc/rfc7489) · dmarc.org — FAQ (https://dmarc.org/resources/frequently-asked-questions/)

DKIM — digital signature on email

Not detected (common selectors only) · Severity: OK · Not scored

No DKIM key was found under the common selectors we probed. That doesn't mean DKIM is missing — selectors can't be listed from public DNS. Not scored.

A missing name for a probed selector (NXDOMAIN/NODATA) only means that selector isn't published. DKIM is marked unverified and excluded from the score. Check a sent message's Authentication-Results for dkim=pass and its s= selector.

Source data: DNS TXT <selector>._domainkey.iitm.ac.in
Selectors checked: google, selector1, selector2, default, k1, s1, s2, dkim, mail, smtp — no key found
google._domainkey: nxdomain
selector1._domainkey: nxdomain
selector2._domainkey: nxdomain
default._domainkey: nxdomain
k1._domainkey: nxdomain
s1._domainkey: nxdomain
s2._domainkey: nxdomain
dkim._domainkey: nxdomain
mail._domainkey: nxdomain
smtp._domainkey: nxdomain
$ dig +short TXT google._domainkey.iitm.ac.in
Documentation: RFC 6376 — DKIM (https://www.rfc-editor.org/rfc/rfc6376) · M3AAWG — Email Authentication Best Practices (https://www.m3aawg.org/sites/default/files/m3aawg-email-authentication-recommended-best-practices-09-2020.pdf)

MX — inbound mail routing

Passed · Severity: OK · unscored

Mail exchangers are published for the domain.

5 MX record(s). This shows where inbound mail is routed, not whether mail is sent from the domain.

Source data: DNS MX iitm.ac.in
50 mailx5.iitm.ac.in
40 mailx4.iitm.ac.in
30 mailx3.iitm.ac.in
20 mailx2.iitm.ac.in
10 mailx1.iitm.ac.in
$ dig +short MX iitm.ac.in
Documentation: RFC 7505 — Null MX (https://www.rfc-editor.org/rfc/rfc7505) · RFC 5321 §5.1 — Locating the target host (https://www.rfc-editor.org/rfc/rfc5321#section-5.1)

HTTPS available

Not applicable · Severity: OK · Not applicable

The domain has no web address (no A/AAAA records), so website checks don't apply.

The domain has no web address (no A/AAAA records), so website checks don't apply.

Source data: HTTPS GET https://iitm.ac.in/
No A/AAAA record for the domain
$ curl -svI https://iitm.ac.in/ 2>&1 | grep -E "SSL|HTTP|expire"
Documentation: OWASP — Transport Layer Security Cheat Sheet (https://cheatsheetseries.owasp.org/cheatsheets/Transport_Layer_Security_Cheat_Sheet.html) · Mozilla — Server Side TLS (https://wiki.mozilla.org/Security/Server_Side_TLS)

HTTP → HTTPS redirect

Not applicable · Severity: OK · Not applicable

The domain has no web address (no A/AAAA records), so website checks don't apply.

The domain has no web address (no A/AAAA records), so website checks don't apply.

Source data: HTTP GET http://iitm.ac.in/ (redirects not followed)
Not checked
$ curl -sI http://iitm.ac.in/ | grep -iE "^(HTTP|location)"
Documentation: OWASP — Transport Layer Security Cheat Sheet (https://cheatsheetseries.owasp.org/cheatsheets/Transport_Layer_Security_Cheat_Sheet.html) · RFC 6797 — HSTS (https://www.rfc-editor.org/rfc/rfc6797)

SSL/TLS certificate validity

Not applicable · Severity: OK · Not applicable

The domain has no web address (no A/AAAA records), so website checks don't apply.

The domain has no web address (no A/AAAA records), so website checks don't apply.

Source data: Certificate Transparency logs (certspotter) for iitm.ac.in
CT logs (context only, not scored):
Issuer: Sectigo
Valid from: 2026-10-30
Valid until: 2027-05-16
Names: *.iitm.ac.in, iitm.ac.in
Based on Certificate Transparency logs; may not reflect the certificate currently served.
$ echo | openssl s_client -connect iitm.ac.in:443 -servername iitm.ac.in 2>/dev/null | openssl x509 -noout -issuer -dates
Documentation: Certificate Transparency (https://certificate.transparency.dev/) · Let's Encrypt — Docs (https://letsencrypt.org/docs/) · Mozilla — Server Side TLS (https://wiki.mozilla.org/Security/Server_Side_TLS)

HSTS — enforce encryption in the browser

Not applicable · Severity: OK · Not applicable

Not applicable — the domain has no web address.

Not applicable — the domain has no web address.

Source data: Response headers from https://iitm.ac.in/
No HTTPS response received
$ curl -sIL https://iitm.ac.in/
Documentation: MDN — Strict-Transport-Security (https://developer.mozilla.org/en-US/docs/Web/HTTP/Reference/Headers/Strict-Transport-Security) · RFC 6797 — HSTS (https://www.rfc-editor.org/rfc/rfc6797) · OWASP — HTTP Headers Cheat Sheet (https://cheatsheetseries.owasp.org/cheatsheets/HTTP_Headers_Cheat_Sheet.html)

CSP — protection from script injection

Not applicable · Severity: OK · Not applicable

Not applicable — the domain has no web address.

Not applicable — the domain has no web address.

Source data: Response headers from https://iitm.ac.in/
No HTTPS response received
$ curl -sIL https://iitm.ac.in/
Documentation: MDN — Content Security Policy (https://developer.mozilla.org/en-US/docs/Web/HTTP/Guides/CSP) · OWASP — CSP Cheat Sheet (https://cheatsheetseries.owasp.org/cheatsheets/Content_Security_Policy_Cheat_Sheet.html)

Clickjacking protection

Not applicable · Severity: OK · Not applicable

Not applicable — the domain has no web address.

Not applicable — the domain has no web address.

Source data: Response headers from https://iitm.ac.in/
No HTTPS response received
$ curl -sIL https://iitm.ac.in/
Documentation: MDN — X-Frame-Options (https://developer.mozilla.org/en-US/docs/Web/HTTP/Reference/Headers/X-Frame-Options) · OWASP — Clickjacking Defense (https://cheatsheetseries.owasp.org/cheatsheets/Clickjacking_Defense_Cheat_Sheet.html)

X-Content-Type-Options

Not applicable · Severity: OK · Not applicable

Not applicable — the domain has no web address.

Not applicable — the domain has no web address.

Source data: Response headers from https://iitm.ac.in/
No HTTPS response received
$ curl -sIL https://iitm.ac.in/
Documentation: MDN — X-Content-Type-Options (https://developer.mozilla.org/en-US/docs/Web/HTTP/Reference/Headers/X-Content-Type-Options) · OWASP — HTTP Headers Cheat Sheet (https://cheatsheetseries.owasp.org/cheatsheets/HTTP_Headers_Cheat_Sheet.html)

Referrer-Policy

Not applicable · Severity: OK · Not applicable

Not applicable — the domain has no web address.

Not applicable — the domain has no web address.

Source data: Response headers from https://iitm.ac.in/
No HTTPS response received
$ curl -sIL https://iitm.ac.in/
Documentation: MDN — Referrer-Policy (https://developer.mozilla.org/en-US/docs/Web/HTTP/Reference/Headers/Referrer-Policy) · OWASP — HTTP Headers Cheat Sheet (https://cheatsheetseries.owasp.org/cheatsheets/HTTP_Headers_Cheat_Sheet.html)

Permissions-Policy

Not applicable · Severity: OK · Not applicable

Not applicable — the domain has no web address.

Not applicable — the domain has no web address.

Source data: Response headers from https://iitm.ac.in/
No HTTPS response received
$ curl -sIL https://iitm.ac.in/
Documentation: MDN — Permissions-Policy (https://developer.mozilla.org/en-US/docs/Web/HTTP/Reference/Headers/Permissions-Policy) · OWASP — HTTP Headers Cheat Sheet (https://cheatsheetseries.owasp.org/cheatsheets/HTTP_Headers_Cheat_Sheet.html)

DNSSEC — signed DNS records

Needs attention · Severity: Medium · Hardening gap · 0/7

The domain's records aren't signed, so in some scenarios users could be redirected to a forged server.

No DS record is published at the parent zone, so there's no DNSSEC chain of trust for this zone.

Source data: DNS-over-HTTPS (Cloudflare / Google): AD flag and DS record at the parent
AD = false
DS iitm.ac.in: NODATA
$ dig +short DS iitm.ac.in
Fix recommendation (effort: Medium)
  1. Enable DNSSEC at your DNS provider (one click at most providers).
  2. Copy the DS record your provider generates to your domain registrar.
  3. Wait for propagation and verify with DNSViz.
dig +dnssec iitm.ac.in SOA
delv iitm.ac.in

Safety: DNS changes are made only at your DNS provider. This tool only reads public data and changes nothing on the domain. A wrong DS record at the registrar will make the domain stop resolving — copy it exactly from the provider.

Documentation: RFC 4033 — DNSSEC (https://www.rfc-editor.org/rfc/rfc4033) · ICANN — DNSSEC: what and why (https://www.icann.org/resources/pages/dnssec-what-is-it-why-important-2019-03-05-en)

CAA — who may issue certificates

Needs attention · Severity: Low · Hardening gap · 0/5

Any certificate authority can issue a certificate for the domain, raising the risk of mis-issuance.

No CAA records found. RFC 8659 lets the domain owner restrict which CAs are authorized.

Source data: DNS CAA iitm.ac.in
(no CAA records found)
$ dig +short CAA iitm.ac.in
Fix recommendation (effort: Easy)
  1. Identify which certificate authority issued your current certificate (see the certificate check).
  2. Publish CAA for that authority only, and add iodef to receive alerts.
iitm.ac.in.  CAA  0 issue "letsencrypt.org"
iitm.ac.in.  CAA  0 iodef "mailto:security@iitm.ac.in"

Safety: DNS changes are made only at your DNS provider. This tool only reads public data and changes nothing on the domain. If your CDN issues certificates on your behalf, include it too — otherwise certificate renewal will fail.

Documentation: RFC 8659 — CAA (https://www.rfc-editor.org/rfc/rfc8659)

DNS server redundancy

Passed · Severity: OK · 3/3

The domain is served by several DNS servers, so one server failing won't take it down.

3 NS servers.

Source data: DNS NS iitm.ac.in
dns3.iitm.ac.in
dns2.iitm.ac.in
dns1.iitm.ac.in
$ dig +short NS iitm.ac.in
Documentation: RFC 2182 — Secondary DNS server operation (https://www.rfc-editor.org/rfc/rfc2182)

Indicative alignment

Best-practice mapping of public findings to common frameworks. Passive scanning tests public configuration only; it doesn't prove compliance or a violation.

  • Google & Yahoo sender rules1 observed gaps · 1 unverified
  • PCI DSS v4.0Not applicable
  • NIS2 / vendor due diligence3 observed gaps
  • SOC 2 / ISO 27001 baseline1 observed gaps

Indicative alignment only, based on public configuration. It doesn't establish whether a framework applies to you, and it isn't legal advice, an audit or a certification.

Public DNS records

Aiitm.ac.in—
AAAAiitm.ac.in—
MXiitm.ac.in50 mailx5.iitm.ac.in | 40 mailx4.iitm.ac.in | 30 mailx3.iitm.ac.in | 20 mailx2.iitm.ac.in | 10 mailx1.iitm.ac.in
NSiitm.ac.indns3.iitm.ac.in | dns2.iitm.ac.in | dns1.iitm.ac.in
TXTiitm.ac.ingoogle-site-verification=B-qjwR1GbECjfbnbBukYz88EYCCoPIHH2yB4nI8T67k | v=spf1 ip4:103.158.42.46/32 ip4:103.158.42.47/32 ip4:103.158.42.48/32 ip4:103.158.42.50/32 ip4:103.158.42.51/32 ~all
TXT_dmarc.iitm.ac.inv=DMARC1;p=quarantine;sp=none;pct=100;fo=1;rua=mailto:admin@iitm.ac.in;ruf=mailto:admin@iitm.ac.in
CAAiitm.ac.in—
DSiitm.ac.in—
Passive check only: reading public DNS records, Certificate Transparency logs and ordinary GET requests to the homepage over HTTPS and HTTP. No changes were made to the scanned domain. Results are an indication and do not replace a professional security assessment.

Check your own domain