Manifest position 609 · CrUX rank bucket 1000
https://vahan.parivahan.gov.in
Blocked after retries
The origin resolved to 164.100.69.3, but the server reset the TLS connection before returning an HTTP response. Chrome showed ERR_CONNECTION_RESET on repeated desktop, mobile, dark-mode, crawler, header, HAR, and layout attempts; curl independently reported “Recv failure: Connection reset by peer”.
Attempts
3 / 3
Judged checks
0 / 58
Blocked
58
Not run
0
This report has no published overall score. Blocked and not-run checks are not passes. A coverage-complete report means every check has a judged outcome; it does not mean every check passed.
All 58 atomic check outcomes
| Principle / check | Status | Confidence | Evidence or reason |
|---|---|---|---|
respect-user-preferencesrespects-color-scheme | blocked | high | The origin resolved to 164.100.69.3, but the server reset the TLS connection before returning an HTTP response. Chrome showed ERR_CONNECTION_RESET on repeated desktop, mobile, dark-mode, crawler, header, HAR, and layout attempts; curl independently reported “Recv failure: Connection reset by peer”. |
respect-user-preferencesrespects-reduced-motion | blocked | high | The origin resolved to 164.100.69.3, but the server reset the TLS connection before returning an HTTP response. Chrome showed ERR_CONNECTION_RESET on repeated desktop, mobile, dark-mode, crawler, header, HAR, and layout attempts; curl independently reported “Recv failure: Connection reset by peer”. |
respect-user-preferencesrespects-contrast | blocked | high | The origin resolved to 164.100.69.3, but the server reset the TLS connection before returning an HTTP response. Chrome showed ERR_CONNECTION_RESET on repeated desktop, mobile, dark-mode, crawler, header, HAR, and layout attempts; curl independently reported “Recv failure: Connection reset by peer”. |
implement-natural-interactionsview-transitions | blocked | high | The origin resolved to 164.100.69.3, but the server reset the TLS connection before returning an HTTP response. Chrome showed ERR_CONNECTION_RESET on repeated desktop, mobile, dark-mode, crawler, header, HAR, and layout attempts; curl independently reported “Recv failure: Connection reset by peer”. |
implement-natural-interactionsscroll-driven-animations | blocked | high | The origin resolved to 164.100.69.3, but the server reset the TLS connection before returning an HTTP response. Chrome showed ERR_CONNECTION_RESET on repeated desktop, mobile, dark-mode, crawler, header, HAR, and layout attempts; curl independently reported “Recv failure: Connection reset by peer”. |
implement-natural-interactionsphysical-gestures | blocked | high | The origin resolved to 164.100.69.3, but the server reset the TLS connection before returning an HTTP response. Chrome showed ERR_CONNECTION_RESET on repeated desktop, mobile, dark-mode, crawler, header, HAR, and layout attempts; curl independently reported “Recv failure: Connection reset by peer”. |
provide-guided-navigationscroll-state-aware-chrome | blocked | high | The origin resolved to 164.100.69.3, but the server reset the TLS connection before returning an HTTP response. Chrome showed ERR_CONNECTION_RESET on repeated desktop, mobile, dark-mode, crawler, header, HAR, and layout attempts; curl independently reported “Recv failure: Connection reset by peer”. |
provide-guided-navigationanchored-positioning | blocked | high | The origin resolved to 164.100.69.3, but the server reset the TLS connection before returning an HTTP response. Chrome showed ERR_CONNECTION_RESET on repeated desktop, mobile, dark-mode, crawler, header, HAR, and layout attempts; curl independently reported “Recv failure: Connection reset by peer”. |
provide-guided-navigationdirects-attention | blocked | high | The origin resolved to 164.100.69.3, but the server reset the TLS connection before returning an HTTP response. Chrome showed ERR_CONNECTION_RESET on repeated desktop, mobile, dark-mode, crawler, header, HAR, and layout attempts; curl independently reported “Recv failure: Connection reset by peer”. |
maximize-content-reduce-noiseno-intrusive-interruptions | blocked | high | The origin resolved to 164.100.69.3, but the server reset the TLS connection before returning an HTTP response. Chrome showed ERR_CONNECTION_RESET on repeated desktop, mobile, dark-mode, crawler, header, HAR, and layout attempts; curl independently reported “Recv failure: Connection reset by peer”. |
maximize-content-reduce-noisesemantic-dismissible-primitives | blocked | high | The origin resolved to 164.100.69.3, but the server reset the TLS connection before returning an HTTP response. Chrome showed ERR_CONNECTION_RESET on repeated desktop, mobile, dark-mode, crawler, header, HAR, and layout attempts; curl independently reported “Recv failure: Connection reset by peer”. |
maximize-content-reduce-noisereduced-chrome | blocked | high | The origin resolved to 164.100.69.3, but the server reset the TLS connection before returning an HTTP response. Chrome showed ERR_CONNECTION_RESET on repeated desktop, mobile, dark-mode, crawler, header, HAR, and layout attempts; curl independently reported “Recv failure: Connection reset by peer”. |
adapt-to-the-form-factorresponsive-no-horizontal-scroll | blocked | high | The origin resolved to 164.100.69.3, but the server reset the TLS connection before returning an HTTP response. Chrome showed ERR_CONNECTION_RESET on repeated desktop, mobile, dark-mode, crawler, header, HAR, and layout attempts; curl independently reported “Recv failure: Connection reset by peer”. |
adapt-to-the-form-factorcomponent-level-responsiveness | blocked | high | The origin resolved to 164.100.69.3, but the server reset the TLS connection before returning an HTTP response. Chrome showed ERR_CONNECTION_RESET on repeated desktop, mobile, dark-mode, crawler, header, HAR, and layout attempts; curl independently reported “Recv failure: Connection reset by peer”. |
adapt-to-the-form-factorinput-modality-aware | blocked | high | The origin resolved to 164.100.69.3, but the server reset the TLS connection before returning an HTTP response. Chrome showed ERR_CONNECTION_RESET on repeated desktop, mobile, dark-mode, crawler, header, HAR, and layout attempts; curl independently reported “Recv failure: Connection reset by peer”. |
support-core-task-successclear-purpose-and-primary-action | blocked | high | The origin resolved to 164.100.69.3, but the server reset the TLS connection before returning an HTTP response. Chrome showed ERR_CONNECTION_RESET on repeated desktop, mobile, dark-mode, crawler, header, HAR, and layout attempts; curl independently reported “Recv failure: Connection reset by peer”. |
support-core-task-successprimary-flow-completion | blocked | high | The origin resolved to 164.100.69.3, but the server reset the TLS connection before returning an HTTP response. Chrome showed ERR_CONNECTION_RESET on repeated desktop, mobile, dark-mode, crawler, header, HAR, and layout attempts; curl independently reported “Recv failure: Connection reset by peer”. |
support-core-task-successclear-system-state-and-recovery | blocked | high | The origin resolved to 164.100.69.3, but the server reset the TLS connection before returning an HTTP response. Chrome showed ERR_CONNECTION_RESET on repeated desktop, mobile, dark-mode, crawler, header, HAR, and layout attempts; curl independently reported “Recv failure: Connection reset by peer”. |
be-fast-and-stablegood-core-web-vitals | blocked | high | The origin resolved to 164.100.69.3, but the server reset the TLS connection before returning an HTTP response. Chrome showed ERR_CONNECTION_RESET on repeated desktop, mobile, dark-mode, crawler, header, HAR, and layout attempts; curl independently reported “Recv failure: Connection reset by peer”. |
be-fast-and-stablevisual-stability | blocked | high | The origin resolved to 164.100.69.3, but the server reset the TLS connection before returning an HTTP response. Chrome showed ERR_CONNECTION_RESET on repeated desktop, mobile, dark-mode, crawler, header, HAR, and layout attempts; curl independently reported “Recv failure: Connection reset by peer”. |
be-fast-and-stableefficient-main-thread | blocked | high | The origin resolved to 164.100.69.3, but the server reset the TLS connection before returning an HTTP response. Chrome showed ERR_CONNECTION_RESET on repeated desktop, mobile, dark-mode, crawler, header, HAR, and layout attempts; curl independently reported “Recv failure: Connection reset by peer”. |
be-fast-and-stableefficient-resource-delivery | blocked | high | The origin resolved to 164.100.69.3, but the server reset the TLS connection before returning an HTTP response. Chrome showed ERR_CONNECTION_RESET on repeated desktop, mobile, dark-mode, crawler, header, HAR, and layout attempts; curl independently reported “Recv failure: Connection reset by peer”. |
be-fast-and-stabletrim-unused-and-duplicate-code | blocked | high | The origin resolved to 164.100.69.3, but the server reset the TLS connection before returning an HTTP response. Chrome showed ERR_CONNECTION_RESET on repeated desktop, mobile, dark-mode, crawler, header, HAR, and layout attempts; curl independently reported “Recv failure: Connection reset by peer”. |
be-inclusivenames-roles-labels | blocked | high | The origin resolved to 164.100.69.3, but the server reset the TLS connection before returning an HTTP response. Chrome showed ERR_CONNECTION_RESET on repeated desktop, mobile, dark-mode, crawler, header, HAR, and layout attempts; curl independently reported “Recv failure: Connection reset by peer”. |
be-inclusivesufficient-contrast | blocked | high | The origin resolved to 164.100.69.3, but the server reset the TLS connection before returning an HTTP response. Chrome showed ERR_CONNECTION_RESET on repeated desktop, mobile, dark-mode, crawler, header, HAR, and layout attempts; curl independently reported “Recv failure: Connection reset by peer”. |
be-inclusivestructure-and-focus | blocked | high | The origin resolved to 164.100.69.3, but the server reset the TLS connection before returning an HTTP response. Chrome showed ERR_CONNECTION_RESET on repeated desktop, mobile, dark-mode, crawler, header, HAR, and layout attempts; curl independently reported “Recv failure: Connection reset by peer”. |
be-inclusivelegible-text | blocked | high | The origin resolved to 164.100.69.3, but the server reset the TLS connection before returning an HTTP response. Chrome showed ERR_CONNECTION_RESET on repeated desktop, mobile, dark-mode, crawler, header, HAR, and layout attempts; curl independently reported “Recv failure: Connection reset by peer”. |
be-inclusivezoom-reflow-targets-and-media | blocked | high | The origin resolved to 164.100.69.3, but the server reset the TLS connection before returning an HTTP response. Chrome showed ERR_CONNECTION_RESET on repeated desktop, mobile, dark-mode, crawler, header, HAR, and layout attempts; curl independently reported “Recv failure: Connection reset by peer”. |
follow-best-practicesno-console-errors | blocked | high | The origin resolved to 164.100.69.3, but the server reset the TLS connection before returning an HTTP response. Chrome showed ERR_CONNECTION_RESET on repeated desktop, mobile, dark-mode, crawler, header, HAR, and layout attempts; curl independently reported “Recv failure: Connection reset by peer”. |
follow-best-practicessound-document-and-assets | blocked | high | The origin resolved to 164.100.69.3, but the server reset the TLS connection before returning an HTTP response. Chrome showed ERR_CONNECTION_RESET on repeated desktop, mobile, dark-mode, crawler, header, HAR, and layout attempts; curl independently reported “Recv failure: Connection reset by peer”. |
follow-best-practicesbrowser-platform-hygiene | blocked | high | The origin resolved to 164.100.69.3, but the server reset the TLS connection before returning an HTTP response. Chrome showed ERR_CONNECTION_RESET on repeated desktop, mobile, dark-mode, crawler, header, HAR, and layout attempts; curl independently reported “Recv failure: Connection reset by peer”. |
be-discoverabletitle-and-description | blocked | high | The origin resolved to 164.100.69.3, but the server reset the TLS connection before returning an HTTP response. Chrome showed ERR_CONNECTION_RESET on repeated desktop, mobile, dark-mode, crawler, header, HAR, and layout attempts; curl independently reported “Recv failure: Connection reset by peer”. |
be-discoverablecrawlable-and-mobile-friendly | blocked | high | The origin resolved to 164.100.69.3, but the server reset the TLS connection before returning an HTTP response. Chrome showed ERR_CONNECTION_RESET on repeated desktop, mobile, dark-mode, crawler, header, HAR, and layout attempts; curl independently reported “Recv failure: Connection reset by peer”. |
be-discoverablecanonical-and-indexing-signals | blocked | high | The origin resolved to 164.100.69.3, but the server reset the TLS connection before returning an HTTP response. Chrome showed ERR_CONNECTION_RESET on repeated desktop, mobile, dark-mode, crawler, header, HAR, and layout attempts; curl independently reported “Recv failure: Connection reset by peer”. |
be-discoverablestructured-and-shareable-metadata | blocked | high | The origin resolved to 164.100.69.3, but the server reset the TLS connection before returning an HTTP response. Chrome showed ERR_CONNECTION_RESET on repeated desktop, mobile, dark-mode, crawler, header, HAR, and layout attempts; curl independently reported “Recv failure: Connection reset by peer”. |
be-private-and-securesecure-transport-and-headers | blocked | high | The origin resolved to 164.100.69.3, but the server reset the TLS connection before returning an HTTP response. Chrome showed ERR_CONNECTION_RESET on repeated desktop, mobile, dark-mode, crawler, header, HAR, and layout attempts; curl independently reported “Recv failure: Connection reset by peer”. |
be-private-and-securedata-minimisation-and-third-parties | blocked | high | The origin resolved to 164.100.69.3, but the server reset the TLS connection before returning an HTTP response. Chrome showed ERR_CONNECTION_RESET on repeated desktop, mobile, dark-mode, crawler, header, HAR, and layout attempts; curl independently reported “Recv failure: Connection reset by peer”. |
be-private-and-securein-context-permissions-and-modern-auth | blocked | high | The origin resolved to 164.100.69.3, but the server reset the TLS connection before returning an HTTP response. Chrome showed ERR_CONNECTION_RESET on repeated desktop, mobile, dark-mode, crawler, header, HAR, and layout attempts; curl independently reported “Recv failure: Connection reset by peer”. |
be-private-and-securedefensive-browser-policies | blocked | high | The origin resolved to 164.100.69.3, but the server reset the TLS connection before returning an HTTP response. Chrome showed ERR_CONNECTION_RESET on repeated desktop, mobile, dark-mode, crawler, header, HAR, and layout attempts; curl independently reported “Recv failure: Connection reset by peer”. |
be-resilientprogressive-enhancement | blocked | high | The origin resolved to 164.100.69.3, but the server reset the TLS connection before returning an HTTP response. Chrome showed ERR_CONNECTION_RESET on repeated desktop, mobile, dark-mode, crawler, header, HAR, and layout attempts; curl independently reported “Recv failure: Connection reset by peer”. |
be-resilientresilient-runtime-behaviour | blocked | high | The origin resolved to 164.100.69.3, but the server reset the TLS connection before returning an HTTP response. Chrome showed ERR_CONNECTION_RESET on repeated desktop, mobile, dark-mode, crawler, header, HAR, and layout attempts; curl independently reported “Recv failure: Connection reset by peer”. |
be-resilientoffline-and-installable | blocked | high | The origin resolved to 164.100.69.3, but the server reset the TLS connection before returning an HTTP response. Chrome showed ERR_CONNECTION_RESET on repeated desktop, mobile, dark-mode, crawler, header, HAR, and layout attempts; curl independently reported “Recv failure: Connection reset by peer”. |
be-resilientnetwork-and-http-failure-states | blocked | high | The origin resolved to 164.100.69.3, but the server reset the TLS connection before returning an HTTP response. Chrome showed ERR_CONNECTION_RESET on repeated desktop, mobile, dark-mode, crawler, header, HAR, and layout attempts; curl independently reported “Recv failure: Connection reset by peer”. |
be-internationalisedlang-dir-and-logical-properties | blocked | high | The origin resolved to 164.100.69.3, but the server reset the TLS connection before returning an HTTP response. Chrome showed ERR_CONNECTION_RESET on repeated desktop, mobile, dark-mode, crawler, header, HAR, and layout attempts; curl independently reported “Recv failure: Connection reset by peer”. |
be-internationalisedlocale-aware-data | blocked | high | The origin resolved to 164.100.69.3, but the server reset the TLS connection before returning an HTTP response. Chrome showed ERR_CONNECTION_RESET on repeated desktop, mobile, dark-mode, crawler, header, HAR, and layout attempts; curl independently reported “Recv failure: Connection reset by peer”. |
be-internationalisedtime-zone-correctness | blocked | high | The origin resolved to 164.100.69.3, but the server reset the TLS connection before returning an HTTP response. Chrome showed ERR_CONNECTION_RESET on repeated desktop, mobile, dark-mode, crawler, header, HAR, and layout attempts; curl independently reported “Recv failure: Connection reset by peer”. |
be-trustworthyno-dark-patterns | blocked | high | The origin resolved to 164.100.69.3, but the server reset the TLS connection before returning an HTTP response. Chrome showed ERR_CONNECTION_RESET on repeated desktop, mobile, dark-mode, crawler, header, HAR, and layout attempts; curl independently reported “Recv failure: Connection reset by peer”. |
be-trustworthyhumane-error-handling | blocked | high | The origin resolved to 164.100.69.3, but the server reset the TLS connection before returning an HTTP response. Chrome showed ERR_CONNECTION_RESET on repeated desktop, mobile, dark-mode, crawler, header, HAR, and layout attempts; curl independently reported “Recv failure: Connection reset by peer”. |
be-trustworthytrustworthy-input-assistance | blocked | high | The origin resolved to 164.100.69.3, but the server reset the TLS connection before returning an HTTP response. Chrome showed ERR_CONNECTION_RESET on repeated desktop, mobile, dark-mode, crawler, header, HAR, and layout attempts; curl independently reported “Recv failure: Connection reset by peer”. |
be-trustworthysafe-commercial-and-account-flows | blocked | high | The origin resolved to 164.100.69.3, but the server reset the TLS connection before returning an HTTP response. Chrome showed ERR_CONNECTION_RESET on repeated desktop, mobile, dark-mode, crawler, header, HAR, and layout attempts; curl independently reported “Recv failure: Connection reset by peer”. |
be-sustainableoptimised-assets | blocked | high | The origin resolved to 164.100.69.3, but the server reset the TLS connection before returning an HTTP response. Chrome showed ERR_CONNECTION_RESET on repeated desktop, mobile, dark-mode, crawler, header, HAR, and layout attempts; curl independently reported “Recv failure: Connection reset by peer”. |
be-sustainableno-wasteful-work | blocked | high | The origin resolved to 164.100.69.3, but the server reset the TLS connection before returning an HTTP response. Chrome showed ERR_CONNECTION_RESET on repeated desktop, mobile, dark-mode, crawler, header, HAR, and layout attempts; curl independently reported “Recv failure: Connection reset by peer”. |
be-sustainablethird-party-and-media-budget | blocked | high | The origin resolved to 164.100.69.3, but the server reset the TLS connection before returning an HTTP response. Chrome showed ERR_CONNECTION_RESET on repeated desktop, mobile, dark-mode, crawler, header, HAR, and layout attempts; curl independently reported “Recv failure: Connection reset by peer”. |
be-agent-readystructured-agent-capabilities | blocked | high | The origin resolved to 164.100.69.3, but the server reset the TLS connection before returning an HTTP response. Chrome showed ERR_CONNECTION_RESET on repeated desktop, mobile, dark-mode, crawler, header, HAR, and layout attempts; curl independently reported “Recv failure: Connection reset by peer”. |
be-agent-readyon-device-inference | blocked | high | The origin resolved to 164.100.69.3, but the server reset the TLS connection before returning an HTTP response. Chrome showed ERR_CONNECTION_RESET on repeated desktop, mobile, dark-mode, crawler, header, HAR, and layout attempts; curl independently reported “Recv failure: Connection reset by peer”. |
be-memory-efficientno-leak-under-repeated-interaction | blocked | high | The origin resolved to 164.100.69.3, but the server reset the TLS connection before returning an HTTP response. Chrome showed ERR_CONNECTION_RESET on repeated desktop, mobile, dark-mode, crawler, header, HAR, and layout attempts; curl independently reported “Recv failure: Connection reset by peer”. |
be-memory-efficientbounded-footprint | blocked | high | The origin resolved to 164.100.69.3, but the server reset the TLS connection before returning an HTTP response. Chrome showed ERR_CONNECTION_RESET on repeated desktop, mobile, dark-mode, crawler, header, HAR, and layout attempts; curl independently reported “Recv failure: Connection reset by peer”. |
be-memory-efficientno-detached-dom-or-unbounded-listeners | blocked | high | The origin resolved to 164.100.69.3, but the server reset the TLS connection before returning an HTTP response. Chrome showed ERR_CONNECTION_RESET on repeated desktop, mobile, dark-mode, crawler, header, HAR, and layout attempts; curl independently reported “Recv failure: Connection reset by peer”. |
Provenance
Canonical report: results/atomic/reports/0609-vahan_parivahan_gov_in.json
Report SHA-256: 30997acf198e39172e9e9f4d0729680e4ec01fa4fd7daa9599f5f4c073af2b48
Local retained report: runs/2026-07-17T17-27-24-856Z/atomic-reports/vahan_parivahan_gov_in/2026-07-28T03-22-32-462Z/report.json
Local evidence root: runs/2026-07-17T17-27-24-856Z/atomic-reports/vahan_parivahan_gov_in/2026-07-28T03-22-32-462Z
Catalog SHA-256: sha256:78ccfdb2d483f4c57d9dafed80fd86c6265585a56457c8dcfddc254b80fb44d7
Raw screenshots, HARs, traces, heaps, and other browser artifacts are retained at the local evidence root and intentionally are not committed. Artifact paths in the canonical report are relative to that root.