Skip to content
https://adblockplus.org

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
87
GRADE
B
FIX
0
REVIEW
3
PASS
6
INFO
0
Probed from Madrid, Spain
200 OK
Checks
9
6 PASS 3 REVIEW
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: 793 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 793 B Sitemaps referenced 0 User-agents *, 008, Linguee, mxbot, ip-web-crawler.com, Screaming Frog SEO Spider Blocking No — crawling allowed
User-agent: *
Disallow: /textpattern/
Disallow: /forum/adm/
Disallow: /forum/download/
Disallow: /forum/images/
Disallow: /forum/includes/
Disallow: /forum/language/
Disallow: /forum/styles/
Disallow: /forum/common.php
Disallow: /forum/config.php
Disallow: /forum/cron.php
Disallow: /forum/faq.php
Disallow: /forum/mcp.php
Disallow: /forum/memberlist.php
Disallow: /forum/posting.php
Disallow: /forum/report.php
Disallow: /forum/search.php
Disallow: /forum/ucp.php
Disallow: /forum/viewonline.php
Disallow: /openid
Disallow: /babelzilla.php
Disallow: /getSubscription
Disallow: /403.html
Disallow: /_include/

User-agent: 008
Disallow: /

User-agent: Linguee
Disallow: /

User-agent: mxbot
Disallow: /

User-agent: ip-web-crawler.com
Disallow: /

User-agent: Screaming Frog SEO Spider
Allow: /
sitemap.xml No sitemap found

No sitemap found

Adding a sitemap helps search engines discover your pages.

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

Certificate validity

40
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 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
1 A records, 104 ms lookup
PASS
1 A records, 104 ms lookup
Info::
Resolves to 1 IPv4 address(es)
Got: 199.36.158.100
Info::
Single A record — no DNS redundancy
Multiple A records provide failover if one server goes down.
Info::
No IPv6 (AAAA) records
Info::
6 nameserver(s) configured
Got: pdns73.ultradns.com, pdns73.ultradns.co.uk, pdns73.ultradns.net, pdns73.ultradns.org, pdns73.ultradns.info, pdns73.ultradns.biz
Info::
5 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: 104 ms
Got: 104 ms
A199.36.158.100
AAAA
CNAME
NSpdns73.ultradns.com, pdns73.ultradns.co.uk, pdns73.ultradns.net, pdns73.ultradns.org, pdns73.ultradns.info, pdns73.ultradns.biz
MX
1 aspmx.l.google.com
5 alt2.aspmx.l.google.com
5 alt1.aspmx.l.google.com
10 aspmx2.googlemail.com
10 aspmx3.googlemail.com
TXT
hosting-site=adblockplus-org
google-site-verification=ajs_bDmJHH-QbE-gbOPAHYrJGyLYx_bKKUF4A2amIzU
knowbe4-site-verification=863c28da52149dff8953aeda38712adc
google-site-verification=ak3vKsHGYb11rfkIp1xY3q3xf-gqTIcjOCqTYLBAK-k
google-site-verification=WscIWU4ciCgJXgNh6k-Z0yJQOD7H1h_N1f3kxsNpLEA
SPF v=spf1 include:spf1.adblockplus.org include:_spf.google.com include:sendgrid.net...
google-site-verification=QhWE6Vtk_VsdAUUFBLD-VmT_YFm8wpzO7laxDL0q9ps
CAALookup not available with standard resolver
Resolved in 104 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+
Redirect Chain
No redirects — direct access
PASS
No redirects — direct access
Info::
No redirects — direct access
Got: https://adblockplus.org

https://adblockplus.org

5 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://adblockplus.org2005 msHTTP/1.1
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

301https://www.adblockplus.org/
200https://adblockplus.org/

Preferred variant: non-www

HTTP → HTTPS

301http://adblockplus.org/ https://adblockplus.org/

Consistent

A
Domain Intelligence
adblockplus.org — via RegistryGate GmbH, 20 years, 1 months old, hosted on Fastly
PASS
adblockplus.org — via RegistryGate GmbH, 20 years, 1 months old, hosted on Fastly
Warning::
Domain expires in 47 days
Consider enabling auto-renewal to prevent accidental expiration.
Got: Expires Jun 9, 2026
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: RegistryGate 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.
Info::
Hosting: Fastly
Got: AS54113
Domain expiry

EXPIRED

June 9, 2026

SSL certificate

40 days

Issued by Google Trust Services

Domain age

20 years, 1 months

Registered June 9, 2006

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

Fastly

ASN AS54113

199.36.158.100

Registrar

RegistryGate GmbH

Unlocked 6 NS records
Expiry timeline
Today
+1 year
Domain expiry SSL expiry Danger zone (≤30 days)
Recommended actions
  • Domain has EXPIRED — renew immediately to avoid total site outage
  • Enable DNSSEC to protect visitors from DNS spoofing
  • Enable registrar lock (clientTransferProhibited) to block unauthorized domain transfers
Registrar RegistryGate GmbH
Created June 9, 2006 (20 years, 1 months ago)
Expires June 9, 2026 (1 months)
Last Updated November 25, 2025
Name Servers pdns73.ultradns.org, pdns73.ultradns.biz, pdns73.ultradns.com, pdns73.ultradns.info, pdns73.ultradns.net, pdns73.ultradns.co.uk
DNSSEC Not enabled
Hosting
IP Address 199.36.158.100
ASN AS54113 (FASTLY - Fastly, Inc., US)
Provider Fastly
Data source: rdap (0.4s)

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

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 144 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
PASS
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
51 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.
144 ms
Total Time Total request time from DNS lookup through full response.
145 ms

Connection waterfall

DNS Lookup 51 ms TCP Connect 0 ms TLS Handshake 3 ms Server Processing 90 ms Content Transfer 0 ms
A
CDN & Delivery
Fastly (MISS)
PASS
Fastly (MISS)
Info::
Site is served via Fastly CDN
Got: x-served-by: cache-toj-leto2350073-TOJ
Info::
CDN cache status: MISS
CDN Detected: Fastly
Provider Fastly Cache Status MISS Evidence x-served-by: cache-toj-leto2350073-TOJ
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback