Skip to content
https://intensedebate.com

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
83
GRADE
B
FIX
1
REVIEW
4
PASS
4
INFO
0
Probed from Madrid, Spain
200 OK
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

C
Crawlability
Action
robots.txt present, sitemap with 0 URLs
REVIEW
robots.txt present, sitemap with 0 URLs
Info::
robots.txt is present
Got: 7507 bytes
Info::
sitemap.xml is present
Warning::
sitemap.xml contains invalid XML
Search engines may not be able to parse the sitemap. Fix XML validation errors.
Warning::
sitemap.xml is empty — no URLs found
An empty sitemap provides no value. Add <url> entries for your pages.
Info::
robots.txt does not reference a sitemap
Add a 'Sitemap:' directive to robots.txt so search engines can discover your sitemap.

Search engines may not be able to parse the sitemap. Fix XML validation errors.

Why this matters

An unparseable sitemap is silently ignored by Google — the URLs it advertises are never queued for crawl.

Learn more

Google's sitemap parser is strict about XML validity. A single unescaped `&` or unclosed tag invalidates the whole file. Run your sitemap through a validator (Search Console's Sitemaps report flags it) and fix the offending entry. Most generators escape correctly; mistakes usually come from manually-written entries.

Source: sitemaps.org / Google Search Central

An empty sitemap provides no value. Add <url> entries for your pages.

Why this matters

An empty sitemap signals 'no content to index' to Google — actively harmful versus having no sitemap at all.

Learn more

Google compares URLs in the sitemap against URLs it has crawled. An empty sitemap on a site with thousands of pages signals abandonment. Either populate it correctly (most CMSes auto-generate) or delete the file and let Google crawl normally.

Source: Google Search Central / sitemaps.org

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 7507 B Sitemaps referenced 0 User-agents Blocking No — crawling allowed
	<!DOCTYPE html>
	<html>
	<head>
		<meta charset="UTF-8">
		<link rel="icon" type="image/x-icon" href="/images/svg/intensedebate-logo-compact.svg"><link rel="stylesheet" type="text/css" href="/css/sys.css?v=107" />
<link rel="stylesheet" type="text/css" href="/css/base.css?v=107" />
<script defer id="bilmur" data-provider="intensedebate" data-service="admin" src="https://s0.wp.com/wp-content/js/bilmur.min.js?i=8&m=202617"></script><script type='text/javascript' src='//wordpress.com/remote-login.php?action=js&#038;id=5116184&#038;host=intensedebate.com&#038;back=https%3A%2F%2Fwww.intensedebate.com%2Frobots.txt'></script><title>IntenseDebate comments enhance and encourage conversation on your blog or website</title><meta name="description" content="IntenseDebate's comment system enhances and encourages conversation on your blog or website." /><meta name="keywords" content="intensedebate, intense debate, intense, debate, comments, comment, commenting, threaded, reply by email, commenter, comment system, commenting system, plugin, widget" /></head><body><style id="antiClickjack">body{display:none !important;}</style>
	<script type="text/javascript">
	if (self === top) {
		var antiClickjack = document.getElementById("antiClickjack");
		antiClickjack.parentNode.removeChild(antiClickjack);
	} else {
		top.location = self.location;
	}
	</script>	<div class="header">
		<div class="wrap">
			<div class="logo">
				<h1>
					<a href="/home" class="intensedebate-logo">IntenseDebate Comment System</a>
				</h1>
			</div>
			<ul class="menu">
								</ul>
				<div class="userbox">
			    <ul class="userbox-menu">
				<li class="loggedout">
					<div class="userbox-avatar">
				    <span></span>
				    <img src="/images/avatar26.png" alt="[Avatar]" />
				    </div>

				    <a href="/logmein">Sign In</a>&nbsp;or&nbsp;<a href="/signup">Create an account</a>
				</li>
			    </ul>
			</div>
            		</div><!--/ wrap -->
	</div><!--/ header -->
    <div class="wrap"><div class="main"><div class="main-inner"><div id="wrapx"><div id="id-container"><div class="id-m">
<div class="columns single">
       <div class="main">
               <div class="id-main-t"><div></div></div>
               <div class="id-main-m">
                       <div>
                               <div>
                               	                                       <h4>Error 404: Page not found</h4>
                                       <p>We're sorry, but the page you tried to access simply doesn't exist. Please check for typing errors.</p>
                                       <p><a href="/">Go to the home page</a></p>
                                                               </div>
                       </div>
               </div>
               <div class="id-main-b"><div></div></div>
         </div> 
              
</div></div></div></div></div>		</div>
	</div><!--/ wrap-->
	<div class="footer">
		<div class="wrap">
			<span class="clear"></span>
			<a href='https://automattic.com' class="automattic_joint" style='text-decoration: none'>an <img src="/images/svg/automattic-logo.svg" alt="Automattic logo"/> Company</a>
			<span class="clear"></span>
			<p class="footer-menu">
				<a href="/home"><span class="r">Home</span></a>
				<a href="/features"><span class="r">Features</span></a>
				<a href="/aboutus"><span class="r">About</span></a>
				<a href="https://automattic.com/press"><span class="r">Press</span></a>
				<!--<a href="/contactus"><span class="r">Contact</span></a>-->
				<a href="https://support.intensedebate.com/category/developers/"><span class="r">Developers</span></a>
				<a href="/help"><span class="r">Help</span></a>
			</p><!--/ footer-menu -->
			<p class="footer-a8c">
				&copy; 2026 Automattic Inc. <a href="/tos">TOS</a>
				| <a href="https://automattic.com/privacy/">Privacy Policy</a>
				| <a href="https://automattic.com/privacy/#california-consumer-privacy-act-ccpa">Privacy Notice for California Users</a>
				<span id="ccpa-donotsell" style="display:none">
					| <a href="#">Do Not Sell or Share My Personal Information</a>
				</span>
			</p>
			<div class="clear"></div>
		</div><!--/ wrap -->
	</div><!--/ footer -->
	<script src="/js/idm-combined.js?v=2" type="text/javascript"></script>
    <script type="text/javascript" src="/wpfiles/jquery.js?ver=1.2.3"></script>
	<script type="text/javascript" src="/js/footer-ccpa.js"></script>
	<script type="text/javascript">
	window.a8cAnalyticsConfig = {"cookieBanner":{"skipBanner":false,"version":"2","cookieDomain":"intensedebate.com","v2CookieName":"eu_cb","v2Text":"We and our partners process your personal data (such as browsing data, IP addresses, cookie information, and other unique identifiers) based on your consent and\/or our legitimate interest to optimize our website, marketing activities, and your user experience.","v2OptionsText":"Your privacy is critically important to us. We and our partners use, store, and process your personal data to optimize: our <strong>website<\/strong> such as by improving security or conducting analytics, <strong>marketing activities<\/strong> to help deliver relevant marketing or content, and your <strong>user experience<\/strong> such as by remembering your account name, language settings, or cart information, where applicable. You can customize your cookie settings below. Learn more in our <a href=\"https:\/\/automattic.com\/privacy\/\" target=\"_blank\">Privacy Policy<\/a> and <a href=\"https:\/\/automattic.com\/cookies\/\" target=\"_blank\">Cookie Policy<\/a>.","v2EssentialOptionHeading":"Required","v2EssentialOptionText":"<strong>Required:<\/strong> These cookies are essential for our websites and services to perform basic functions and are necessary for us to operate certain features. These include those required to allow registered users to authenticate and perform account-related functions, store preferences set by users such as account name, language, and location, and ensure our services are operating properly.","v2AnalyticsOptionHeading":"Analytics","v2AnalyticsOptionText":"<strong>Analytics:<\/strong> These cookies allow us to optimize performance by collecting information on how users interact with our websites, including which pages are visited most, as well as other analytical data. We use these details to improve how our websites function and to understand how users interact with them. You can opt-out by logging into your account and changing your privacy settings at <a target=\"_blank\" href=\"https:\/\/wordpress.com\/me\/privacy\">https:\/\/wordpress.com\/me\/privacy<\/a>.","v2AdvertisingOptionHeading":"Advertising","v2AdvertisingOptionText":"<strong>Advertising:<\/strong> These cookies are set by us and our advertising partners to provide you with relevant content and to understand that content\u2019s effectiveness. They may be used to collect information about your online activities over time and across different websites to predict your preferences and to display more relevant advertisements to you. These cookies also allow a profile to be built about you and your interests, and enable personalized ads to be shown to you based on your profile.","v2CustomizeButtonText":"Customize","v2AcceptAllButtonText":"Accept All","v2AcceptSelectionButtonText":"Accept Selection"}};
</script>
<script type="text/javascript" src="//s0.wp.com/wp-content/mu-plugins/a8c-analytics/a8c-analytics.js?v=20251218" charset="utf-8" async crossorigin="anonymous"></script></body></html>
sitemap.xml 200 OK
Type URL Set URLs 0 entries Valid XML No
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.intensedebate.com/
200https://intensedebate.com/

Inconsistent — duplicate content risk

HTTP → HTTPS

301http://intensedebate.com/ https://intensedebate.com/

Consistent

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

Certificate validity

59
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
A+
DNS Records
2 A records, 44 ms lookup
PASS
2 A records, 44 ms lookup
Info::
Resolves to 2 IPv4 address(es)
Got: 192.0.123.247, 192.0.123.246
Info::
No IPv6 (AAAA) records
Info::
3 nameserver(s) configured
Got: ns2.automattic.com, ns1.automattic.com, ns3.automattic.com
Info::
2 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: 44 ms
Got: 44 ms
A192.0.123.247, 192.0.123.246
AAAA
CNAME
NSns2.automattic.com, ns1.automattic.com, ns3.automattic.com
MX
10 mx1.dfw.automattic.com
10 mx2.ams.automattic.com
TXT
SPF v=spf1 include:_spf.automattic.com include:mail.zendesk.com -all
CAALookup not available with standard resolver
Resolved in 44 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
No redirects — direct access
PASS
No redirects — direct access
Info::
No redirects — direct access
Got: https://intensedebate.com

https://intensedebate.com

467 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://intensedebate.com200467 msHTTP/1.1nginx
A+
Domain Intelligence
intensedebate.com — via MarkMonitor Inc., 20 years, 6 months old, hosted on WordPress.com (Automattic)
PASS
intensedebate.com — via MarkMonitor Inc., 20 years, 6 months old, hosted on WordPress.com (Automattic)
Info::
Domain registered until Jan 26, 2028 (1 years, 9 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: MarkMonitor Inc.
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

591 days

January 26, 2028

SSL certificate

59 days

Issued by Let's Encrypt

Domain age

20 years, 6 months

Registered January 26, 2006

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

WordPress.com (Automattic)

ASN AS2635

192.0.123.246

Registrar

MarkMonitor Inc.

Unlocked 3 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 MarkMonitor Inc.
Created January 26, 2006 (20 years, 6 months ago)
Expires January 26, 2028 (1 years, 9 months)
Last Updated December 25, 2025
Name Servers ns1.automattic.com, ns2.automattic.com, ns3.automattic.com
DNSSEC Not enabled
Hosting
IP Address 192.0.123.246
ASN AS2635 (AUTOMATTIC - Automattic, Inc, US)
Provider WordPress.com (Automattic)
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 494 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
PASS
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
26 ms
TCP Connect TCP Connect — time to establish a TCP connection to the server.
155 ms
TLS Handshake TLS Handshake — time to complete the HTTPS encryption handshake.
157 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
494 ms
Total Time Total request time from DNS lookup through full response.
494 ms

Connection waterfall

DNS Lookup 26 ms TCP Connect 155 ms TLS Handshake 157 ms Server Processing 156 ms Content Transfer 1 ms
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback