Manifest position 493 · CrUX rank bucket 1000
https://socialregistry.wb.gov.in
Blocked after retries
The hostname resolves, but HTTPS port 443 did not accept a connection from the audit environment. All 58 atomic checks are blocked and the run is not complete.
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 | DNS resolved socialregistry.wb.gov.in to 103.38.191.101, but TCP port 443 timed out in curl (10–20 s), OpenSSL (15 s), and four independent Chrome evidence attempts (90 s each); no HTTP response or rendered state was available. |
respect-user-preferencesrespects-reduced-motion | blocked | high | DNS resolved socialregistry.wb.gov.in to 103.38.191.101, but TCP port 443 timed out in curl (10–20 s), OpenSSL (15 s), and four independent Chrome evidence attempts (90 s each); no HTTP response or rendered state was available. |
respect-user-preferencesrespects-contrast | blocked | high | DNS resolved socialregistry.wb.gov.in to 103.38.191.101, but TCP port 443 timed out in curl (10–20 s), OpenSSL (15 s), and four independent Chrome evidence attempts (90 s each); no HTTP response or rendered state was available. |
implement-natural-interactionsview-transitions | blocked | high | DNS resolved socialregistry.wb.gov.in to 103.38.191.101, but TCP port 443 timed out in curl (10–20 s), OpenSSL (15 s), and four independent Chrome evidence attempts (90 s each); no HTTP response or rendered state was available. |
implement-natural-interactionsscroll-driven-animations | blocked | high | DNS resolved socialregistry.wb.gov.in to 103.38.191.101, but TCP port 443 timed out in curl (10–20 s), OpenSSL (15 s), and four independent Chrome evidence attempts (90 s each); no HTTP response or rendered state was available. |
implement-natural-interactionsphysical-gestures | blocked | high | DNS resolved socialregistry.wb.gov.in to 103.38.191.101, but TCP port 443 timed out in curl (10–20 s), OpenSSL (15 s), and four independent Chrome evidence attempts (90 s each); no HTTP response or rendered state was available. |
provide-guided-navigationscroll-state-aware-chrome | blocked | high | DNS resolved socialregistry.wb.gov.in to 103.38.191.101, but TCP port 443 timed out in curl (10–20 s), OpenSSL (15 s), and four independent Chrome evidence attempts (90 s each); no HTTP response or rendered state was available. |
provide-guided-navigationanchored-positioning | blocked | high | DNS resolved socialregistry.wb.gov.in to 103.38.191.101, but TCP port 443 timed out in curl (10–20 s), OpenSSL (15 s), and four independent Chrome evidence attempts (90 s each); no HTTP response or rendered state was available. |
provide-guided-navigationdirects-attention | blocked | high | DNS resolved socialregistry.wb.gov.in to 103.38.191.101, but TCP port 443 timed out in curl (10–20 s), OpenSSL (15 s), and four independent Chrome evidence attempts (90 s each); no HTTP response or rendered state was available. |
maximize-content-reduce-noiseno-intrusive-interruptions | blocked | high | DNS resolved socialregistry.wb.gov.in to 103.38.191.101, but TCP port 443 timed out in curl (10–20 s), OpenSSL (15 s), and four independent Chrome evidence attempts (90 s each); no HTTP response or rendered state was available. |
maximize-content-reduce-noisesemantic-dismissible-primitives | blocked | high | DNS resolved socialregistry.wb.gov.in to 103.38.191.101, but TCP port 443 timed out in curl (10–20 s), OpenSSL (15 s), and four independent Chrome evidence attempts (90 s each); no HTTP response or rendered state was available. |
maximize-content-reduce-noisereduced-chrome | blocked | high | DNS resolved socialregistry.wb.gov.in to 103.38.191.101, but TCP port 443 timed out in curl (10–20 s), OpenSSL (15 s), and four independent Chrome evidence attempts (90 s each); no HTTP response or rendered state was available. |
adapt-to-the-form-factorresponsive-no-horizontal-scroll | blocked | high | DNS resolved socialregistry.wb.gov.in to 103.38.191.101, but TCP port 443 timed out in curl (10–20 s), OpenSSL (15 s), and four independent Chrome evidence attempts (90 s each); no HTTP response or rendered state was available. |
adapt-to-the-form-factorcomponent-level-responsiveness | blocked | high | DNS resolved socialregistry.wb.gov.in to 103.38.191.101, but TCP port 443 timed out in curl (10–20 s), OpenSSL (15 s), and four independent Chrome evidence attempts (90 s each); no HTTP response or rendered state was available. |
adapt-to-the-form-factorinput-modality-aware | blocked | high | DNS resolved socialregistry.wb.gov.in to 103.38.191.101, but TCP port 443 timed out in curl (10–20 s), OpenSSL (15 s), and four independent Chrome evidence attempts (90 s each); no HTTP response or rendered state was available. |
support-core-task-successclear-purpose-and-primary-action | blocked | high | DNS resolved socialregistry.wb.gov.in to 103.38.191.101, but TCP port 443 timed out in curl (10–20 s), OpenSSL (15 s), and four independent Chrome evidence attempts (90 s each); no HTTP response or rendered state was available. |
support-core-task-successprimary-flow-completion | blocked | high | DNS resolved socialregistry.wb.gov.in to 103.38.191.101, but TCP port 443 timed out in curl (10–20 s), OpenSSL (15 s), and four independent Chrome evidence attempts (90 s each); no HTTP response or rendered state was available. |
support-core-task-successclear-system-state-and-recovery | blocked | high | DNS resolved socialregistry.wb.gov.in to 103.38.191.101, but TCP port 443 timed out in curl (10–20 s), OpenSSL (15 s), and four independent Chrome evidence attempts (90 s each); no HTTP response or rendered state was available. |
be-fast-and-stablegood-core-web-vitals | blocked | high | DNS resolved socialregistry.wb.gov.in to 103.38.191.101, but TCP port 443 timed out in curl (10–20 s), OpenSSL (15 s), and four independent Chrome evidence attempts (90 s each); no HTTP response or rendered state was available. |
be-fast-and-stablevisual-stability | blocked | high | DNS resolved socialregistry.wb.gov.in to 103.38.191.101, but TCP port 443 timed out in curl (10–20 s), OpenSSL (15 s), and four independent Chrome evidence attempts (90 s each); no HTTP response or rendered state was available. |
be-fast-and-stableefficient-main-thread | blocked | high | DNS resolved socialregistry.wb.gov.in to 103.38.191.101, but TCP port 443 timed out in curl (10–20 s), OpenSSL (15 s), and four independent Chrome evidence attempts (90 s each); no HTTP response or rendered state was available. |
be-fast-and-stableefficient-resource-delivery | blocked | high | DNS resolved socialregistry.wb.gov.in to 103.38.191.101, but TCP port 443 timed out in curl (10–20 s), OpenSSL (15 s), and four independent Chrome evidence attempts (90 s each); no HTTP response or rendered state was available. |
be-fast-and-stabletrim-unused-and-duplicate-code | blocked | high | DNS resolved socialregistry.wb.gov.in to 103.38.191.101, but TCP port 443 timed out in curl (10–20 s), OpenSSL (15 s), and four independent Chrome evidence attempts (90 s each); no HTTP response or rendered state was available. |
be-inclusivenames-roles-labels | blocked | high | DNS resolved socialregistry.wb.gov.in to 103.38.191.101, but TCP port 443 timed out in curl (10–20 s), OpenSSL (15 s), and four independent Chrome evidence attempts (90 s each); no HTTP response or rendered state was available. |
be-inclusivesufficient-contrast | blocked | high | DNS resolved socialregistry.wb.gov.in to 103.38.191.101, but TCP port 443 timed out in curl (10–20 s), OpenSSL (15 s), and four independent Chrome evidence attempts (90 s each); no HTTP response or rendered state was available. |
be-inclusivestructure-and-focus | blocked | high | DNS resolved socialregistry.wb.gov.in to 103.38.191.101, but TCP port 443 timed out in curl (10–20 s), OpenSSL (15 s), and four independent Chrome evidence attempts (90 s each); no HTTP response or rendered state was available. |
be-inclusivelegible-text | blocked | high | DNS resolved socialregistry.wb.gov.in to 103.38.191.101, but TCP port 443 timed out in curl (10–20 s), OpenSSL (15 s), and four independent Chrome evidence attempts (90 s each); no HTTP response or rendered state was available. |
be-inclusivezoom-reflow-targets-and-media | blocked | high | DNS resolved socialregistry.wb.gov.in to 103.38.191.101, but TCP port 443 timed out in curl (10–20 s), OpenSSL (15 s), and four independent Chrome evidence attempts (90 s each); no HTTP response or rendered state was available. |
follow-best-practicesno-console-errors | blocked | high | DNS resolved socialregistry.wb.gov.in to 103.38.191.101, but TCP port 443 timed out in curl (10–20 s), OpenSSL (15 s), and four independent Chrome evidence attempts (90 s each); no HTTP response or rendered state was available. |
follow-best-practicessound-document-and-assets | blocked | high | DNS resolved socialregistry.wb.gov.in to 103.38.191.101, but TCP port 443 timed out in curl (10–20 s), OpenSSL (15 s), and four independent Chrome evidence attempts (90 s each); no HTTP response or rendered state was available. |
follow-best-practicesbrowser-platform-hygiene | blocked | high | DNS resolved socialregistry.wb.gov.in to 103.38.191.101, but TCP port 443 timed out in curl (10–20 s), OpenSSL (15 s), and four independent Chrome evidence attempts (90 s each); no HTTP response or rendered state was available. |
be-discoverabletitle-and-description | blocked | high | DNS resolved socialregistry.wb.gov.in to 103.38.191.101, but TCP port 443 timed out in curl (10–20 s), OpenSSL (15 s), and four independent Chrome evidence attempts (90 s each); no HTTP response or rendered state was available. |
be-discoverablecrawlable-and-mobile-friendly | blocked | high | DNS resolved socialregistry.wb.gov.in to 103.38.191.101, but TCP port 443 timed out in curl (10–20 s), OpenSSL (15 s), and four independent Chrome evidence attempts (90 s each); no HTTP response or rendered state was available. |
be-discoverablecanonical-and-indexing-signals | blocked | high | DNS resolved socialregistry.wb.gov.in to 103.38.191.101, but TCP port 443 timed out in curl (10–20 s), OpenSSL (15 s), and four independent Chrome evidence attempts (90 s each); no HTTP response or rendered state was available. |
be-discoverablestructured-and-shareable-metadata | blocked | high | DNS resolved socialregistry.wb.gov.in to 103.38.191.101, but TCP port 443 timed out in curl (10–20 s), OpenSSL (15 s), and four independent Chrome evidence attempts (90 s each); no HTTP response or rendered state was available. |
be-private-and-securesecure-transport-and-headers | blocked | high | DNS resolved socialregistry.wb.gov.in to 103.38.191.101, but TCP port 443 timed out in curl (10–20 s), OpenSSL (15 s), and four independent Chrome evidence attempts (90 s each); no HTTP response or rendered state was available. |
be-private-and-securedata-minimisation-and-third-parties | blocked | high | DNS resolved socialregistry.wb.gov.in to 103.38.191.101, but TCP port 443 timed out in curl (10–20 s), OpenSSL (15 s), and four independent Chrome evidence attempts (90 s each); no HTTP response or rendered state was available. |
be-private-and-securein-context-permissions-and-modern-auth | blocked | high | DNS resolved socialregistry.wb.gov.in to 103.38.191.101, but TCP port 443 timed out in curl (10–20 s), OpenSSL (15 s), and four independent Chrome evidence attempts (90 s each); no HTTP response or rendered state was available. |
be-private-and-securedefensive-browser-policies | blocked | high | DNS resolved socialregistry.wb.gov.in to 103.38.191.101, but TCP port 443 timed out in curl (10–20 s), OpenSSL (15 s), and four independent Chrome evidence attempts (90 s each); no HTTP response or rendered state was available. |
be-resilientprogressive-enhancement | blocked | high | DNS resolved socialregistry.wb.gov.in to 103.38.191.101, but TCP port 443 timed out in curl (10–20 s), OpenSSL (15 s), and four independent Chrome evidence attempts (90 s each); no HTTP response or rendered state was available. |
be-resilientresilient-runtime-behaviour | blocked | high | DNS resolved socialregistry.wb.gov.in to 103.38.191.101, but TCP port 443 timed out in curl (10–20 s), OpenSSL (15 s), and four independent Chrome evidence attempts (90 s each); no HTTP response or rendered state was available. |
be-resilientoffline-and-installable | blocked | high | DNS resolved socialregistry.wb.gov.in to 103.38.191.101, but TCP port 443 timed out in curl (10–20 s), OpenSSL (15 s), and four independent Chrome evidence attempts (90 s each); no HTTP response or rendered state was available. |
be-resilientnetwork-and-http-failure-states | blocked | high | DNS resolved socialregistry.wb.gov.in to 103.38.191.101, but TCP port 443 timed out in curl (10–20 s), OpenSSL (15 s), and four independent Chrome evidence attempts (90 s each); no HTTP response or rendered state was available. |
be-internationalisedlang-dir-and-logical-properties | blocked | high | DNS resolved socialregistry.wb.gov.in to 103.38.191.101, but TCP port 443 timed out in curl (10–20 s), OpenSSL (15 s), and four independent Chrome evidence attempts (90 s each); no HTTP response or rendered state was available. |
be-internationalisedlocale-aware-data | blocked | high | DNS resolved socialregistry.wb.gov.in to 103.38.191.101, but TCP port 443 timed out in curl (10–20 s), OpenSSL (15 s), and four independent Chrome evidence attempts (90 s each); no HTTP response or rendered state was available. |
be-internationalisedtime-zone-correctness | blocked | high | DNS resolved socialregistry.wb.gov.in to 103.38.191.101, but TCP port 443 timed out in curl (10–20 s), OpenSSL (15 s), and four independent Chrome evidence attempts (90 s each); no HTTP response or rendered state was available. |
be-trustworthyno-dark-patterns | blocked | high | DNS resolved socialregistry.wb.gov.in to 103.38.191.101, but TCP port 443 timed out in curl (10–20 s), OpenSSL (15 s), and four independent Chrome evidence attempts (90 s each); no HTTP response or rendered state was available. |
be-trustworthyhumane-error-handling | blocked | high | DNS resolved socialregistry.wb.gov.in to 103.38.191.101, but TCP port 443 timed out in curl (10–20 s), OpenSSL (15 s), and four independent Chrome evidence attempts (90 s each); no HTTP response or rendered state was available. |
be-trustworthytrustworthy-input-assistance | blocked | high | DNS resolved socialregistry.wb.gov.in to 103.38.191.101, but TCP port 443 timed out in curl (10–20 s), OpenSSL (15 s), and four independent Chrome evidence attempts (90 s each); no HTTP response or rendered state was available. |
be-trustworthysafe-commercial-and-account-flows | blocked | high | DNS resolved socialregistry.wb.gov.in to 103.38.191.101, but TCP port 443 timed out in curl (10–20 s), OpenSSL (15 s), and four independent Chrome evidence attempts (90 s each); no HTTP response or rendered state was available. |
be-sustainableoptimised-assets | blocked | high | DNS resolved socialregistry.wb.gov.in to 103.38.191.101, but TCP port 443 timed out in curl (10–20 s), OpenSSL (15 s), and four independent Chrome evidence attempts (90 s each); no HTTP response or rendered state was available. |
be-sustainableno-wasteful-work | blocked | high | DNS resolved socialregistry.wb.gov.in to 103.38.191.101, but TCP port 443 timed out in curl (10–20 s), OpenSSL (15 s), and four independent Chrome evidence attempts (90 s each); no HTTP response or rendered state was available. |
be-sustainablethird-party-and-media-budget | blocked | high | DNS resolved socialregistry.wb.gov.in to 103.38.191.101, but TCP port 443 timed out in curl (10–20 s), OpenSSL (15 s), and four independent Chrome evidence attempts (90 s each); no HTTP response or rendered state was available. |
be-agent-readystructured-agent-capabilities | blocked | high | DNS resolved socialregistry.wb.gov.in to 103.38.191.101, but TCP port 443 timed out in curl (10–20 s), OpenSSL (15 s), and four independent Chrome evidence attempts (90 s each); no HTTP response or rendered state was available. |
be-agent-readyon-device-inference | blocked | high | DNS resolved socialregistry.wb.gov.in to 103.38.191.101, but TCP port 443 timed out in curl (10–20 s), OpenSSL (15 s), and four independent Chrome evidence attempts (90 s each); no HTTP response or rendered state was available. |
be-memory-efficientno-leak-under-repeated-interaction | blocked | high | DNS resolved socialregistry.wb.gov.in to 103.38.191.101, but TCP port 443 timed out in curl (10–20 s), OpenSSL (15 s), and four independent Chrome evidence attempts (90 s each); no HTTP response or rendered state was available. |
be-memory-efficientbounded-footprint | blocked | high | DNS resolved socialregistry.wb.gov.in to 103.38.191.101, but TCP port 443 timed out in curl (10–20 s), OpenSSL (15 s), and four independent Chrome evidence attempts (90 s each); no HTTP response or rendered state was available. |
be-memory-efficientno-detached-dom-or-unbounded-listeners | blocked | high | DNS resolved socialregistry.wb.gov.in to 103.38.191.101, but TCP port 443 timed out in curl (10–20 s), OpenSSL (15 s), and four independent Chrome evidence attempts (90 s each); no HTTP response or rendered state was available. |
Provenance
Canonical report: results/atomic/reports/0493-socialregistry_wb_gov_in.json
Report SHA-256: fcadcb01ffc0fda7e805d27dfadcdd888b7cc29ad39b723631a71626d85fc2d4
Local retained report: runs/2026-07-17T17-27-24-856Z/atomic-reports/socialregistry_wb_gov_in/2026-07-28T00-41-16-227Z/report.json
Local evidence root: runs/2026-07-17T17-27-24-856Z/atomic-reports/socialregistry_wb_gov_in/2026-07-28T00-41-16-227Z
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.