Methodology
This page is generated from the same source code that runs the audits (audit/src/checks/registry.ts) — the check list below is never hand-copied and cannot drift out of date with what the site actually runs.
Principles
- Passive only. We fetch pages like a browser would — the homepage and a bounded set of same-site links. No path guessing, no port scans, no form submissions, no login attempts. Security findings come only from response headers and page contents.
- Polite. At most one request per second per site, at most 30 pages and 20 PDFs per audit, `robots.txt` honoured beyond the homepage, and a self-identifying User-Agent.
- Reproducible. Every check is a pure function of the fetched response to a pass/warn/fail/not-applicable result with evidence attached, and has its own automated test.
- Explainable. Every finding states what it means for a citizen and how a webmaster can fix it — never a bare internal check id.
- Charitable. A site is only called "down" after two consecutive failed light checks. A site unreachable only from our vantage point is "unverifiable", not "down".
Two tiers of checks
A light check runs every 6 hours, for every registered site: reachability, HTTP status, redirects, TLS certificate validity, response time and security headers. Adeep audit runs daily on a rolling batch of the sites most overdue or most recently changed, adding accessibility, performance, content and GIGW-compliance checks, plus a screenshot. A site whose homepage changes materially between light checks is bumped to the front of the next deep-audit batch, so the system reacts to change instead of waiting its turn.
Scoring
Availability is a gate, not a component: if a check marked ★ status-settingbelow fails, the site's status is set directly (see the table under "Every check" for which status each one sets) and no score is shown. Otherwise, each of six categories scores 0–100 (100 minus deductions from its failed/warned checks, floored at 0), combined into a weighted overall score:
| Category | Weight |
|---|---|
| Security | 25% |
| Accessibility | 25% |
| Content & maintenance | 15% |
| Government guidelines (GIGW) | 15% |
| Performance & mobile | 10% |
| Identity & hygiene | 10% |
A failed or warned check deducts from its category's score by severity:
| Severity | Deduction on fail | Deduction on warn |
|---|---|---|
| Critical | −40 | −20 |
| High | −20 | −10 |
| Medium | −10 | −5 |
| Low | −4 | −2 |
| Info | −0 | −0 |
The overall score decides the status: 80 or above is Healthy, 50–79 is Needs work, below 50 is Poor. Changing any weight or threshold needs a recorded decision (ADR-006) and a note on this page.
Status definitions
| Status | Meaning |
|---|---|
| Down | Two failed checks in a row — the site did not answer, whether that was a DNS failure, a refused connection, or an HTTP error. |
| Possibly hijacked — do not visit | The address no longer serves the real site — it now shows a parked/for-sale page, redirects to an unrelated domain, or was flagged by a malware check. Do not enter any personal details there. |
| Broken | The site responds, but shows nothing a citizen can use: a blank page, the web server's own default page, an "under construction" notice, or a security certificate a browser blocks. |
| Unverifiable | We could not check this site from our monitoring location — for example, it may only allow visitors from Indian internet connections. It may be working fine for you. |
| Healthy | Scored 80 or above out of 100 in the most recent deep audit. |
| Needs work | Scored 50–79 out of 100 in the most recent deep audit — usable, with real problems worth fixing. |
| Poor | Scored below 50 out of 100 in the most recent deep audit. |
| Not yet audited | No deep audit has run for this site yet — only the lightweight up/down check. |
In charts, statuses are grouped into five colour bands so a picture of 1,500 sites stays readable: Healthy, Needs work, Poor, Down / broken (Down, Possibly hijacked — do not visit, Broken), Not audited (Not yet audited, Unverifiable). Every badge and list still uses the individual status, so "Unverifiable" is never hidden.
A status word is never shown alone on this site (ADR-026): every Down or Broken site page states the specific reason — a DNS failure, a refused connection, an invalid certificate, a blank page, and so on — not just the badge above.
Government and government-aided colleges
Kerala has two kinds of public college. A government college is run directly by the Government of Kerala. A government-aided college is run by a private trust, society or community organisation, but the Government pays its teachers' salaries and fills most of its seats through the state's own admission process. We audit both, and list them separately (government · government-aided) so it is clear who is responsible for each website.
We mark a college as one or the other only when an official document says so: for engineering colleges, theKEAM prospectus published by the Commissioner for Entrance Examinations; for polytechnics, the official name in the Directorate of Technical Education's own list when it says "Government", otherwise the college's own website. Until then a college is shown as "not yet confirmed" — we never guess. Government-aided colleges count toward the headline number of Kerala government websites, because they are publicly funded and publicly regulated.
Action grades
The action report gives every website a grade for its most urgent problem, from 1 (act now) to 5 (minor). Grades come mechanically from each check's own settings, never assigned by hand. A check that onlywarns counts one grade lower than its severity, and can never be grade 1 or 2. Signs of tampering are the top grade but do not change a site's status: a link-text heuristic is not strong enough to tell citizens not to visit a working site. If a finding is wrong, suggest a correction and we fix the check (ADR-028).
| Grade | When | Checks |
|---|---|---|
| Grade 1 — Act now: visitors may be at risk | A check that says the site may be hijacked, or shows signs it has been tampered with, fails. Signs the site may have been tampered with, or that it now points somewhere it should not. | Site redirects to an unrelated domain; Domain shows a "for sale" / parking page; Flagged by Google Safe Browsing; Links to suspicious outside websites |
| Grade 2 — Act now: citizens cannot use the site | A check that makes the site down or broken fails, including a failure seen only by the 6-hourly light check. The site is down, broken or shows a browser warning, so people cannot use it. | Hostname does not resolve; Server did not respond; Page does not load successfully; Server's default page is showing, not the site; Page is effectively empty; "Under construction" page only; Not served over HTTPS at all; HTTPS certificate is invalid or expired |
| Grade 3 — Fix soon | Any other Critical or High finding fails. A serious problem that puts visitors or the site's reliability at risk. | Site keeps going up and down; Plain http:// does not redirect to https://; Certificate is about to expire; Only an old, insecure TLS version is supported; Secure page loads insecure content; Uses a JavaScript library with a known vulnerability; Critical accessibility violations; Page language is missing or wrong; Not set up for mobile screens; "Last updated" date is missing or very old; Placeholder text left on the live site; Uses a non-Unicode Malayalam font; Broken internal links; No "Contact Us" page; No RTI / Public Information Officer details; Not on an official government domain; Domain registration is about to expire |
| Grade 4 — Plan a fix | A Medium finding fails. A real weakness worth scheduling a fix for. | Server is slow to start responding; No HSTS header; No clickjacking protection; Serious accessibility violations; Images missing alt text; Text contrast is too low; Form fields without labels; Main content is slow to appear; Homepage is very large to download; Buttons/links too small or close together on mobile; Footer copyright year is old; News/announcements section is stale; Uses obsolete web technology; Linked PDFs are missing; No Malayalam version available; Page title is missing or generic; No sitemap page; No Privacy Policy; No Accessibility Statement; No content-ownership statement; No last-updated date shown; Running old, unsupported software |
| Grade 5 — Minor | A Low finding fails. A small improvement; nothing urgent. | No Content-Security-Policy header; No X-Content-Type-Options header; No Referrer-Policy header; Server discloses exact software versions; Minor accessibility issues; Heading structure is missing or broken; No "skip to content" link; Possible keyboard-navigation trap; Page layout jumps around while loading; Images are uncompressed or oversized; "Best viewed in..." notice; Broken images; No meta description; No favicon; JavaScript errors on load; No feedback mechanism; No Terms & Conditions / Terms of Use; No Copyright Policy; No Hyperlinking Policy; No Disclaimer; No Screen Reader Access page; No Help page; No site search; www and non-www versions are inconsistent; No robots.txt; No sitemap.xml; Missing pages return "200 OK" instead of a proper error; Missing UTF-8 charset or HTML5 doctype |
Vantage point and geo-blocking
Our checks run from GitHub Actions runners in the US/EU. Some Kerala government sites are hosted behind infrastructure that blocks or throttles non-Indian traffic; calling those sites "down" would be wrong and unfair to a working site. When a check sees a block signature consistent with this (a specific 403 page, or a timeout on a host that other evidence shows is up), the site is marked Unverifiable instead — listed separately, never counted as broken. A self-hosted monitoring point inside India, once available, would resolve these to a real answer; until then the site honestly reports what it could not check.
How to contest a finding
Every status-setting finding stores the evidence that produced it (the exact response code, matched text, or final URL) on the site's own page, so anyone can verify it independently. If a finding looks wrong, or a site has since been fixed, open an issue onthe project's issue trackerdescribing what changed — a re-check can then be run within the hour rather than waiting for the site's next scheduled turn.
Limitations
- Passive checks cannot see behaviour behind a login or a form submission. A site that looks fine on its public pages can still have broken functionality we have no way to observe without acting like an authenticated user, which we deliberately do not do.
- Lighthouse scores are indicative only and never set a status or fail a check outright — shared CI runners have too much run-to-run variance to trust as a hard gate (ADR-015).
- Not every registered site has a deep audit yet. Deep audits run on a rolling batch; a site shows "Not yet audited" for its full score until its first one completes, even though its light up/down status is already real and current.
- GIGW-compliance checks are heuristic. They look for expected link/heading text in English and Malayalam (Contact Us, Sitemap, Privacy Policy, and so on) on the homepage; a compliant page using unusual wording could be missed.
- This is an independent project, not an official audit. It has no legal or administrative authority over any department, and every finding is a starting point for a department to investigate, not a final verdict.
Every check (85)
★ means the check sets the site's status directly on failure, instead of only affecting its category's score (see Scoring, above).
Availability (11)
| Check | Severity | Sets status | Reference |
|---|---|---|---|
avail.blank Page is effectively empty | Critical | Broken | — |
avail.connect Server did not respond | Critical | Down | — |
avail.default_page Server's default page is showing, not the site | Critical | Broken | — |
avail.dns Hostname does not resolve | Critical | Down | — |
avail.flapping Site keeps going up and down | High | — | — |
avail.geo_blocked Blocked from where we check from | Info | Unverifiable | — |
avail.parked Domain shows a "for sale" / parking page | Critical | Possibly hijacked — do not visit | — |
avail.redirect_offsite Site redirects to an unrelated domain | Critical | Possibly hijacked — do not visit | — |
avail.status Page does not load successfully | Critical | Down | — |
avail.ttfb Server is slow to start responding | Medium | — | — |
avail.under_construction "Under construction" page only | High | Broken | — |
Security (15)
| Check | Severity | Sets status | Reference |
|---|---|---|---|
sec.cert_expiry Certificate is about to expire | High | — | — |
sec.cert_valid HTTPS certificate is invalid or expired | Critical | Broken | — |
sec.csp No Content-Security-Policy header | Low | — | OWASP Secure Headers |
sec.hsts No HSTS header | Medium | — | OWASP Secure Headers |
sec.http_redirect Plain http:// does not redirect to https:// | High | — | — |
sec.https Not served over HTTPS at all | Critical | Broken | — |
sec.injected_links Links to suspicious outside websites | Critical | — | OWASP A03:2021 Injection |
sec.mixed_content Secure page loads insecure content | High | — | — |
sec.referrer No Referrer-Policy header | Low | — | OWASP Secure Headers |
sec.safe_browsing Flagged by Google Safe Browsing | Critical | Possibly hijacked — do not visit | — |
sec.server_banner Server discloses exact software versions | Low | — | — |
sec.tls_version Only an old, insecure TLS version is supported | High | — | — |
sec.vuln_js Uses a JavaScript library with a known vulnerability | High | — | OWASP A06:2021 Vulnerable and Outdated Components |
sec.xcto No X-Content-Type-Options header | Low | — | OWASP Secure Headers |
sec.xfo No clickjacking protection | Medium | — | OWASP Secure Headers |
Accessibility (11)
| Check | Severity | Sets status | Reference |
|---|---|---|---|
a11y.alt Images missing alt text | Medium | — | WCAG 2.1 SC 1.1.1 |
a11y.axe_critical Critical accessibility violations | High | — | WCAG 2.1 AA |
a11y.axe_moderate_minor Minor accessibility issues | Low | — | WCAG 2.1 AA |
a11y.axe_serious Serious accessibility violations | Medium | — | WCAG 2.1 AA |
a11y.contrast Text contrast is too low | Medium | — | WCAG 2.1 SC 1.4.3 |
a11y.headings Heading structure is missing or broken | Low | — | WCAG 2.1 SC 1.3.1 |
a11y.keyboard Possible keyboard-navigation trap | Low | — | WCAG 2.1 SC 2.1.1 |
a11y.labels Form fields without labels | Medium | — | WCAG 2.1 SC 4.1.2 |
a11y.lang Page language is missing or wrong | High | — | WCAG 2.1 SC 3.1.1 |
a11y.lighthouse Lighthouse accessibility score | Info | — | — |
a11y.skip_link No "skip to content" link | Low | — | WCAG 2.1 SC 2.4.1 |
Content & maintenance (15)
| Check | Severity | Sets status | Reference |
|---|---|---|---|
content.best_viewed "Best viewed in..." notice | Low | — | — |
content.broken_images Broken images | Low | — | — |
content.broken_links Broken internal links | High | — | — |
content.broken_pdfs Linked PDFs are missing | Medium | — | — |
content.console_errors JavaScript errors on load | Low | — | — |
content.copyright_year Footer copyright year is old | Medium | — | — |
content.favicon No favicon | Low | — | — |
content.last_updated "Last updated" date is missing or very old | High | — | GIGW 3.0 |
content.legacy_font Uses a non-Unicode Malayalam font | High | — | — |
content.malayalam No Malayalam version available | Medium | — | — |
content.meta_desc No meta description | Low | — | — |
content.obsolete_tech Uses obsolete web technology | Medium | — | — |
content.placeholder Placeholder text left on the live site | High | — | — |
content.stale_news News/announcements section is stale | Medium | — | — |
content.title Page title is missing or generic | Medium | — | — |
Government guidelines (GIGW) (16)
| Check | Severity | Sets status | Reference |
|---|---|---|---|
gigw.accessibility_statement No Accessibility Statement | Medium | — | GIGW 3.0 |
gigw.contact No "Contact Us" page | High | — | GIGW 3.0 |
gigw.copyright_policy No Copyright Policy | Low | — | GIGW 3.0 |
gigw.disclaimer No Disclaimer | Low | — | GIGW 3.0 |
gigw.emblem No state/national emblem shown | Info | — | GIGW 3.0 |
gigw.feedback No feedback mechanism | Low | — | GIGW 3.0 |
gigw.help No Help page | Low | — | GIGW 3.0 |
gigw.hyperlink_policy No Hyperlinking Policy | Low | — | GIGW 3.0 |
gigw.last_updated No last-updated date shown | Medium | — | GIGW 3.0 |
gigw.ownership No content-ownership statement | Medium | — | GIGW 3.0 |
gigw.privacy No Privacy Policy | Medium | — | GIGW 3.0 |
gigw.rti No RTI / Public Information Officer details | High | — | RTI Act 2005 s.4 |
gigw.screen_reader No Screen Reader Access page | Low | — | GIGW 3.0 |
gigw.search No site search | Low | — | GIGW 3.0 |
gigw.sitemap No sitemap page | Medium | — | GIGW 3.0 |
gigw.terms No Terms & Conditions / Terms of Use | Low | — | GIGW 3.0 |
Performance & mobile (7)
| Check | Severity | Sets status | Reference |
|---|---|---|---|
perf.cls Page layout jumps around while loading | Low | — | — |
perf.images Images are uncompressed or oversized | Low | — | — |
perf.lcp Main content is slow to appear | Medium | — | — |
perf.lighthouse Lighthouse performance score | Info | — | — |
perf.tap_targets Buttons/links too small or close together on mobile | Medium | — | — |
perf.viewport Not set up for mobile screens | High | — | — |
perf.weight Homepage is very large to download | Medium | — | — |
Identity & hygiene (10)
| Check | Severity | Sets status | Reference |
|---|---|---|---|
id.canonical No canonical link tag | Info | — | — |
id.charset_doctype Missing UTF-8 charset or HTML5 doctype | Low | — | — |
id.domain_expiry Domain registration is about to expire | High | — | — |
id.gov_domain Not on an official government domain | High | — | — |
id.robots No robots.txt | Low | — | — |
id.sitemap_xml No sitemap.xml | Low | — | — |
id.soft_404 Missing pages return "200 OK" instead of a proper error | Low | — | — |
id.tech Running old, unsupported software | Medium | — | — |
id.third_party Loads third-party trackers | Info | — | — |
id.www_consistency www and non-www versions are inconsistent | Low | — | — |
Full check explanations (what a finding means for a citizen, and how to fix it) are shown on each audited site's own page as they apply. Seedocs/DESIGN.mdfor the full design.