Skip to content
https://texastribune.org

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
87
GRADE
B
FIX
1
REVIEW
3
PASS
5
INFO
0
Probed from Madrid, Spain
301 Moved Permanently
Checks
9
5 PASS 3 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

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.texastribune.org/
200https://texastribune.org/

Inconsistent — duplicate content risk

HTTP → HTTPS

301http://texastribune.org/ https://texastribune.org/

Consistent

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

Certificate validity

87
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
2 A records, 31 ms lookup
PASS
2 A records, 31 ms lookup
Info::
Resolves to 2 IPv4 address(es)
Got: 192.0.78.137, 192.0.78.217
Info::
No IPv6 (AAAA) records
Info::
2 nameserver(s) configured
Got: jean.ns.cloudflare.com, jeff.ns.cloudflare.com
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: 31 ms
Got: 31 ms
A192.0.78.137, 192.0.78.217
AAAA
CNAME
NSjean.ns.cloudflare.com, jeff.ns.cloudflare.com
MX
1 aspmx.l.google.com
5 alt2.aspmx.l.google.com
5 alt1.aspmx.l.google.com
10 alt3.aspmx.l.google.com
10 alt4.aspmx.l.google.com
TXT
apple-domain-verification=qlJSRjJfaAm0dWYX
atlassian-domain-verification=GDo/fN1pgfc4F7ycUtQ8kk/RLgRVTadJAbEVDIJEaGlg4hpdaI...
facebook-domain-verification=jg8t9jm21aiwptr2ozwaheexfpib4o
3FBB64A7OD
MS=4D8B4FDE7E4759D3868AFD464118D1A9CB16493E
google-site-verification=Z1-3dsBwf3Z5PJZRWpWlrTpvu4167IBqg8XYU0ggAx8
google-site-verification=WEErOwZhSfebXUWmfXrXGbIs596L2briH5MGJRPliNE
google-site-verification=9a9FgW1qxgFIvQfvLHU0WQnhNV_cFX65G4i4G5Tx3iA
SPF v=spf1 include:mailgun.org include:_spf.salesforce.com include:_spf.google.com i...
google-site-verification=FjYatvq64seombKQSJa-khMfD4mqKNOSXg78RZFIt4U
anthropic-domain-verification-xa8f7w=TRYLHHQIzXvxdgKHDCVm5tW5n
google-site-verification=1j6vWb3T0e8DSNLy-dEFlUqUXZqc7zp6UV21vYJWC6U
CAALookup not available with standard resolver
Resolved in 31 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), 377 ms total
PASS
1 redirect(s), 377 ms total
Info::
Single redirect
Got: https://texastribune.org → https://www.texastribune.org/ (301)
Info::
WWW normalization redirect

https://texastribune.org

165 ms · HTTP/1.1

301

https://www.texastribune.org/

212 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://texastribune.org301165 msHTTP/1.1nginx
2https://www.texastribune.org/200212 msHTTP/1.1nginx

See the visual redirect chain in the HTTP Probe tab →

A+
Crawlability
robots.txt present, sitemap with 30 URLs
PASS
robots.txt present, sitemap with 30 URLs
Info::
robots.txt is present
Got: 227 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 30 entries
Info::
Sitemap index with 30 child sitemaps
Info::
robots.txt references sitemap
robots.txt 200 OK
Size 227 B Sitemaps referenced 2 User-agents * Blocking No — crawling allowed
Sitemap: https://www.texastribune.org/sitemap.xml
Sitemap: https://www.texastribune.org/news-sitemap.xml
# START YOAST BLOCK
# ---------------------------
User-agent: *
Disallow:

# ---------------------------
# END YOAST BLOCK
A+
Domain Intelligence
texastribune.org — via Tucows Domains Inc., 17 years, 9 months old, hosted on WordPress.com (Automattic)
PASS
texastribune.org — via Tucows Domains Inc., 17 years, 9 months old, hosted on WordPress.com (Automattic)
Info::
Domain registered until Oct 3, 2033 (7 years, 6 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: Tucows Domains 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

2667 days

October 3, 2033

SSL certificate

87 days

Issued by Google Trust Services

Domain age

17 years, 9 months

Registered October 3, 2008

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

WordPress.com (Automattic)

ASN AS2635

192.0.78.217

Registrar

Tucows Domains Inc.

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 Tucows Domains Inc.
Created October 3, 2008 (17 years, 9 months ago)
Expires October 3, 2033 (7 years, 6 months)
Last Updated October 15, 2025
Name Servers jean.ns.cloudflare.com, jeff.ns.cloudflare.com
DNSSEC Not enabled
Hosting
IP Address 192.0.78.217
ASN AS2635 (AUTOMATTIC - Automattic, Inc, US)
Provider WordPress.com (Automattic)
Data source: rdap (0.5s)

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 198 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
PASS
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
36 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.
133 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
198 ms
Total Time Total request time from DNS lookup through full response.
198 ms

Connection waterfall

DNS Lookup 36 ms TCP Connect 0 ms TLS Handshake 133 ms Server Processing 29 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