Skip to content
https://softpedia.com

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
84
GRADE
B
FIX
1
REVIEW
4
PASS
4
INFO
0
Probed from Madrid, Spain
301 Moved Permanently
Checks
9
4 PASS 4 REVIEW 1 FIX
D
CDN & Delivery
Action
No CDN detected
FIX
No CDN detected
Warning::
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.

C
IPv6 Readiness
Action
No IPv6 support
REVIEW
No IPv6 support
Info::
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
Crawlability
robots.txt present, no sitemap
REVIEW
robots.txt present, no sitemap
Info::
robots.txt is present
Got: 1466 bytes
Info::
No sitemap.xml found
A sitemap helps search engines discover and index your pages more efficiently.
Info::
robots.txt does not reference a sitemap
Add a 'Sitemap:' directive to robots.txt so search engines can discover your sitemap.

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 1466 B Sitemaps referenced 0 User-agents Google-Site-Verification, QuerySeekerSpider, MauiBot, GPTBot, Bytespider, Flamingo_SearchEngine, Vegi bot, demandbase-bot, DemandbasePublisherAnalyzer, DataForSeoBot, Buck, Adsbot-Google, *, NING, Cliqzbot, Mediapartners-Google, GrapeshotCrawler, GermCrawler, PetalBot, CCBot, TweetmemeBot, trendkite-akashic-crawler, BLEXBot, PerplexityBot, SputnikBot, YaK, bingbot, Amazonbot, SeekportBot, GoogleOther, AmazonAdBot, ClaudeBot, PaperLiBot Blocking No — crawling allowed
User-agent: Mediapartners-Google
Disallow:

User-agent: Google-Site-Verification
Disallow:

User-agent: Adsbot-Google
Disallow:

User-Agent: GoogleOther
Disallow:

User-Agent: AmazonAdBot
Disallow:

User-agent: *
Disallow: /dyn-search.php
Disallow: /xpubcid.php
Disallow: /rsst/
Disallow: /_xaja/dltrk.php
Disallow: /_xaja/nrtrk.php
Disallow: /zd.php
Disallow: /yd.php
Disallow: /cgi-bin/
Disallow: /addineyeV2.html
Disallow: /DARTIframe.html
Disallow: /doubleclick

User-agent: bingbot
Crawl-delay: 2

User-agent: GPTBot
Disallow: /

User-agent: PerplexityBot
Disallow: /

User-Agent: Bytespider
Disallow: /

User-Agent: Amazonbot
Disallow: /

User-agent: ClaudeBot
Disallow: /

User-agent: CCBot
Disallow: /

User-agent: TweetmemeBot
Disallow: /

User-agent: QuerySeekerSpider
Disallow: /

User-Agent: NING
Disallow: /

User-Agent: SputnikBot
Disallow: /

User-Agent: Cliqzbot
Disallow: /

User-Agent: Flamingo_SearchEngine
Disallow: /

User-Agent: Vegi bot
Disallow: /

User-Agent: demandbase-bot
Disallow: /

User-Agent: trendkite-akashic-crawler
Disallow: /

User-Agent: DemandbasePublisherAnalyzer
Disallow: /

User-Agent: GrapeshotCrawler
Disallow: /

User-Agent: YaK
Disallow: /

User-Agent: MauiBot
Disallow: /

User-Agent: GermCrawler
Disallow: /

User-Agent: PaperLiBot
Disallow: /

User-agent: BLEXBot
Disallow: /

User-agent: PetalBot
Disallow: /

User-agent: DataForSeoBot
Disallow: /

User-Agent: Buck
Disallow: /

User-Agent: SeekportBot
Disallow: /

sitemap.xml No sitemap found

No sitemap found

Adding a sitemap helps search engines discover your pages.

B
URL Variants
www/non-www, trailing slash, HTTP→HTTPS
REVIEW
www/non-www, trailing slash, HTTP→HTTPS
Critical::
Both www and non-www versions serve content
Got: Both variants return 200 Expected: One variant 301-redirects to the other
Info::
HTTP correctly 301-redirects to HTTPS

www / non-www

200https://www.softpedia.com/
200https://softpedia.com/

Inconsistent — duplicate content risk

HTTP → HTTPS

301http://softpedia.com/ https://www.softpedia.com/

Consistent

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

Certificate validity

31
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
A+
DNS Records
2 A records, 64 ms lookup
PASS
2 A records, 64 ms lookup
Info::
Resolves to 2 IPv4 address(es)
Got: 64.77.16.72, 64.77.16.71
Info::
No IPv6 (AAAA) records
Info::
4 nameserver(s) configured
Got: ns3.softpedia.com, ns2.softpedia.com, ns1.softpedia.com, ns.softpedia.com
Info::
3 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: 64 ms
Got: 64 ms
A64.77.16.72, 64.77.16.71
AAAA
CNAME
NSns3.softpedia.com, ns2.softpedia.com, ns1.softpedia.com, ns.softpedia.com
MX
10 mail.softpedia.com
20 mail2.softpedia.com
30 mail3.softpedia.com
TXT
SPF v=spf1 mx ip4:64.77.16.0/24 ip4:146.70.213.128/27 ~all
google-site-verification=Y79HW-hv5jdxyGwOtNOAB9bbMNs1hhtpnNt_7_uj9_A
facebook-domain-verification=xfn1ms3ix6q4jtljsd2mzajgxa0pa6
brave-ledger-verification=a9034d4121db7aee0036170e2b5c90a2c24444541795b55b890f71...
google-site-verification: Trb8bEfK5IlEwxTm7zbUvWO3SiS42DP8t9hZGdv1eqc
CAALookup not available with standard resolver
Resolved in 64 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
Redirect Chain
1 redirect(s), 985 ms total
PASS
1 redirect(s), 985 ms total
Info::
Single redirect
Got: https://softpedia.com → https://www.softpedia.com/ (301)
Info::
WWW normalization redirect
Info::
Redirect overhead: 985 ms total
Got: 985 ms

https://softpedia.com

443 ms · HTTP/1.1

301

https://www.softpedia.com/

542 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://softpedia.com301443 msHTTP/1.1Apache
2https://www.softpedia.com/200542 msHTTP/1.1cloudflare

See the visual redirect chain in the HTTP Probe tab →

A+
Domain Intelligence
softpedia.com — via Instra Corporation Pty Ltd., 23 years, 2 months old, hosted on COGECO-PEER1 - Aptum Technologies, CA
PASS
softpedia.com — via Instra Corporation Pty Ltd., 23 years, 2 months old, hosted on COGECO-PEER1 - Aptum Technologies, CA
Info::
Domain registered until Jun 19, 2028 (2 years, 2 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: Instra Corporation Pty Ltd.
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.
Info::
Hosting: COGECO-PEER1 - Aptum Technologies, CA
Got: AS13768
Domain expiry

734 days

June 19, 2028

SSL certificate

31 days

Issued by Sectigo Limited

Domain age

23 years, 2 months

Registered June 19, 2003

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

COGECO-PEER1 - Aptum Technologies, CA

ASN AS13768

64.77.16.71

Registrar

Instra Corporation Pty Ltd.

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 Instra Corporation Pty Ltd.
Created June 19, 2003 (23 years, 2 months ago)
Expires June 19, 2028 (2 years, 2 months)
Last Updated November 23, 2025
Name Servers ns.softpedia.com, ns1.softpedia.com, ns2.softpedia.com, ns3.softpedia.com
DNSSEC Not enabled
Hosting
IP Address 64.77.16.71
ASN AS13768 (COGECO-PEER1 - Aptum Technologies, CA)
Provider COGECO-PEER1 - Aptum Technologies, CA
Data source: rdap (0.3s)

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 506 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
PASS
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
64 ms
TCP Connect TCP Connect — time to establish a TCP connection to the server.
109 ms
TLS Handshake TLS Handshake — time to complete the HTTPS encryption handshake.
224 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
506 ms
Total Time Total request time from DNS lookup through full response.
506 ms

Connection waterfall

DNS Lookup 64 ms TCP Connect 109 ms TLS Handshake 224 ms Server Processing 110 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