Skip to content
https://malwarebytes.com

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
81
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.

B
Redirect Chain
1 redirect(s), 2660 ms total
REVIEW
1 redirect(s), 2660 ms total
Info::
Single redirect
Got: https://malwarebytes.com → https://www.malwarebytes.com (301)
Info::
WWW normalization redirect
Warning::
Redirect overhead: 2660 ms total
Got: 2660 ms

https://malwarebytes.com

6 ms · HTTP/1.1

301

https://www.malwarebytes.com

2654 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://malwarebytes.com3016 msHTTP/1.1nginx
2https://www.malwarebytes.com2002654 msHTTP/1.1nginx

See the visual redirect chain in the HTTP Probe tab →

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
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.malwarebytes.com/
200https://malwarebytes.com/

Inconsistent — duplicate content risk

HTTP → HTTPS

301http://malwarebytes.com/ https://malwarebytes.com/

Consistent

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

Certificate validity

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

Recommended actions

  • Add includeSubDomains to the HSTS directive
  • Add the preload directive and submit to hstspreload.org once max-age + includeSubDomains are in place
  • Enable OCSP stapling on your TLS server to remove a CA roundtrip and protect user privacy
A+
DNS Records
1 A records, 63 ms lookup
PASS
1 A records, 63 ms lookup
Info::
Resolves to 1 IPv4 address(es)
Got: 192.0.66.233
Info::
Single A record — no DNS redundancy
Multiple A records provide failover if one server goes down.
Info::
No IPv6 (AAAA) records
Info::
4 nameserver(s) configured
Got: ns-1684.awsdns-18.co.uk, ns-1123.awsdns-12.org, ns-202.awsdns-25.com, ns-914.awsdns-50.net
Info::
1 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: 63 ms
Got: 63 ms
A192.0.66.233
AAAA
CNAME
NSns-1684.awsdns-18.co.uk, ns-1123.awsdns-12.org, ns-202.awsdns-25.com, ns-914.awsdns-50.net
MX
0 malwarebytes-com.mail.protection.outlook.com
TXT
h1-domain-verification=XSPr8ZX1NjiVXff9E3aCmWNmw7t9Kk4nZaEd3hGkjoxqB3dQ
adobe-idp-site-verification=046136e12b20b6a648e63fdc548b5732c52ded8ba2466cb950f6...
rippling-domain-verification=0f54b9602224f399
pendo-domain-verification=dhEbuTQlkGkKxFCdC1VpJkqsPkI
atlassian-domain-verification=d2E1tHpaX3rkDXq5+ZlZyEo1GPjuo23hvyVq/WUG3xbU92gNX2...
anthropic-domain-verification-cpypz4=t0STeocBrJ4QjCzam3Zsomj9U
spycloud-domain-verification=9834e4f8-e7ee-4cee-a35a-a731c70acecc
docusign=5bdadb4b-5cf8-4ed7-bde6-07ed3c06b337
y5fzkwz9y8wwsnjnywq5t90f503zcntk
yandex-verification: 2591bba93ba202da
openai-domain-verification=dv-SZcqGxi7Z98mZ9XPg3KrFpjQ
amazonses:Dp3Q+oLMlCeqgtaqYfxWrx2aTghDqtWPX7+bHwXXjHw=
MS=ms24598734
miro-verification=262ec37f2f74a0cc84954088b958c57dea890d58
apple-domain-verification=3MaCkk39tqqEiKOh
SPF v=spf1 include:spf1.malwarebytes.com include:clients.cleverbridge.com include:sp...
jamf-site-verification=tui5K1JGxQdWgOCN2w1CNQ
hj-ownership=kAivaWbbgy2W2xA2qKLh
CAALookup not available with standard resolver
Resolved in 63 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 10 URLs
PASS
robots.txt present, sitemap with 10 URLs
Info::
robots.txt is present
Got: 1816 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 10 entries
Info::
Sitemap index with 10 child sitemaps
Info::
robots.txt references sitemap
robots.txt 200 OK
Size 1816 B Sitemaps referenced 10 User-agents bingbot, OAI-SearchBot, ClaudeBot, *, GPTBot, GeminiBot, Googlebot, applebot, PerplexityBot Blocking No — crawling allowed
User-agent: *
User-Agent: Googlebot
User-Agent: applebot
User-Agent: PerplexityBot
User-Agent: bingbot
User-Agent:  OAI-SearchBot
User-Agent:  GPTBot
User-Agent: GeminiBot
User-Agent: ClaudeBot

Disallow: /wp-admin/
Allow: /wp-admin/admin-ajax.php
Disallow: /*?wg-choose-original= 
DISALLOW: /*?x-clickref=
DISALLOW: /*?amp
DISALLOW: /*?d=
DISALLOW: /*?sid2=
DISALLOW: /*.pdf
DISALLOW: /ctrl/*
DISALLOW: /v1a/*
DISALLOW: /*.php
DISALLOW: /404
DISALLOW: /press/2008*
DISALLOW: /press/2009*
DISALLOW: /press/2010*
DISALLOW: /press/2011*
DISALLOW: /press/2012*
DISALLOW: /press/2013*
DISALLOW: /press/2014*
DISALLOW: /press/2015*
DISALLOW: /press/2016*
DISALLOW: /press/2017*
DISALLOW: /press/2018*
DISALLOW: /press/2019*
DISALLOW: /press/2020*
DISALLOW: /press/2021*
DISALLOW: /press/2022*
DISALLOW: /press/category/in-the-news*
DISALLOW: /business/solutions/gdpr/contact-us
DISALLOW: /education/contact/thankyou
DISALLOW: /eula/*
DISALLOW: /finance/contact/thankyou
DISALLOW: /lp/*
DISALLOW: /mac-download
DISALLOW: /pricing/inapp/*
DISALLOW: /secure
DISALLOW: /secure/guidelines
DISALLOW: /support/thirdpartynotices/*
DISALLOW: /thank_you*
DISALLOW: /thank-you*
DISALLOW: /threezerodays
Disallow: *.ttf?
DISALLOW: /mbam-whats-new.json*
Sitemap: https://www.malwarebytes.com/sitemap_index.xml
Sitemap: https://www.malwarebytes.com/pt-br/page-sitemap.xml
Sitemap: https://www.malwarebytes.com/nl/page-sitemap.xml
Sitemap: https://www.malwarebytes.com/es/page-sitemap.xml
Sitemap: https://www.malwarebytes.com/de/page-sitemap.xml
Sitemap: https://www.malwarebytes.com/fr/page-sitemap.xml
Sitemap: https://www.malwarebytes.com/pl/page-sitemap.xml
Sitemap: https://www.malwarebytes.com/it/page-sitemap.xml
Sitemap: https://www.malwarebytes.com/ru/page-sitemap.xml
Sitemap: https://www.malwarebytes.com/pt/page-sitemap.xml
A
Domain Intelligence
malwarebytes.com — via GoDaddy.com, LLC, 22 years, 1 months old, hosted on WordPress.com (Automattic)
PASS
malwarebytes.com — via GoDaddy.com, LLC, 22 years, 1 months old, hosted on WordPress.com (Automattic)
Warning::
Domain expires in 72 days
Consider enabling auto-renewal to prevent accidental expiration.
Got: Expires Jul 3, 2026
Info::
DNSSEC is enabled
Info::
Registrar: GoDaddy.com, LLC
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: WordPress.com (Automattic)
Got: AS2635
Domain expiry

17 days

July 3, 2026

SSL certificate

37 days

Issued by Let's Encrypt

Domain age

22 years, 1 months

Registered July 3, 2004

DNSSEC

Enabled

Protects against DNS spoofing

Hosting

WordPress.com (Automattic)

ASN AS2635

192.0.66.233

Registrar

GoDaddy.com, LLC

Unlocked 4 NS records
Expiry timeline
Today
+1 year
Domain expiry SSL expiry Danger zone (≤30 days)
Recommended actions
  • Renew the domain or enable auto-renewal to prevent accidental expiry
  • Enable registrar lock (clientTransferProhibited) to block unauthorized domain transfers
Registrar GoDaddy.com, LLC
Created July 3, 2004 (22 years, 1 months ago)
Expires July 3, 2026 (2 months)
Last Updated February 17, 2026
Name Servers ns-1123.awsdns-12.org, ns-1684.awsdns-18.co.uk, ns-202.awsdns-25.com, ns-914.awsdns-50.net
DNSSEC Enabled
Hosting
IP Address 192.0.66.233
ASN AS2635 (AUTOMATTIC - Automattic, Inc, US)
Provider WordPress.com (Automattic)
Data source: rdap (0.3s)

Consider enabling auto-renewal to prevent accidental expiration.

Why this matters

Domain expiry approaching — renew immediately and ensure auto-renew + alerting are configured.

Source: ICANN renewal policy

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

Connection waterfall

DNS Lookup 28 ms TCP Connect 0 ms TLS Handshake 3 ms Server Processing 123 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