Skip to content
https://digitaljournal.com

Infrastructure

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

Inconsistent — duplicate content risk

HTTP → HTTPS

301http://digitaljournal.com/ → https://www.digitaljournal.com/

Consistent

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

Certificate validity

44
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
B
CDN & Delivery
Cloudflare
REVIEW
Cloudflare
Info::
Site is served via Cloudflare CDN (edge: CDG)
Got: cf-ray: 9eff97e2799bd473-CDG
CDN Detected: Cloudflare
Provider Cloudflare Evidence cf-ray: 9eff97e2799bd473-CDG
A+
DNS Records
2 A records, 40 ms lookup
PASS
2 A records, 40 ms lookup
Info::
Resolves to 2 IPv4 address(es)
Got: 104.17.46.19, 104.17.47.19
Info::
No IPv6 (AAAA) records
Info::
2 nameserver(s) configured
Got: ernest.ns.cloudflare.com, carioca.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: 40 ms
Got: 40 ms
A104.17.46.19, 104.17.47.19
AAAA—
CNAME—
NSernest.ns.cloudflare.com, carioca.ns.cloudflare.com
MX
1 aspmx.l.google.com
5 alt1.aspmx.l.google.com
5 alt2.aspmx.l.google.com
10 aspmx3.googlemail.com
10 aspmx2.googlemail.com
TXT
google-site-verification=jBC8n2aO4MvQOf1Tqy879yqJcQ2CcFCEqiuX4GwG0sY
SPF v=spf1 include:45739551.spf06.hubspotemail.net include:_spf.google.com ~all
google-site-verification=feEUeDlgbsHSHtq9GPtlX0eV5upnbvDtEVZ4C1n2lPY
CAALookup not available with standard resolver
Resolved in 40 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), 204 ms total
PASS
1 redirect(s), 204 ms total
Info::
Single redirect
Got: https://digitaljournal.com → https://www.digitaljournal.com/ (301)
Info::
WWW normalization redirect

https://digitaljournal.com

64 ms · HTTP/1.1

301

https://www.digitaljournal.com/

140 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://digitaljournal.com30164 msHTTP/1.1cloudflare
2https://www.digitaljournal.com/200140 msHTTP/1.1cloudflare

See the visual redirect chain in the HTTP Probe tab →

A+
Crawlability
robots.txt present, sitemap with 276 URLs
PASS
robots.txt present, sitemap with 276 URLs
Info::
robots.txt is present
Got: 117 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 276 entries
Info::
Sitemap index with 276 child sitemaps
Info::
robots.txt does not reference a sitemap
Add a 'Sitemap:' directive to robots.txt so search engines can discover your sitemap.

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 117 B Sitemaps referenced 0 User-agents * Blocking No — crawling allowed
User-agent: *

Disallow: /wp-admin/

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

Disallow: /uploads/wpo-plugins-tables-list.json
sitemap.xml 200 OK
Type Sitemap Index URLs 276 entries Valid XML Yes
Child Sitemaps:
A+
Domain Intelligence
digitaljournal.com — via Network Solutions, LLC, 27 years, 11 months old, hosted on Cloudflare
PASS
digitaljournal.com — via Network Solutions, LLC, 27 years, 11 months old, hosted on Cloudflare
Info::
Domain registered until Sep 21, 2026 (5 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: Network Solutions, 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: Cloudflare
Got: AS13335
Domain expiry

97 days

September 21, 2026

SSL certificate

44 days

Issued by Let's Encrypt

Domain age

27 years, 11 months

Registered September 22, 1998

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

Cloudflare

ASN AS13335

104.17.47.19

Registrar

Network Solutions, LLC

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 Network Solutions, LLC
Created September 22, 1998 (27 years, 11 months ago)
Expires September 21, 2026 (5 months)
Last Updated February 21, 2025
Name Servers carioca.ns.cloudflare.com, ernest.ns.cloudflare.com
DNSSEC Not enabled
Hosting
IP Address 104.17.47.19
ASN AS13335 (CLOUDFLARENET - Cloudflare, Inc., US)
Provider Cloudflare
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 98 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
PASS
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
35 ms
TCP Connect TCP Connect — time to establish a TCP connection to the server.
16 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.
98 ms
Total Time Total request time from DNS lookup through full response.
99 ms

Connection waterfall

DNS Lookup 35 ms TCP Connect 16 ms TLS Handshake 22 ms Server Processing 25 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