Skip to content
https://mynewsdesk.com

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
91
GRADE
A
FIX
1
REVIEW
2
PASS
6
INFO
0
Probed from Sao Paulo, Brazil
301 Moved Permanently
Checks
9
6 PASS 2 REVIEW 1 FIX
D
Redirect Chain
Action
2 redirect(s), 1201 ms total
FIX
2 redirect(s), 1201 ms total
Warning::
2 redirects before reaching final URL
Each redirect adds latency. Try to minimize the chain to 1 hop.
Info::
WWW normalization redirect
Info::
Uses 302 (temporary) redirect
If permanent, use 301 instead.
Got: https://www.mynewsdesk.com/
Warning::
Redirect overhead: 1201 ms total
Got: 1201 ms

https://mynewsdesk.com

265 ms · HTTP/1.1

301

https://www.mynewsdesk.com/

675 ms · HTTP/1.1

302

https://www.mynewsdesk.com/en/

262 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://mynewsdesk.com301265 msHTTP/1.1cloudflare
2https://www.mynewsdesk.com/302675 msHTTP/1.1cloudflare
3https://www.mynewsdesk.com/en/200262 msHTTP/1.1cloudflare

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

If permanent, use 301 instead.

Why this matters

302 (Found) is for genuinely temporary redirects — if this redirect is permanent, switch to 301 to preserve SEO equity.

Learn more ▾

Search engines treat 302 as temporary, keeping the original URL indexed and not transferring full link equity to the destination. Use 301 (Moved Permanently) for permanent redirects (HTTP→HTTPS, www-vs-non-www, URL restructures).

Source: Google Search Central

B
TLS Certificate Expiry & Recommendations
64 days until leaf cert expires — 3 issues to address
REVIEW

Certificate validity

64
days left
0d 30d 60d 90d+

Recommended actions

  • 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
B
CDN & Delivery
Cloudflare (EXPIRED)
REVIEW
Cloudflare (EXPIRED)
Info::
Site is served via Cloudflare CDN (edge: GRU)
Got: cf-ray: 9f0094579c85311f-GRU
Info::
CDN cache status: EXPIRED
CDN Detected: Cloudflare
Provider Cloudflare Cache Status EXPIRED Evidence cf-ray: 9f0094579c85311f-GRU
A+
DNS Records
2 A records, 15 ms lookup
PASS
2 A records, 15 ms lookup
Info::
Resolves to 2 IPv4 address(es)
Got: 104.18.27.2, 104.18.26.2
Info::
Has 2 IPv6 (AAAA) record(s)
Got: 2606:4700::6812:1a02, 2606:4700::6812:1b02
Info::
2 nameserver(s) configured
Got: brad.ns.cloudflare.com, nadia.ns.cloudflare.com
Info::
7 mail exchanger(s) configured
Info::
CAA records not checked
CAA record lookup requires a specialized DNS resolver. This check will be available in a future update.
Info::
SPF record present in TXT
Info::
DNS resolution time: 15 ms
Got: 15 ms
A104.18.27.2, 104.18.26.2
AAAA2606:4700::6812:1a02, 2606:4700::6812:1b02
CNAME—
NSbrad.ns.cloudflare.com, nadia.ns.cloudflare.com
MX
10 aspmx.l.google.com
20 alt1.aspmx.l.google.com
20 alt2.aspmx.l.google.com
30 aspmx2.googlemail.com
30 aspmx5.googlemail.com
30 aspmx4.googlemail.com
30 aspmx3.googlemail.com
TXT
Ticket ID - 336357
anthropic-domain-verification-kqg30s=r23Bztnc5cCVZq3RHiYHkOCO8
apple-domain-verification=ZB2Q0OOAMl8UxL86
atlassian-domain-verification=/ejansBhdJkD4t1ylv4ayrQf2mAwyguNTzmVi8k01BAS4G1Ios...
cursor-domain-verification-3dne4v=MSZLO2lwKiPbgHdIG2mRreSt3
facebook-domain-verification=1fx1tc1o3pqpfl88dkxoqohpe2r664
google-site-verification=8oXwUmUQoVBhkihuWOkKdiY4Fls8o3ISsz_wkXrLcnI
google-site-verification=F7FFQiYpmrz1eGfPgQkMBtqfiqKVFVXy-U4njYdPSW0
google-site-verification=L8raoV5pGJiyfKKvtVHFnN8wEFbqsa4nhB5Sz6A7-fA
google-site-verification=QN-5Vuxsiv3zEOZHe6mWm8aRwuEjSSvpYSV0licReaM
google-site-verification=Y568cad10wB5XxtLGUGgei8h2QxmyYX_IUGb7FOTibM
google-site-verification=mF2hWEhSoKaJv-milTWMhIJ8N8mj_1hIdI7vX4tCkkE
google-site-verification=q6RwvWT_J9gN6MndOKsUchYMZAm1XSmKlyqh0u7E2Zw
google-site-verification=szINrytg-kU81iKOYQd83F9ntjLzeiJzJzhYeEWtQo8
heroku-mynewsdesk
hj= 181931-08042021
miro-verification=f4e6672c9f5c77821d91ff177ded78b29d68e26f
status-page-domain-verification=d7n589s718qb
SPF v=spf1 include:_spf.google.com include:sendgrid.net include:5540930.spf08.hubspo...
CAALookup not available with standard resolver
Resolved in 15 ms

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+
IPv6 Readiness
IPv6 reachable (1 ms)
PASS
IPv6 reachable (1 ms)
Info::
IPv6 is configured and reachable at 2606:4700::6812:1a02, 2606:4700::6812:1b02
Got: 1 ms connect
IPv6 Ready
AAAA Records 2606:4700::6812:1a02, 2606:4700::6812:1b02 Connection Reachable (1 ms)
A+
Crawlability
robots.txt present, sitemap with 336 URLs
PASS
robots.txt present, sitemap with 336 URLs
Info::
robots.txt is present
Got: 275 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 336 entries
Info::
Sitemap index with 336 child sitemaps
Info::
robots.txt references sitemap
robots.txt 200 OK
Size 275 B Sitemaps referenced 4 User-agents * Blocking No — crawling allowed
Sitemap: https://sitemaps.mynewsdesk.com/sitemap.xml
Sitemap: https://www.mynewsdesk.com/post-sitemap.xml
Sitemap: https://www.mynewsdesk.com/page-sitemap.xml
Sitemap: https://www.mynewsdesk.com/customer_case-sitemap.xml
User-agent: *
Disallow: /analytics/
Disallow: /*.pdf$
sitemap.xml 200 OK
Type Sitemap Index URLs 336 entries Valid XML Yes
Child Sitemaps:
A+
URL Variants
www/non-www, trailing slash, HTTP→HTTPS
PASS
www/non-www, trailing slash, HTTP→HTTPS
Info::
www/non-www redirect configured correctly (preferred: non-www)
Info::
HTTP correctly 301-redirects to HTTPS

www / non-www

302https://www.mynewsdesk.com/
200https://mynewsdesk.com/

Preferred variant: non-www

HTTP → HTTPS

301http://mynewsdesk.com/ → https://mynewsdesk.com/

Consistent

A+
Domain Intelligence
mynewsdesk.com — via 1API GmbH, 18 years, 5 months old
PASS
mynewsdesk.com — via 1API GmbH, 18 years, 5 months old
Info::
Domain registered until Feb 19, 2027 (10 months remaining)
Info::
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.
Info::
Registrar: 1API GmbH
Warning::
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.
Domain expiry

216 days

February 19, 2027

SSL certificate

64 days

Issued by Let's Encrypt

Domain age

18 years, 5 months

Registered February 19, 2008

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

Unknown

2606:4700::6812:1a02

Registrar

1API GmbH

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 1API GmbH
Created February 19, 2008 (18 years, 5 months ago)
Expires February 19, 2027 (10 months)
Last Updated February 14, 2026
Name Servers brad.ns.cloudflare.com, nadia.ns.cloudflare.com
DNSSEC Not enabled
Hosting
IP Address 2606:4700::6812:1a02
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 276 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
PASS
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
11 ms
TCP Connect TCP Connect — time to establish a TCP connection to the server.
2 ms
TLS Handshake TLS Handshake — time to complete the HTTPS encryption handshake.
13 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
277 ms
Total Time Total request time from DNS lookup through full response.
277 ms

Connection waterfall

DNS Lookup 11 ms TCP Connect 2 ms TLS Handshake 13 ms Server Processing 251 ms Content Transfer 0 ms
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback