Skip to content
https://rbi.org.in

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
89
GRADE
B
FIX
1
REVIEW
3
PASS
5
INFO
0
Probed from Madrid, Spain
200 OK
Checks
9
5 PASS 3 REVIEW 1 FIX
D
URL Variants
Action
www/non-www, trailing slash, HTTP→HTTPS
FIX
www/non-www, trailing slash, HTTP→HTTPS
Critical::
Both www and non-www versions serve content
Got: Both variants return 200 Expected: One variant 301-redirects to the other
Critical::
HTTP version does not redirect to HTTPS
Got: HTTP 404 Expected: 301 redirect to HTTPS

www / non-www

200https://www.rbi.org.in/
200https://rbi.org.in/

Inconsistent — duplicate content risk

HTTP → HTTPS

404http://rbi.org.in/

HTTP version does not redirect to HTTPS

C
HTTP Probe Timing
Action
Total 1504 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
REVIEW
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
73 ms
TCP Connect TCP Connect — time to establish a TCP connection to the server.
17 ms
TLS Handshake TLS Handshake — time to complete the HTTPS encryption handshake.
37 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
1.49 s
Total Time Total request time from DNS lookup through full response.
1.50 s

Connection waterfall

DNS Lookup 73 ms TCP Connect 17 ms TLS Handshake 37 ms Server Processing 1.36 s Content Transfer 14 ms
B
TLS Certificate Expiry & Recommendations
74 days until leaf cert expires — 4 issues to address
REVIEW

Certificate validity

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

Recommended actions

  • Extend HSTS max-age to at least 31536000 (1 year) to meet the preload list criteria
  • Add the preload directive and submit to hstspreload.org once max-age + includeSubDomains are in place
  • 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
B
CDN & Delivery
Azure CDN (PRIVATE_NOSTORE)
REVIEW
Azure CDN (PRIVATE_NOSTORE)
Info::
Site is served via Azure CDN CDN
Got: x-azure-ref: 20260422T232509Z-1675fbfb9b4bbp2lhC1PAR2v8g0000000p7g00000000cvwu
Info::
CDN cache status: PRIVATE_NOSTORE
CDN Detected: Azure CDN
Provider Azure CDN Cache Status PRIVATE_NOSTORE Evidence x-azure-ref: 20260422T232509Z-1675fbfb9b4bbp2lhC1PAR2v8g0000000p7g00000000cvwu
A+
DNS Records
1 A records, 45 ms lookup
PASS
1 A records, 45 ms lookup
Info::
Resolves to 1 IPv4 address(es)
Got: 150.171.110.117
Info::
Single A record — no DNS redundancy
Multiple A records provide failover if one server goes down.
Info::
Has 1 IPv6 (AAAA) record(s)
Got: 2603:1061:14:174::1
Info::
6 nameserver(s) configured
Got: ns61.constellix.net, ns11.constellix.com, ns31.constellix.com, ns41.constellix.net, ns51.constellix.net, ns21.constellix.com
Info::
2 mail exchanger(s) configured
Info::
CAA records not checked
CAA record lookup requires a specialized DNS resolver. This check will be available in a future update.
Info::
SPF record present in TXT
Info::
DNS resolution time: 45 ms
Got: 45 ms
A150.171.110.117
AAAA2603:1061:14:174::1
CNAME—
NSns61.constellix.net, ns11.constellix.com, ns31.constellix.com, ns41.constellix.net, ns51.constellix.net, ns21.constellix.com
MX
5 mms1.rbi.org.in
10 mms3.rbi.org.in
TXT
cisco-ci-domain-verification=4e4b30d9f1a6c8024cdbd21e6fa155d7aed29fa6fa86e4f2715...
g63xh62nxmmzf7tzc3207lkscvrs95wc
SPF v=spf1 ip4:1.6.199.39 ip4:1.6.199.26 ip4:59.160.124.39 ip4:59.160.124.26 ip4:1.6...
pkrxt805n0stq43vns6s07pfbxwqpgtv
MS=5B6D41D605A1A889691F801DC963C235AB6AFFE3
MS=ms29308063
CAALookup not available with standard resolver
Resolved in 45 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

CAA record lookup requires a specialized DNS resolver. This check will be available in a future update.

Why this matters

Informational: CAA (Certification Authority Authorization) records weren't checked in this scan.

A+
Redirect Chain
No redirects — direct access
PASS
No redirects — direct access
Info::
No redirects — direct access
Got: https://rbi.org.in

https://rbi.org.in

947 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://rbi.org.in200947 msHTTP/1.1
A+
IPv6 Readiness
IPv6 reachable (16 ms)
PASS
IPv6 reachable (16 ms)
Info::
IPv6 is configured and reachable at 2603:1061:14:174::1
Got: 16 ms connect
IPv6 Ready
AAAA Records 2603:1061:14:174::1 Connection Reachable (16 ms)
A
Crawlability
no robots.txt, sitemap with 497 URLs
PASS
no robots.txt, sitemap with 497 URLs
Info::
No robots.txt found
robots.txt is optional but recommended. It tells search engine crawlers which pages to index.
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 497 entries

robots.txt is optional but recommended. It tells search engine crawlers which pages to index.

Why this matters

No robots.txt — crawlers fetch /robots.txt and get 404; not breaking but means default crawl behavior with no directives or sitemap reference.

Learn more ▾

A minimal robots.txt with `User-agent: * / Allow: / / Sitemap: https://example.com/sitemap.xml` covers the basics. Without it, crawlers behave fine but lose the sitemap signal and can't be selectively blocked from crawl-traps.

Source: robotstxt.org

robots.txt No robots.txt found

No robots.txt found

This is fine for most sites — a missing robots.txt allows all crawling by default.

sitemap.xml 200 OK
Type URL Set URLs 497 entries Valid XML Yes
Sample URLs:
A+
Domain Intelligence
rbi.org.in — via Sify Digital Services Limited, 23 years, 5 months old
PASS
rbi.org.in — via Sify Digital Services Limited, 23 years, 5 months old
Info::
Domain registered until Feb 28, 2027 (10 months remaining)
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.
Info::
Registrar: Sify Digital Services Limited
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.
Domain expiry

257 days

February 28, 2027

SSL certificate

74 days

Issued by DigiCert Inc

Domain age

23 years, 5 months

Registered February 28, 2003

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

Unknown

2603:1061:14:174::1

Registrar

Sify Digital Services Limited

Unlocked 6 NS records
Expiry timeline
Today
+1 year
Domain expiry 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 Sify Digital Services Limited
Created February 28, 2003 (23 years, 5 months ago)
Expires February 28, 2027 (10 months)
Last Updated January 14, 2026
Name Servers ns51.constellix.net, ns21.constellix.com, ns31.constellix.com, ns41.constellix.net, ns11.constellix.com, ns61.constellix.net
DNSSEC Not enabled
Hosting
IP Address 2603:1061:14:174::1
Data source: rdap (0.7s)

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