Infrastructure

· 17 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Probed from Sao Paulo, Brazil

403 Forbidden

Checks

4 PASS 10 REVIEW 3 FIX

Multi-Resolver DNS Speed

Action

Mean 1085ms across 3 resolvers (spread 1238ms)

FIX

Mean 1085ms across 3 resolvers (spread 1238ms)

Google: 565ms

Got: 565ms via 8.8.8.8:53

Cloudflare: 888ms

Got: 888ms via 1.1.1.1:53

Quad9: 1803ms

Got: 1803ms via 9.9.9.9:53

High latency spread between resolvers: 1238ms (min 565ms / max 1803ms)

Wide gap between the fastest and slowest public resolver suggests a geographic anycast issue or an authoritative-server cache problem. Users in different regions will see materially different DNS times.

HTTP Probe Timing

Action

Total 4822 ms — DNS, TCP, TLS, TTFB, content transfer breakdown

FIX

DNS Lookup

3.38 s

TCP Connect

302 ms

TLS Handshake

841 ms

Time to First Byte

4.82 s

Total Time

4.82 s

Connection waterfall

DNS Lookup 3.38 s TCP Connect 302 ms TLS Handshake 841 ms Server Processing 304 ms Content Transfer 0 ms

CDN & Delivery

Action

No CDN detected

FIX

No CDN detected

A CDN can significantly improve load times for users around the world by caching content at edge nodes closer to them.

No CDN detected

Consider using a CDN to improve global delivery speed and reduce origin load.

DNS Records

1 A records, 2885 ms lookup

REVIEW

1 A records, 2885 ms lookup

Resolves to 1 IPv4 address(es)

Got: 103.251.43.237

Single A record — no DNS redundancy

Multiple A records provide failover if one server goes down.

No IPv6 (AAAA) records

No NS records found

No MX records — email not configured via DNS

No SPF record found in TXT records

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

DNS resolution is slow (2885 ms)

Slow DNS adds latency to every page load. Consider a faster DNS provider.

Got: 2885 ms

A	103.251.43.237
AAAA	—
CNAME	—
NS	—
MX	—
TXT	—
CAA	Lookup not available with standard resolver

Resolved in 2885 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)

Slow DNS adds latency to every page load. Consider a faster DNS provider.

Why this matters

DNS resolution is slow — anycast DNS providers (Cloudflare, Route 53) typically resolve <50ms globally.

Source: DNS performance benchmarks

DNSSEC

Unsigned (DNSSEC not deployed)

REVIEW

Unsigned (DNSSEC not deployed)

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).

CAA Records

No CAA records (any CA may issue certificates)

REVIEW

No CAA records (any CA may issue certificates)

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.

Reverse DNS

Action

0/1 IPs match cert SAN

REVIEW

0/1 IPs match cert SAN

PTR lookup failed for 103.251.43.237: lookup 103.251.43.237: no such host

No reverse DNS record set for this IP. Common on bare cloud-VM IPs without provider-side PTR; not a security issue.

Redirect Chain

0 redirect(s), 3596 ms total

REVIEW

0 redirect(s), 3596 ms total

Redirect overhead: 3596 ms total

Got: 3596 ms

https://www.keralapsc.gov.in/shortlists

3596 ms · HTTP/1.1 FINAL

#	URL	Status	Time	Protocol	Server
1	https://www.keralapsc.gov.in/shortlists	403	3596 ms	HTTP/1.1	Apache

IPv6 Readiness

Action

No IPv6 support

REVIEW

No IPv6 support

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

Crawlability

no robots.txt, no sitemap

REVIEW

no robots.txt, no sitemap

No robots.txt found

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

No sitemap.xml found

A sitemap helps search engines discover and index your pages more efficiently.

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

A sitemap helps search engines discover and index your pages more efficiently.

Why this matters

No sitemap.xml — Google relies on crawl-graph discovery alone, slowing indexing of deep or fresh URLs.

Learn more ▾

A sitemap accelerates Google's discovery of new and updated content. Most CMSes auto-generate one; static-site frameworks need a build-step plugin. Reference it from robots.txt and submit in Search Console to confirm Google can fetch it.

Source: sitemaps.org / Google Search Central

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 No sitemap found

No sitemap found

Adding a sitemap helps search engines discover your pages.

TLS Certificate Expiry & Recommendations

100 days until leaf cert expires — 4 issues to address

REVIEW

Certificate validity

100

days left

0d 30d 60d 90d+

Recommended actions

Prefer TLS 1.3 — TLS 1.2 is acceptable but TLS 1.3 removes RSA key exchange and improves latency
Enable HSTS: Strict-Transport-Security: max-age=31536000; includeSubDomains
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

CDN Cache Observability

No CDN cache-status headers in the response

REVIEW

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.

Operational Status Page

No status page link detected

REVIEW

No status page link detected

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+

Subdomain Takeover

No subdomain takeover risk detected

PASS

No subdomain takeover risk detected

No CNAME record present

A+

URL Variants

www/non-www, trailing slash, HTTP→HTTPS

PASS

www/non-www, trailing slash, HTTP→HTTPS

HTTP correctly redirects to HTTPS permanently

Got: HTTP 301

www / non-www

200https://www.keralapsc.gov.in/shortlists

403https://keralapsc.gov.in/shortlists

Trailing Slash

403https://www.keralapsc.gov.in/shortlists/

200https://www.keralapsc.gov.in/shortlists

HTTP → HTTPS

301http://www.keralapsc.gov.in/shortlists → https://www.keralapsc.gov.in/shortlists

Consistent

A+

Domain Intelligence

keralapsc.gov.in — via National Informatics Centre, 13 years, 10 months old, hosted on KSITM-AS-AP - KERALA STATE IT MISSION, IN

PASS

keralapsc.gov.in — via National Informatics Centre, 13 years, 10 months old, hosted on KSITM-AS-AP - KERALA STATE IT MISSION, IN

Domain registered until Jan 8, 2027 (4 months remaining)

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.

Registrar: National Informatics Centre

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.

Hosting: KSITM-AS-AP - KERALA STATE IT MISSION, IN

Got: AS133037

Domain expiry

126 days

January 8, 2027

SSL certificate

100 days

Issued by Sectigo Limited

Domain age

13 years, 10 months

Registered January 8, 2013

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

KSITM-AS-AP - KERALA STATE IT MISSION, IN

ASN AS133037

103.251.43.237

Registrar

National Informatics Centre

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
Enable registrar lock (clientTransferProhibited) to block unauthorized domain transfers

Registrar National Informatics Centre

Created January 8, 2013 (13 years, 10 months ago)

Expires January 8, 2027 (4 months)

Last Updated February 22, 2026

Name Servers nsdc1.kerala.gov.in, nsdc2.kerala.gov.in

DNSSEC Not enabled

Hosting

IP Address 103.251.43.237

ASN AS133037 (KSITM-AS-AP - KERALA STATE IT MISSION, IN)

Provider KSITM-AS-AP - KERALA STATE IT MISSION, IN

Data source: rdap (3.0s)

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+

Health Check Endpoint

Auth-protected health endpoint at https://www.keralapsc.gov.in/health (HTTP 403)

PASS

Auth-protected health endpoint at https://www.keralapsc.gov.in/health (HTTP 403)

Auth-protected health endpoint exposed at https://www.keralapsc.gov.in/health

Got: https://www.keralapsc.gov.in/health

All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.