Skip to content
https://mbmis.in

Infrastructure

· 17 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
84
GRADE
B
FIX
0
REVIEW
9
PASS
8
INFO
0
Probed from Madrid, Spain
302 Found
Checks
17
8 PASS 9 REVIEW
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
CAA Records
No CAA records (any CA may issue certificates)
REVIEW
No CAA records (any CA may issue certificates)
Info::
No CAA records published
Without CAA records, any publicly-trusted CA can issue certificates for this domain. Adding a CAA record (`yourdomain. IN CAA 0 issue "letsencrypt.org"`) restricts issuance to CAs you authorize. Required by CAB Forum baseline since 2017; the default of 'any CA' is widely supported but is the broader attack surface for issuance fraud.
C
Reverse DNS
Action
0/1 IPs match cert SAN
REVIEW
0/1 IPs match cert SAN
Info::
PTR lookup failed for 117.239.128.227: lookup 117.239.128.227: DNS response contained records which contain invalid names
No reverse DNS record set for this IP. Common on bare cloud-VM IPs without provider-side PTR; not a security issue.
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

C
Crawlability
Action
robots.txt present, sitemap with 0 URLs
REVIEW
robots.txt present, sitemap with 0 URLs
Info::
robots.txt is present
Got: 4626 bytes
Info::
sitemap.xml is present
Warning::
sitemap.xml contains invalid XML
Search engines may not be able to parse the sitemap. Fix XML validation errors.
Warning::
sitemap.xml is empty — no URLs found
An empty sitemap provides no value. Add <url> entries for your pages.
Info::
robots.txt does not reference a sitemap
Add a 'Sitemap:' directive to robots.txt so search engines can discover your sitemap.

Search engines may not be able to parse the sitemap. Fix XML validation errors.

Why this matters

An unparseable sitemap is silently ignored by Google — the URLs it advertises are never queued for crawl.

Learn more ▾

Google's sitemap parser is strict about XML validity. A single unescaped `&` or unclosed tag invalidates the whole file. Run your sitemap through a validator (Search Console's Sitemaps report flags it) and fix the offending entry. Most generators escape correctly; mistakes usually come from manually-written entries.

Source: sitemaps.org / Google Search Central

An empty sitemap provides no value. Add <url> entries for your pages.

Why this matters

An empty sitemap signals 'no content to index' to Google — actively harmful versus having no sitemap at all.

Learn more ▾

Google compares URLs in the sitemap against URLs it has crawled. An empty sitemap on a site with thousands of pages signals abandonment. Either populate it correctly (most CMSes auto-generate) or delete the file and let Google crawl normally.

Source: Google Search Central / sitemaps.org

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 4626 B Sitemaps referenced 0 User-agents Blocking No — crawling allowed
<!DOCTYPE html>
<html lang="en">
<head>
    
    <meta charset="UTF-8">
    <meta name="viewport" content="width=device-width, initial-scale=1.0">
    <meta name="description" content="Mission Bhagiratha MIS Portal - Rural Drinking Water Supply Monitoring">
    <title>Login | Mission Bhagiratha MIS Portal</title>
    <link rel="preconnect" href="https://cdn.jsdelivr.net" crossorigin>
    <link href="https://cdn.jsdelivr.net/npm/bootstrap@5.3.3/dist/css/bootstrap.min.css" rel="stylesheet">
    <link href="https://cdn.jsdelivr.net/npm/bootstrap-icons@1.11.3/font/bootstrap-icons.min.css" rel="stylesheet">
    <link href="/static/css/main.f6ddba205904.css" rel="stylesheet">
    
<style>
.login-photo-row {
    display: flex;
    justify-content: center;
    gap: 1.5rem;
    margin-bottom: 1.5rem;
    flex-wrap: wrap;
}
.login-photo-slot {
    text-align: center;
}
.login-photo-circle {
    width: 92px;
    height: 92px;
    border-radius: 50%;
    border: 3px solid #fff;
    background: transparent;
    overflow: hidden;
    display: flex;
    align-items: center;
    justify-content: center;
    box-shadow: 0 0 0 1px rgba(255,255,255,0.25);
}
.login-photo-circle img {
    width: 100%;
    height: 100%;
    object-fit: cover;
}
.login-photo-slot span {
    display: block;
    margin-top: 0.4rem;
    color: rgba(255,255,255,0.9);
    font-size: 0.75rem;
}
</style>

</head>
<body class="auth-page">
    
<div class="auth-wrapper">
    <div class="login-photo-row">
        
        <div class="login-photo-slot">
            <div class="login-photo-circle">
                
            </div>
            <span>Chief Minister</span>
        </div>
        
        <div class="login-photo-slot">
            <div class="login-photo-circle">
                
                <img src="/media/login/logo.png" alt="Logo">
                
            </div>
            <span>Logo</span>
        </div>
        
        <div class="login-photo-slot">
            <div class="login-photo-circle">
                
            </div>
            <span>Department Minister</span>
        </div>
        
    </div>
    <div class="auth-card">
        <div class="auth-header text-center mb-4">
            <div class="auth-logo mb-3">
                <i class="bi bi-droplet-fill"></i>
            </div>
            <h1 class="h4 fw-bold text-primary mb-1">MB MIS</h1>
            <p class="text-muted small mb-0">Mission Bhagiratha MIS Portal</p>
        </div>

        

        <form method="post" novalidate>
            <input type="hidden" name="csrfmiddlewaretoken" value="MUxbdjX0CMGSxupXPU7Fjj4r5OvigZmFb59QvBfdhokaeMo7dSKOENmx4YqkCbgy">
            <div class="mb-3">
                <label for="id_username" class="form-label fw-semibold">
                    <i class="bi bi-person-badge me-1"></i> Employee ID
                </label>
                <input type="text" name="username" class="form-control form-control-lg" placeholder="Enter Employee ID" autocomplete="username" autofocus maxlength="20" required id="id_username">
                
            </div>
            <div class="mb-3">
                <label for="id_password" class="form-label fw-semibold">
                    <i class="bi bi-lock me-1"></i> Password
                </label>
                <input type="password" name="password" class="form-control form-control-lg" placeholder="Enter Password" autocomplete="current-password" required id="id_password">
                
            </div>
            <div class="mb-3">
                <label for="id_captcha" class="form-label fw-semibold">
                    What is 2 + 9?
                </label>
                <input type="text" name="captcha" class="form-control form-control-lg" inputmode="numeric" autocomplete="off" maxlength="3" required id="id_captcha">
                
            </div>
            
            <button type="submit" class="btn btn-primary btn-lg w-100 mt-2">
                <i class="bi bi-box-arrow-in-right me-1"></i> Sign In
            </button>
        </form>

        <div class="text-center mt-4">
            <a href="/accounts/password-reset/" class="text-decoration-none small">
                <i class="bi bi-question-circle me-1"></i> Forgot Password?
            </a>
        </div>
    </div>
    <p class="text-center text-white-50 small mt-3 mb-0">
        Government of Telangana &mdash; Mission Bhagiratha
    </p>
</div>


    <script src="https://cdn.jsdelivr.net/npm/bootstrap@5.3.3/dist/js/bootstrap.bundle.min.js"></script>
    <script src="/static/js/main.3355e6e2403d.js"></script>
    
</body>
</html>

sitemap.xml 200 OK
Type URL Set URLs 0 entries Valid XML No
B
TLS Certificate Expiry & Recommendations
70 days until leaf cert expires — 3 issues to address
REVIEW

Certificate validity

70
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, 5 assets); document served directly from origin
REVIEW
Assets on Cloudflare (host cdn.jsdelivr.net, 5 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, 5 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: 5), 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: 5 · Cache Status: HIT

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.
A
DNS Records
1 A records, 33 ms lookup
PASS
1 A records, 33 ms lookup
Info::
Resolves to 1 IPv4 address(es)
Got: 117.239.128.227
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: ns74.domaincontrol.com, ns73.domaincontrol.com
Info::
No MX records — email not configured via DNS
Info::
No SPF record found in TXT records
SPF helps prevent email spoofing. Add a TXT record starting with 'v=spf1'.
Info::
DNS resolution time: 33 ms
Got: 33 ms
A117.239.128.227
AAAA—
CNAME—
NSns74.domaincontrol.com, ns73.domaincontrol.com
MX—
TXT—
CAALookup not available with standard resolver
Resolved in 33 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

SPF helps prevent email spoofing. Add a TXT record starting with 'v=spf1'.

Why this matters

Without SPF, receiving servers can't validate sending IPs — your domain is easier to spoof in phishing.

Learn more ▾

SPF complements DMARC. Both should be published. SPF records list authorized sending IPs (e.g., `v=spf1 include:_spf.google.com ~all` for Google Workspace). After publishing, verify in Google Postmaster Tools or mxtoolbox.

Source: RFC 7208 (SPF)

A+
Subdomain Takeover
No subdomain takeover risk detected
PASS
No subdomain takeover risk detected
Info::
No CNAME record present
A+
Multi-Resolver DNS Speed
Mean 26ms across 3 resolvers (spread 9ms)
PASS
Mean 26ms across 3 resolvers (spread 9ms)
Info::
Cloudflare: 23ms
Got: 23ms via 1.1.1.1:53
Info::
Quad9: 23ms
Got: 23ms via 9.9.9.9:53
Info::
Google: 32ms
Got: 32ms via 8.8.8.8:53
A
Redirect Chain
1 redirect(s), 653 ms total
PASS
1 redirect(s), 653 ms total
Info::
Single redirect
Got: https://mbmis.in → https://mbmis.in/accounts/login/?next=/ (302)
Info::
Uses 302 (temporary) redirect
If permanent, use 301 instead.
Got: https://mbmis.in
Info::
Redirect overhead: 653 ms total
Got: 653 ms

https://mbmis.in

486 ms · HTTP/1.1

302

https://mbmis.in/accounts/login/?next=/

166 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://mbmis.in302486 msHTTP/1.1nginx/1.28.3 (Ubuntu)
2https://mbmis.in/accounts/login/?next=/200166 msHTTP/1.1nginx/1.28.3 (Ubuntu)

See the visual redirect chain in the HTTP Probe tab →

If permanent, use 301 instead.

Why this matters

302 (Found) is for genuinely temporary redirects — if this redirect is permanent, switch to 301 to preserve SEO equity.

Learn more ▾

Search engines treat 302 as temporary, keeping the original URL indexed and not transferring full link equity to the destination. Use 301 (Moved Permanently) for permanent redirects (HTTP→HTTPS, www-vs-non-www, URL restructures).

Source: Google Search Central

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

302https://www.mbmis.in/
200https://mbmis.in/

Preferred variant: non-www

HTTP → HTTPS

301http://mbmis.in/ → https://mbmis.in/

Consistent

A+
Domain Intelligence
mbmis.in — via GoDaddy, 19 days old, hosted on BSNL-NIB - National Internet Backbone, IN
PASS
mbmis.in — via GoDaddy, 19 days old, hosted on BSNL-NIB - National Internet Backbone, IN
Info::
Domain registered until Oct 2, 2027 (11 months remaining)
Info::
Domain is only 19 days old
Newly registered domains may face SEO trust challenges. Search engines generally give more authority to older domains. This is informational — not a problem to fix.
Got: Registered Oct 2, 2026
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: GoDaddy
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: BSNL-NIB - National Internet Backbone, IN
Got: AS9829
Domain expiry

344 days

October 2, 2027

SSL certificate

70 days

Issued by Let's Encrypt

Domain age

19 days

Registered October 2, 2026

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

BSNL-NIB - National Internet Backbone, IN

ASN AS9829

117.239.128.227

Registrar

GoDaddy

Unlocked 2 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
  • Newly registered domain — build backlinks and content to establish SEO trust
  • Enable registrar lock (clientTransferProhibited) to block unauthorized domain transfers
Registrar GoDaddy
Created October 2, 2026 (19 days ago)
Expires October 2, 2027 (11 months)
Last Updated October 7, 2026
Name Servers ns74.domaincontrol.com, ns73.domaincontrol.com
DNSSEC Not enabled
Hosting
IP Address 117.239.128.227
ASN AS9829 (BSNL-NIB - National Internet Backbone, IN)
Provider BSNL-NIB - National Internet Backbone, IN
Data source: rdap (1.0s)

Newly registered domains may face SEO trust challenges. Search engines generally give more authority to older domains. This is informational — not a problem to fix.

Why this matters

Informational: domain age. Newer domains may have lower trust signals in spam/security filters.

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

A
HTTP Probe Timing
Total 528 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
PASS
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
37 ms
TCP Connect TCP Connect — time to establish a TCP connection to the server.
160 ms
TLS Handshake TLS Handshake — time to complete the HTTPS encryption handshake.
168 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
529 ms
Total Time Total request time from DNS lookup through full response.
529 ms

Connection waterfall

DNS Lookup 37 ms TCP Connect 160 ms TLS Handshake 168 ms Server Processing 163 ms Content Transfer 0 ms
A+
Health Check Endpoint
Health endpoint at https://mbmis.in/health (HTTP 200)
PASS
Health endpoint at https://mbmis.in/health (HTTP 200)
Info::
Public health endpoint at https://mbmis.in/health
Got: https://mbmis.in/health
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback