https://dev-shivaninevrekar.pantheonsite.io

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 Madrid, Spain

403 Forbidden

Checks

7 PASS 8 REVIEW 1 FIX

Crawlability

Action

robots.txt present, no sitemap

FIX

robots.txt present, no sitemap

robots.txt is present

Got: 133 bytes

robots.txt blocks all crawlers

Disallow: / for all user-agents prevents search engines from indexing any page. This will remove the site from search results.

No sitemap.xml found

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

robots.txt does not reference a sitemap

Add a 'Sitemap:' directive to robots.txt so search engines can discover your sitemap.

Disallow: / for all user-agents prevents search engines from indexing any page. This will remove the site from search results.

Why this matters

Disallow: / in robots.txt blocks every search crawler — the site becomes invisible in organic search.

Learn more ▾

Common deployment mistake: a staging robots.txt with `User-agent: * / Disallow: /` ships to prod. The site falls out of search results within days. Verify your robots.txt is the production-intended version. If this is intentional (private site), no action needed.

Source: Google Search Central

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

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 133 B Sitemaps referenced 0 User-agents * Blocking Yes — all crawlers blocked

# Pantheon's documentation on robots.txt: http://helpdesk.getpantheon.com/customer/portal/articles/1389628
User-agent: *
Disallow: /

sitemap.xml No sitemap found

No sitemap found

Adding a sitemap helps search engines discover your pages.

DNS Records

1 A records, 34 ms lookup

REVIEW

1 A records, 34 ms lookup

Resolves to 1 IPv4 address(es)

Got: 185.178.196.4

Single A record — no DNS redundancy

Multiple A records provide failover if one server goes down.

Has 1 IPv6 (AAAA) record(s)

Got: 2a0a:6c80::4

CNAME record at zone apex

A CNAME at the zone apex can break MX and NS records. Use ALIAS/ANAME or A records instead.

Got: fe.cfp2p.edge.pantheon.io

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 time: 34 ms

Got: 34 ms

A	185.178.196.4
AAAA	2a0a:6c80::4
CNAME	fe.cfp2p.edge.pantheon.io
NS	—
MX	—
TXT	—
CAA	Lookup not available with standard resolver

Resolved in 34 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

A CNAME at the zone apex can break MX and NS records. Use ALIAS/ANAME or A records instead.

Why this matters

CNAME at the apex (example.com) breaks every other apex record (MX, TXT, NS) — DNS-protocol violation per RFC 1034.

Learn more ▾

RFC 1034 forbids CNAME alongside other records at the same name. Some DNS providers offer ALIAS / ANAME / flattened-CNAME records that work around this — use those instead. Otherwise apex-level CNAME breaks email (no MX), domain ownership verification (no TXT), and more.

Source: RFC 1034

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)

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/2 IPs match cert SAN

REVIEW

0/2 IPs match cert SAN

PTR lookup failed for 185.178.196.4: lookup 185.178.196.4: 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.

PTR lookup failed for 2a0a:6c80::4: lookup 2a0a:6c80::4: 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.

TLS Certificate Expiry & Recommendations

83 days until leaf cert expires — 5 issues to address

REVIEW

Certificate validity

days left

0d 30d 60d 90d+

Recommended actions

Extend HSTS max-age to at least 31536000 (1 year) to meet the preload list criteria
Add includeSubDomains to the HSTS directive
Add the preload directive and submit to hstspreload.org once max-age + includeSubDomains are in place
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 & Delivery

Cloudflare

REVIEW

Cloudflare

Document is served via Cloudflare CDN (edge: CDG)

Got: cf-ray: a3f8f7594ac2ebaa-CDG

Document served via CDN: Cloudflare

Provider Cloudflare Evidence cf-ray: a3f8f7594ac2ebaa-CDG

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

CNAME does not point at a known takeover-able service

A+

Multi-Resolver DNS Speed

Mean 29ms across 3 resolvers (spread 14ms)

PASS

Mean 29ms across 3 resolvers (spread 14ms)

Google: 20ms

Got: 20ms via 8.8.8.8:53

Quad9: 33ms

Got: 33ms via 9.9.9.9:53

Cloudflare: 34ms

Got: 34ms via 1.1.1.1:53

A+

Redirect Chain

0 redirect(s), 66 ms total

PASS

0 redirect(s), 66 ms total

https://dev-shivaninevrekar.pantheonsite...

66 ms · HTTP/1.1 FINAL

#	URL	Status	Time	Protocol	Server
1	https://dev-shivaninevrekar.pantheonsite...	403	66 ms	HTTP/1.1	cloudflare

A+

IPv6 Readiness

IPv6 reachable (17 ms)

PASS

IPv6 reachable (17 ms)

IPv6 is configured and reachable at 2a0a:6c80::4

Got: 17 ms connect

IPv6 Ready

AAAA Records 2a0a:6c80::4 Connection Reachable (17 ms)

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

https://www.dev-shivaninevrekar.pantheonsite.io/

200https://dev-shivaninevrekar.pantheonsite.io/

HTTP → HTTPS

301http://dev-shivaninevrekar.pantheonsite.io/ → https://dev-shivaninevrekar.pantheonsite.io/

Consistent

A+

HTTP Probe Timing

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

PASS

DNS Lookup

46 ms

TCP Connect

17 ms

TLS Handshake

24 ms

Time to First Byte

108 ms

Total Time

108 ms

Connection waterfall

DNS Lookup 46 ms TCP Connect 17 ms TLS Handshake 24 ms Server Processing 22 ms Content Transfer 0 ms

A+

Health Check Endpoint

Auth-protected health endpoint at https://dev-shivaninevrekar.pantheonsite.io/health (HTTP 403)

PASS

Auth-protected health endpoint at https://dev-shivaninevrekar.pantheonsite.io/health (HTTP 403)

Auth-protected health endpoint exposed at https://dev-shivaninevrekar.pantheonsite.io/health

Got: https://dev-shivaninevrekar.pantheonsite.io/health

Domain Intelligence

Domain intelligence data not available

INFO

Domain intelligence data not available

RDAP and WHOIS lookup both failed

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