Skip to content
https://techopedia.com

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
94
GRADE
A
FIX
0
REVIEW
3
PASS
6
INFO
0
Probed from Sao Paulo, Brazil
301 Moved Permanently
Checks
9
6 PASS 3 REVIEW
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.techopedia.com/
200https://techopedia.com/

Inconsistent — duplicate content risk

HTTP → HTTPS

301http://techopedia.com/ https://techopedia.com/

Consistent

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

Certificate validity

48
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
Cloudflare
REVIEW
Cloudflare
Info::
Site is served via Cloudflare CDN (edge: GRU)
Got: cf-ray: 9eff986cfdc93b9a-GRU
CDN Detected: Cloudflare
Provider Cloudflare Evidence cf-ray: 9eff986cfdc93b9a-GRU
A+
DNS Records
2 A records, 13 ms lookup
PASS
2 A records, 13 ms lookup
Info::
Resolves to 2 IPv4 address(es)
Got: 172.66.163.8, 104.20.44.33
Info::
Has 2 IPv6 (AAAA) record(s)
Got: 2606:4700:10::6814:2c21, 2606:4700:10::ac42:a308
Info::
2 nameserver(s) configured
Got: jaziel.ns.cloudflare.com, rosa.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: 13 ms
Got: 13 ms
A172.66.163.8, 104.20.44.33
AAAA2606:4700:10::6814:2c21, 2606:4700:10::ac42:a308
CNAME
NSjaziel.ns.cloudflare.com, rosa.ns.cloudflare.com
MX
10 aspmx.l.google.com
20 alt1.aspmx.l.google.com
20 alt2.aspmx.l.google.com
30 aspmx3.googlemail.com
30 aspmx5.googlemail.com
30 aspmx4.googlemail.com
30 aspmx2.googlemail.com
TXT
google-site-verification=vpI3F3IkOUE5TmVbtFNCuuDNpI1aMwAH4K8C4IfAeIs
SPF v=spf1 mx ip4:34.217.21.192/32 ip4:34.217.225.71/32 ip4:34.217.124.69/32 ip4:66....
CAALookup not available with standard resolver
Resolved in 13 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), 837 ms total
PASS
1 redirect(s), 837 ms total
Info::
Single redirect
Got: https://techopedia.com → https://www.techopedia.com/ (301)
Info::
WWW normalization redirect
Info::
Redirect overhead: 837 ms total
Got: 837 ms

https://techopedia.com

56 ms · HTTP/1.1

301

https://www.techopedia.com/

781 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://techopedia.com30156 msHTTP/1.1cloudflare
2https://www.techopedia.com/200781 msHTTP/1.1cloudflare

See the visual redirect chain in the HTTP Probe tab →

A+
IPv6 Readiness
IPv6 reachable (1 ms)
PASS
IPv6 reachable (1 ms)
Info::
IPv6 is configured and reachable at 2606:4700:10::6814:2c21, 2606:4700:10::ac42:a308
Got: 1 ms connect
IPv6 Ready
AAAA Records 2606:4700:10::6814:2c21, 2606:4700:10::ac42:a308 Connection Reachable (1 ms)
A+
Crawlability
robots.txt present, sitemap with 27 URLs
PASS
robots.txt present, sitemap with 27 URLs
Info::
robots.txt is present
Got: 1023 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 27 entries
Info::
Sitemap index with 27 child sitemaps
Info::
robots.txt references sitemap
robots.txt 200 OK
Size 1023 B Sitemaps referenced 1 User-agents Mozilla/5.0 (compatible; Qwantify/; +https://www.qwant.com/), *, Yeti, NaverBot Blocking No — crawling allowed
# This virtual robots.txt file was created by the Virtual Robots.txt WordPress plugin: https://www.wordpress.org/plugins/pc-robotstxt/
User-agent: *


Allow: /wp-admin/admin-ajax.php

Allow: /wp-includes/js/

Allow: /wp-includes/images/


Disallow: /wp-admin/

Disallow: /wp-includes/

Disallow: /trackback/

Disallow: /wp-login.php

Disallow: /wp-register.php

Disallow: /extrafiles/

Disallow: /userarea/

Disallow: /search/

Disallow: /companies/

Disallow: /partners/

Disallow: /gulpfile.js

Disallow: /package.json

Disallow: /log4net.config

Disallow: /packages.config

Disallow: /account/

Disallow: /preview/

Disallow: /about/contact/3/

Disallow: */visit/*


Sitemap: https://www.techopedia.com/sitemap_index.xml


# Yeti

User-agent: Yeti

Allow: /


# NaverBot

User-agent: NaverBot

Allow: /


#DaumWebMasterTool:e67bfc59694ecca0a675be084c0f799be8c89503967cde61c6e118d22559cb59:xw8wyXlVS2zgXx/N3Kgy4w==


# Qwantify

User-agent: Mozilla/5.0 (compatible; Qwantify/; +https://www.qwant.com/)

Disallow: /
A+
Domain Intelligence
techopedia.com — via SafeNames Ltd., 23 years, 4 months old
PASS
techopedia.com — via SafeNames Ltd., 23 years, 4 months old
Info::
Domain registered until Apr 7, 2030 (4 years 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: SafeNames 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.
Domain expiry

1360 days

April 7, 2030

SSL certificate

48 days

Issued by Google Trust Services

Domain age

23 years, 4 months

Registered April 7, 2003

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

Unknown

2606:4700:10::ac42:a308

Registrar

SafeNames Ltd.

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 SafeNames Ltd.
Created April 7, 2003 (23 years, 4 months ago)
Expires April 7, 2030 (4 years)
Last Updated September 25, 2025
Name Servers jaziel.ns.cloudflare.com, rosa.ns.cloudflare.com
DNSSEC Not enabled
Hosting
IP Address 2606:4700:10::ac42:a308
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 58 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
PASS
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
14 ms
TCP Connect TCP Connect — time to establish a TCP connection to the server.
1 ms
TLS Handshake TLS Handshake — time to complete the HTTPS encryption handshake.
8 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
58 ms
Total Time Total request time from DNS lookup through full response.
58 ms

Connection waterfall

DNS Lookup 14 ms TCP Connect 1 ms TLS Handshake 8 ms Server Processing 35 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