Infrastructure
· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.BRedirect Chain1 redirect(s), 1024 ms totalREVIEW
https://securityweek.com
778 ms · HTTP/1.1
https://www.securityweek.com/
246 ms · HTTP/1.1 FINAL
| # | URL | Status | Time | Protocol | Server |
|---|---|---|---|---|---|
| 1 | https://securityweek.com | 301 | 778 ms | HTTP/1.1 | cloudflare |
| 2 | https://www.securityweek.com/ | 200 | 246 ms | HTTP/1.1 | cloudflare |
See the visual redirect chain in the HTTP Probe tab →
BURL Variantswww/non-www, trailing slash, HTTP→HTTPSREVIEW
www / non-www
Inconsistent — duplicate content risk
HTTP → HTTPS
Consistent
BTLS Certificate Expiry & Recommendations43 days until leaf cert expires — 2 issues to addressREVIEW
Certificate validity
Recommended actions
- Enable HSTS: Strict-Transport-Security: max-age=31536000; includeSubDomains
- Enable OCSP stapling on your TLS server to remove a CA roundtrip and protect user privacy
A+DNS Records3 A records, 7 ms lookupPASS
| A | 104.24.160.3, 104.24.161.3, 172.67.97.169 |
| AAAA | 2606:4700:20::6818:a003, 2606:4700:20::6818:a103, 2606:4700:20::ac43:61a9 |
| CNAME | — |
| NS | lee.ns.cloudflare.com, roxy.ns.cloudflare.com |
| MX | 1 aspmx.l.google.com 5 alt2.aspmx.l.google.com 5 alt1.aspmx.l.google.com 10 aspmx3.googlemail.com 10 aspmx2.googlemail.com |
| TXT | include:5319632.spf05.hubspotemail.net SPF v=spf1 include:_spf.securityweek_com._d.easydmarc.pro ~all v=DKIM1; k=rsa; p=MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQCVg2TBbq6dmfhS1HCRb0O3vE... |
| CAA | Lookup not available with standard resolver |
CAA record lookup requires a specialized DNS resolver. This check will be available in a future update.
Informational: CAA (Certification Authority Authorization) records weren't checked in this scan.
A+IPv6 ReadinessIPv6 reachable (2 ms)PASS
A+Crawlabilityrobots.txt present, sitemap with 41 URLsPASS
User-agent: *
Allow: /
Disallow: /trackback/
Disallow: /wp-admin/
Disallow: /wp-includes/
Disallow: /xmlrpc.php
Disallow: /cgi-bin
Disallow: /readme.html
Disallow: /license.txt
Disallow: /*?*
Disallow: /*.js$
Disallow: /*.inc$
Disallow: /*.css$
Disallow: /*.gz$
Disallow: /*.wmv$
Disallow: /*.cgi$
Disallow: /*.xhtml$
Disallow: /*/wp-*
Disallow: /*/*.js$
Disallow: /*/*.inc$
Allow: /wp-content/uploads/
Sitemap: http://www.securityweek.com/sitemap.xml
- https://www.securityweek.com/post-sitema...
- https://www.securityweek.com/post-sitema...
- https://www.securityweek.com/post-sitema...
- https://www.securityweek.com/post-sitema...
- https://www.securityweek.com/post-sitema...
- https://www.securityweek.com/post-sitema...
- https://www.securityweek.com/post-sitema...
- https://www.securityweek.com/post-sitema...
- https://www.securityweek.com/post-sitema...
- https://www.securityweek.com/post-sitema...
- https://www.securityweek.com/post-sitema...
- https://www.securityweek.com/post-sitema...
- https://www.securityweek.com/post-sitema...
- https://www.securityweek.com/post-sitema...
- https://www.securityweek.com/post-sitema...
- https://www.securityweek.com/post-sitema...
- https://www.securityweek.com/post-sitema...
- https://www.securityweek.com/post-sitema...
- https://www.securityweek.com/post-sitema...
- https://www.securityweek.com/post-sitema...
- https://www.securityweek.com/post-sitema...
- https://www.securityweek.com/post-sitema...
- https://www.securityweek.com/post-sitema...
- https://www.securityweek.com/post-sitema...
- https://www.securityweek.com/post-sitema...
- https://www.securityweek.com/post-sitema...
- https://www.securityweek.com/post-sitema...
- https://www.securityweek.com/post-sitema...
- https://www.securityweek.com/post-sitema...
- https://www.securityweek.com/post-sitema...
- https://www.securityweek.com/post-sitema...
- https://www.securityweek.com/post-sitema...
- https://www.securityweek.com/post-sitema...
- https://www.securityweek.com/post-sitema...
- https://www.securityweek.com/page-sitema...
- https://www.securityweek.com/category-si...
- https://www.securityweek.com/post_tag-si...
- https://www.securityweek.com/post_tag-si...
- https://www.securityweek.com/post_tag-si...
- https://www.securityweek.com/post_tag-si...
- https://www.securityweek.com/author-site...
A+Domain Intelligencesecurityweek.com — via GoDaddy.com, LLC, 24 years, 5 months oldPASS
3173 days
March 21, 2035
43 days
Issued by Let's Encrypt
24 years, 5 months
Registered March 21, 2002
Enabled
Protects against DNS spoofing
Unknown
2606:4700:20::6818:a003
GoDaddy.com, LLC
Expiry timeline
Recommended actions
- Enable registrar lock (clientTransferProhibited) to block unauthorized domain transfers
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.
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