Skip to content
https://washingtonian.com

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
98
GRADE
A+
FIX
0
REVIEW
1
PASS
8
INFO
0
Probed from Madrid, Spain
200 OK
Checks
9
8 PASS 1 REVIEW
B
TLS Certificate Expiry & Recommendations
36 days until leaf cert expires — 3 issues to address
REVIEW

Certificate validity

36
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: 104.17.145.110, 104.17.144.110
Info::
Has 2 IPv6 (AAAA) record(s)
Got: 2606:4700::6811:906e, 2606:4700::6811:916e
Info::
2 nameserver(s) configured
Got: eva.ns.cloudflare.com, terin.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: 44 ms
Got: 44 ms
A104.17.145.110, 104.17.144.110
AAAA2606:4700::6811:906e, 2606:4700::6811:916e
CNAME
NSeva.ns.cloudflare.com, terin.ns.cloudflare.com
MX
1 aspmx.l.google.com
5 alt1.aspmx.l.google.com
5 alt2.aspmx.l.google.com
10 alt4.aspmx.l.google.com
10 alt3.aspmx.l.google.com
TXT
brave-ledger-verification=b8b761adf8fc6d4fa2e0aa8ca70d81647accdf9aad0fa184890343...
facebook-domain-verification=loket7mlad549ax6vyfxp3104m4af6
mandrill_verify.C8OjAcwOpLmqR5jfcwpeWQ
apple-domain-verification=lco3t6rih6X51gto
SPF v=spf1 include:_spf.google.com include:spf.mandrillapp.com include:userinclude.d...
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://washingtonian.com

https://washingtonian.com

77 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://washingtonian.com20077 msHTTP/1.1cloudflare
A+
IPv6 Readiness
IPv6 reachable (17 ms)
PASS
IPv6 reachable (17 ms)
Info::
IPv6 is configured and reachable at 2606:4700::6811:906e, 2606:4700::6811:916e
Got: 17 ms connect
IPv6 Ready
AAAA Records 2606:4700::6811:906e, 2606:4700::6811:916e Connection Reachable (17 ms)
A
Crawlability
robots.txt present, sitemap with 0 URLs
PASS
robots.txt present, sitemap with 0 URLs
Info::
robots.txt is present
Got: 167 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Warning::
sitemap.xml is empty — no URLs found
An empty sitemap provides no value. Add <url> entries for your pages.
Info::
robots.txt references sitemap

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

robots.txt 200 OK
Size 167 B Sitemaps referenced 2 User-agents * Blocking No — crawling allowed
User-agent: *

Disallow: /wp-admin/

Allow: /wp-admin/admin-ajax.php


Sitemap: https://washingtonian.com/sitemap.xml

Sitemap: https://washingtonian.com/sitemap.rss

sitemap.xml 200 OK
Type URL Set URLs 0 entries Valid XML Yes
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.washingtonian.com/
200https://washingtonian.com/

Preferred variant: non-www

HTTP → HTTPS

301http://washingtonian.com/ https://washingtonian.com/

Consistent

A+
Domain Intelligence
washingtonian.com — via Tucows Domains Inc., 30 years, 4 months old
PASS
washingtonian.com — via Tucows Domains Inc., 30 years, 4 months old
Info::
Domain registered until May 1, 2031 (5 years, 1 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.
Domain expiry

1780 days

May 1, 2031

SSL certificate

36 days

Issued by Google Trust Services

Domain age

30 years, 4 months

Registered April 30, 1996

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

Unknown

2606:4700::6811:906e

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 April 30, 1996 (30 years, 4 months ago)
Expires May 1, 2031 (5 years, 1 months)
Last Updated April 1, 2025
Name Servers eva.ns.cloudflare.com, terin.ns.cloudflare.com
DNSSEC Not enabled
Hosting
IP Address 2606:4700::6811:906e
Data source: rdap (0.1s)

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

Connection waterfall

DNS Lookup 40 ms TCP Connect 17 ms TLS Handshake 22 ms Server Processing 32 ms Content Transfer 2 ms
A+
CDN & Delivery
Cloudflare (HIT)
PASS
Cloudflare (HIT)
Info::
Site is served via Cloudflare CDN (edge: CDG)
Got: cf-ray: 9f0893498abdd141-CDG
Info::
CDN cache status: HIT
CDN Detected: Cloudflare
Provider Cloudflare Cache Status HIT Evidence cf-ray: 9f0893498abdd141-CDG
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback