Skip to content
https://sau.int

Infrastructure

· 17 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
85
GRADE
B
FIX
2
REVIEW
8
PASS
7
INFO
0
Probed from Madrid, Spain
200 OK
Checks
17
7 PASS 8 REVIEW 2 FIX
D
Multi-Resolver DNS Speed
Action
Mean 569ms across 3 resolvers (spread 1281ms)
FIX
Mean 569ms across 3 resolvers (spread 1281ms)
Info::
Quad9: 1ms
Got: 1ms via 9.9.9.9:53
Info::
Google: 424ms
Got: 424ms via 8.8.8.8:53
Info::
Cloudflare: 1282ms
Got: 1282ms via 1.1.1.1:53
Info::
High latency spread between resolvers: 1281ms (min 1ms / max 1282ms)
Wide gap between the fastest and slowest public resolver suggests a geographic anycast issue or an authoritative-server cache problem. Users in different regions will see materially different DNS times.
F
HTTP Probe Timing
Action
Total 3361 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
FIX
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
450 ms
TCP Connect TCP Connect — time to establish a TCP connection to the server.
227 ms
TLS Handshake TLS Handshake — time to complete the HTTPS encryption handshake.
257 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
1.95 s
Total Time Total request time from DNS lookup through full response.
3.36 s

Connection waterfall

DNS Lookup 450 ms TCP Connect 227 ms TLS Handshake 257 ms Server Processing 1.02 s Content Transfer 1.41 s
B
DNSSEC
Unsigned (DNSSEC not deployed)
REVIEW
Unsigned (DNSSEC not deployed)
Info::
DNSSEC is not deployed
The zone is not DNSSEC-signed. Users on validating resolvers (Cloudflare 1.1.1.1, Quad9 9.9.9.9, growing default in mobile resolvers) get no protection against DNS spoofing for this domain. Most registrars now offer DNSSEC at a single click; consider enabling it for sites where authenticity matters (banking, healthcare, government).
B
Reverse DNS
0/1 IPs match cert SAN
REVIEW
0/1 IPs match cert SAN
Info::
PTR for 103.243.237.41 does not match any cert SAN: w2.sau.int
Common when behind a CDN or shared hosting (PTR points at the provider's hostname). Mismatch can also affect mail deliverability if this IP sends email -- many MTAs reject mail when forward+reverse DNS disagree.
C
IPv6 Readiness
Action
No IPv6 support
REVIEW
No IPv6 support
Info::
No IPv6 (AAAA) records found
IPv6 support is increasingly important for global accessibility. About 40% of internet users have IPv6 connectivity.
No IPv6 Support
About 40% of internet users have IPv6. Consider adding AAAA records.

IPv6 support is increasingly important for global accessibility. About 40% of internet users have IPv6 connectivity.

Why this matters

No AAAA records — same impact as 'no IPv6 (AAAA) records'; IPv6-preferring clients pay extra latency falling back to IPv4.

Source: Google IPv6 stats

B
TLS Certificate Expiry & Recommendations
37 days until leaf cert expires — 3 issues to address
REVIEW

Certificate validity

37
days left
0d 30d 60d 90d+

Recommended actions

  • Submit your domain to hstspreload.org to be added to the Chrome preload list
  • Enable DNSSEC on your domain for DNS spoofing protection
  • Enable OCSP stapling on your TLS server to remove a CA roundtrip and protect user privacy
C
CDN & Delivery
Action
Assets on Cloudflare (host cdn.jsdelivr.net, 9 assets); document served directly from origin
REVIEW
Assets on Cloudflare (host cdn.jsdelivr.net, 9 assets); document served directly from origin
Warning::
Document not behind existing CDN (Cloudflare serves the assets)
The page's subresources are delivered by Cloudflare (cdn.jsdelivr.net, 9 assets), but the HTML document itself comes straight from the origin. Routing the document through the CDN already in use is the cheapest latency win available here -- the provider relationship, the certificate and the config already exist. A short edge TTL with stale-while-revalidate suits HTML that changes often; if the response is genuinely per-user, edge TLS termination alone still removes a full round trip from every visitor's first byte.
Got: delegation cdn.jsdelivr.net.cdn.cloudflare.net
Info::
Assets on Cloudflare: cdn.jsdelivr.net (assets: 9), cache HIT
Got: delegation cdn.jsdelivr.net.cdn.cloudflare.net
Warning: Assets on a CDN, document is not: Cloudflare
Document origin not attributed

Asset hosts on a CDN

  • cdn.jsdelivr.net — Cloudflare · assets: 9 · Cache Status: HIT

Other asset hosts

  • fonts.googleapis.com — assets: 4 · Google
  • admissions.sau.int — assets: 2 · below probe threshold
  • cdnjs.cloudflare.com — assets: 2 · below probe threshold
  • ajax.googleapis.com — assets: 1 · below probe threshold
  • www.google.com — assets: 1 · below probe threshold
  • www.googletagmanager.com — assets: 1 · below probe threshold
  • www.gstatic.com — assets: 1 · below probe threshold

The heavy static files already ride an edge network, but every visitor still waits on the origin for the HTML itself. Routing the document through the same CDN is usually a config change rather than a migration: a short edge TTL with stale-while-revalidate for cacheable HTML, or edge TLS termination alone when the response is per-user.

B
CDN Cache Observability
No CDN cache-status headers in the response
REVIEW
No CDN cache-status headers in the response
Info::
No CDN cache-status headers in the response
Without an X-Cache / CF-Cache-Status / X-Vercel-Cache / Age header, you can't tell from outside whether a request hit the cache or went to origin. Operationally important: enables debugging stale-content reports and verifying cache rules. Most managed CDN platforms emit at least one of these by default; absence often means the platform's diagnostic headers are stripped at an upstream proxy.
B
Operational Status Page
No status page link detected
REVIEW
No status page link detected
Info::
No operational status page link detected
Status pages communicate planned maintenance and incidents to users -- a hallmark of operationally-mature services. Most SaaS teams publish one via Atlassian Statuspage, Instatus, BetterUptime, or a self-hosted Cachet. Smaller sites legitimately don't need one; flagged as Info, not a failure.
B
Health Check Endpoint
No conventional health endpoint found
REVIEW
No conventional health endpoint found
Info::
No conventional health endpoint found
Health endpoints (/health, /healthz, /status, /ping, /api/health) let uptime monitors, load balancers, and orchestration systems (Kubernetes, ECS, Fly.io) verify the service is alive. Marketing sites and small services often skip them legitimately; flagged as Info, not a failure. Probe results: /api/health: 404, /health: connection error, /healthz: 404, /ping: 404, /status: 404.
A
DNS Records
1 A records, 466 ms lookup
PASS
1 A records, 466 ms lookup
Info::
Resolves to 1 IPv4 address(es)
Got: 103.243.237.41
Info::
Single A record — no DNS redundancy
Multiple A records provide failover if one server goes down.
Info::
No IPv6 (AAAA) records
Info::
2 nameserver(s) configured
Got: ns2.sau.ac.in, ns1.sau.ac.in
Info::
7 mail exchanger(s) configured
Info::
SPF record present in TXT
Warning::
DNS resolution is slow (466 ms)
Slow DNS adds latency to every page load. Consider a faster DNS provider.
Got: 466 ms
A103.243.237.41
AAAA—
CNAME—
NSns2.sau.ac.in, ns1.sau.ac.in
MX
10 ASPMX.L.GOOGLE.COM
20 ALT1.ASPMX.L.GOOGLE.COM
20 ALT2.ASPMX.L.GOOGLE.COM
30 ASPMX5.GOOGLEMAIL.COM
30 ASPMX3.GOOGLEMAIL.COM
30 ASPMX2.GOOGLEMAIL.COM
30 ASPMX4.GOOGLEMAIL.COM
TXT
SPF v=spf1 include:_spf.google.com include:amazonses.com -all
google-site-verification=AXmIVfyEGx1M6VpYo8798xpBWwzp7zasIKr1666xHrY
_sevx2hh396hw6hob2dvwglo6cl9ydaf
MS=ms97202584
CAALookup not available with standard resolver
Resolved in 466 ms

Multiple A records provide failover if one server goes down.

Why this matters

Single A record means a single point of failure — if that IP goes down, your site is unreachable until DNS TTL expires.

Learn more ▾

Add multiple A records for round-robin failover, or use a managed DNS provider with health-checked failover (Route 53, Cloudflare, NS1). Short TTL (60-300s) lets clients recover faster on outages.

Source: SRE practice / DNS architecture

Slow DNS adds latency to every page load. Consider a faster DNS provider.

Why this matters

DNS resolution is slow — anycast DNS providers (Cloudflare, Route 53) typically resolve <50ms globally.

Source: DNS performance benchmarks

A+
Subdomain Takeover
No subdomain takeover risk detected
PASS
No subdomain takeover risk detected
Info::
No CNAME record present
A+
CAA Records
issue: sectigo.com, letsencrypt.org, digicert.com | iodef configured
PASS
issue: sectigo.com, letsencrypt.org, digicert.com | iodef configured
Info::
CAA issue tag present — authorized CA(s): sectigo.com, letsencrypt.org, digicert.com
Info::
CAA iodef tag present (failed-issuance notifications enabled)
A+
Redirect Chain
No redirects — direct access
PASS
No redirects — direct access
Info::
No redirects — direct access
Got: https://sau.int

https://sau.int

1469 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://sau.int2001469 msHTTP/1.1Apache
A+
Crawlability
robots.txt present, sitemap with 21 URLs
PASS
robots.txt present, sitemap with 21 URLs
Info::
robots.txt is present
Got: 704 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 21 entries
Info::
Sitemap index with 21 child sitemaps
Info::
robots.txt does not reference a sitemap
Add a 'Sitemap:' directive to robots.txt so search engines can discover your sitemap.

Add a 'Sitemap:' directive to robots.txt so search engines can discover your sitemap.

Why this matters

robots.txt omits Sitemap: directive — crawlers must fetch /sitemap.xml by convention; reliable but missing the explicit hint.

Source: sitemaps.org

robots.txt 200 OK
Size 704 B Sitemaps referenced 0 User-agents * Blocking No — crawling allowed
User-agent: *
Disallow: /wp-login
Disallow: /wp-admin
Disallow: /wp-includes/
Disallow: /wp-login.php
Disallow: /wp-content/
Disallow: /*/feed/
Disallow: /*/trackback/
Disallow: /trackback
Disallow: */trackback
Disallow: */*/trackback
Disallow: /*/attachment/
Disallow: /author/
Disallow: /*/page/
Disallow: /*/feed/
Disallow: /tag/*/page/
Disallow: /tag/*/feed/
Disallow: /page/
Disallow: /comments/
Disallow: /xmlrpc.php
Disallow: /*?s=
Disallow: /*/*/*/feed.xml
Disallow: /?attachment_id*
Disallow: /cgi-bin
Disallow: /xmlrpc.php
Disallow: */*/feed/*/
Disallow: */feed
Disallow: /*?*
Disallow: /search/
Disallow: /tag
Disallow: /?author=*

Allow: /wp-admin/admin-ajax.php
Allow: /wp-content/uploads/
sitemap.xml 200 OK
Type Sitemap Index URLs 21 entries Valid XML Yes
Child Sitemaps:
A+
URL Variants
www/non-www, trailing slash, HTTP→HTTPS
PASS
www/non-www, trailing slash, HTTP→HTTPS
Info::
www/non-www redirect configured correctly (preferred: non-www)
Info::
HTTP correctly redirects to HTTPS permanently
Got: HTTP 301

www / non-www

301https://www.sau.int/
200https://sau.int/

Preferred variant: non-www

HTTP → HTTPS

301http://sau.int/ → https://sau.int:443/

Consistent

A+
Domain Intelligence
sau.int — 11 years, 7 months old, hosted on SAU-AS - South Asian University, IN
PASS
sau.int — 11 years, 7 months old, hosted on SAU-AS - South Asian University, IN
Info::
DNSSEC is not enabled
DNSSEC protects against DNS spoofing attacks. While not required, enabling DNSSEC adds an additional layer of security. Contact your DNS provider to enable it.
Warning::
Registrar lock is NOT enabled
The domain can be transferred without an unlock step. Enable registrar lock (clientTransferProhibited) in your registrar's control panel to protect against unauthorized or accidental transfers.
Info::
Hosting: SAU-AS - South Asian University, IN
Got: AS132995
Domain expiry

Unknown

SSL certificate

37 days

Issued by Let's Encrypt

Domain age

11 years, 7 months

Registered May 8, 2015

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

SAU-AS - South Asian University, IN

ASN AS132995

103.243.237.41

Registrar

Registrar unknown

Unlocked 2 NS records
Expiry timeline
Today
+1 year
SSL expiry Danger zone (≤30 days)
Recommended actions
  • Enable DNSSEC to protect visitors from DNS spoofing
  • Enable registrar lock (clientTransferProhibited) to block unauthorized domain transfers
Registrar
Created May 8, 2015 (11 years, 7 months ago)
Last Updated May 8, 2015
Name Servers ns1.sau.ac.in, ns2.sau.ac.in
DNSSEC Not enabled
Registrant South Asian University
Hosting
IP Address 103.243.237.41
ASN AS132995 (SAU-AS - South Asian University, IN)
Provider SAU-AS - South Asian University, IN
Data source: rdap (1.0s)

DNSSEC protects against DNS spoofing attacks. While not required, enabling DNSSEC adds an additional layer of security. Contact your DNS provider to enable it.

Why this matters

Without DNSSEC, an attacker who can poison your DNS can hijack your domain — and SSL certs alone don't stop them.

Learn more ▾

DNSSEC adds cryptographic signatures to DNS records, preventing forged responses from poisoning resolver caches. Without it, an attacker who controls the network path can redirect your domain to a malicious server before any HTTPS handshake happens. Most modern registrars (Cloudflare, Google Domains, Route 53) enable it with one toggle.

Source: ICANN / RFC 4033

The domain can be transferred without an unlock step. Enable registrar lock (clientTransferProhibited) in your registrar's control panel to protect against unauthorized or accidental transfers.

Why this matters

Without registrar lock, an attacker who phishes your registrar credentials can transfer the domain in minutes — total brand hijack.

Learn more ▾

Registrar lock (clientTransferProhibited, clientUpdateProhibited, clientDeleteProhibited) requires extra verification before any transfer/update/delete. Every major registrar offers it free. Combined with 2FA on your registrar account, it's the strongest defense against domain hijacking.

Source: ICANN / domain-security best practice

All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback