Infrastructure - https://tribuneindia.com BeaverCheck Audit

D

Redirect Chain

Action

2 redirect(s), 1840 ms total

FIX

2 redirect(s), 1840 ms total

2 redirects before reaching final URL

Each redirect adds latency. Try to minimize the chain to 1 hop.

HTTP to HTTPS redirect present

WWW normalization redirect

2-hop chain could be reduced to 1 hop

Redirect directly from https://tribuneindia.com to https://www.tribuneindia.com:443/

Redirect overhead: 1840 ms total

Got: 1840 ms

https://tribuneindia.com

381 ms · HTTP/1.1

301

http://www.tribuneindia.com/

11 ms · HTTP/1.1

301

https://www.tribuneindia.com:443/

1449 ms · HTTP/1.1 FINAL

#	URL	Status	Time	Protocol	Server
1	https://tribuneindia.com	301	381 ms	HTTP/1.1	nginx
2	http://www.tribuneindia.com/	301	11 ms	HTTP/1.1
3	https://www.tribuneindia.com:443/	200	1449 ms	HTTP/1.1	nginx

See the visual redirect chain in the HTTP Probe tab →

Each redirect adds latency. Try to minimize the chain to 1 hop.

Why this matters

Redirect chain — each hop adds latency; combine into one redirect where possible.

Source: Google Search Central / web.dev

Redirect directly from https://tribuneindia.com to https://www.tribuneindia.com:443/

Why this matters

Redirect chain could be flattened to one hop — server config tweak removes intermediate latency.

Source: web.dev

C

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

B

URL Variants

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

REVIEW

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

Both www and non-www versions serve content

Got: Both variants return 200 Expected: One variant 301-redirects to the other

HTTP correctly 301-redirects to HTTPS

www / non-www

200https://www.tribuneindia.com/

200https://tribuneindia.com/

Inconsistent — duplicate content risk

HTTP → HTTPS

301http://tribuneindia.com/ → https://tribuneindia.com:443/

Consistent

B

TLS Certificate Expiry & Recommendations

40 days until leaf cert expires — 3 issues to address

REVIEW

Certificate validity

40

days left

0d 30d 60d 90d+

Recommended actions

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

B

CDN & Delivery

Google Cloud CDN

REVIEW

Google Cloud CDN

Site is served via Google Cloud CDN CDN

Got: via: 1.1 google

CDN Detected: Google Cloud CDN

Provider Google Cloud CDN Evidence via: 1.1 google

A+

DNS Records

1 A records, 15 ms lookup

PASS

1 A records, 15 ms lookup

Resolves to 1 IPv4 address(es)

Got: 34.160.67.217

Single A record — no DNS redundancy

Multiple A records provide failover if one server goes down.

No IPv6 (AAAA) records

4 nameserver(s) configured

Got: ns-1160.awsdns-17.org, ns-17.awsdns-02.com, ns-1722.awsdns-23.co.uk, ns-592.awsdns-10.net

5 mail exchanger(s) configured

CAA records not checked

CAA record lookup requires a specialized DNS resolver. This check will be available in a future update.

SPF record present in TXT

DNS resolution time: 15 ms

Got: 15 ms

A	34.160.67.217
AAAA	—
CNAME	—
NS	ns-1160.awsdns-17.org, ns-17.awsdns-02.com, ns-1722.awsdns-23.co.uk, ns-592.awsdns-10.net
MX	10 aspmx.l.google.com 20 alt1.aspmx.l.google.com 30 alt2.aspmx.l.google.com 40 aspmx2.googlemail.com 50 aspmx3.googlemail.com
TXT	google-site-verification=xMCpu2K7FbpAQhrXl-ahCTryApH01Dj9HMs5ynZgUo8 SPF v=spf1 include:_spf.google.com ~all
CAA	Lookup not available with standard resolver

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

CAA record lookup requires a specialized DNS resolver. This check will be available in a future update.

Why this matters

Informational: CAA (Certification Authority Authorization) records weren't checked in this scan.

A+

Crawlability

robots.txt present, sitemap with 38 URLs

PASS

robots.txt present, sitemap with 38 URLs

robots.txt is present

Got: 186 bytes

sitemap.xml is present

sitemap.xml is valid XML

sitemap.xml contains 38 entries

Sitemap index with 38 child sitemaps

robots.txt references sitemap

robots.txt 200 OK

Size 186 B Sitemaps referenced 1 User-agents * Blocking No — crawling allowed

User-agent: *
Allow: /
Sitemap: https://www.tribuneindia.com/sitemap.xml
Sitemap : https://www.tribuneindia.com/sitemap-news.xml
Sitemap : https://www.tribuneindia.com/recent-sitemap.xml

sitemap.xml 200 OK

Type Sitemap Index URLs 38 entries Valid XML Yes

Child Sitemaps:

A+

Domain Intelligence

tribuneindia.com — via GoDaddy.com, LLC, 29 years, 3 months old, hosted on Google Cloud

PASS

tribuneindia.com — via GoDaddy.com, LLC, 29 years, 3 months old, hosted on Google Cloud

Domain registered until May 28, 2028 (2 years, 1 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: GoDaddy.com, LLC

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: Google Cloud

Got: AS396982

Domain expiry

712 days

May 28, 2028

SSL certificate

40 days

Issued by Google Trust Services

Domain age

29 years, 3 months

Registered May 29, 1997

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

Google Cloud

ASN AS396982

34.160.67.217

Registrar

GoDaddy.com, LLC

Unlocked 4 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 GoDaddy.com, LLC

Created May 29, 1997 (29 years, 3 months ago)

Expires May 28, 2028 (2 years, 1 months)

Last Updated September 30, 2024

Name Servers ns-1160.awsdns-17.org, ns-17.awsdns-02.com, ns-1722.awsdns-23.co.uk, ns-592.awsdns-10.net

DNSSEC Not enabled

Hosting

IP Address 34.160.67.217

ASN AS396982 (GOOGLE-CLOUD-PLATFORM - Google LLC, US)

Provider Google Cloud

Data source: rdap (0.4s)

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+

HTTP Probe Timing

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

PASS

DNS Lookup

7 ms

TCP Connect

2 ms

TLS Handshake

12 ms

Time to First Byte

373 ms

Total Time

373 ms

Connection waterfall

DNS Lookup 7 ms TCP Connect 2 ms TLS Handshake 12 ms Server Processing 352 ms Content Transfer 0 ms