Skip to content
https://diabetesjournals.org

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
93
GRADE
A
FIX
0
REVIEW
3
PASS
6
INFO
0
Probed from Amsterdam, Netherlands
403 Forbidden
Checks
9
6 PASS 3 REVIEW
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.diabetesjournals.org/
200https://diabetesjournals.org/

Inconsistent — duplicate content risk

HTTP → HTTPS

301http://diabetesjournals.org/ https://diabetesjournals.org/

Consistent

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

Certificate validity

72
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: AMS)
Got: cf-ray: 9f00bbac4fb51229-AMS
CDN Detected: Cloudflare
Provider Cloudflare Evidence cf-ray: 9f00bbac4fb51229-AMS
A+
DNS Records
2 A records, 7 ms lookup
PASS
2 A records, 7 ms lookup
Info::
Resolves to 2 IPv4 address(es)
Got: 104.18.12.179, 104.18.13.179
Info::
Has 2 IPv6 (AAAA) record(s)
Got: 2606:4700::6812:db3, 2606:4700::6812:cb3
Info::
4 nameserver(s) configured
Got: ns1-05.azure-dns.com, ns2-05.azure-dns.net, ns3-05.azure-dns.org, ns4-05.azure-dns.info
Info::
No MX records — email not configured via DNS
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: 7 ms
Got: 7 ms
A104.18.12.179, 104.18.13.179
AAAA2606:4700::6812:db3, 2606:4700::6812:cb3
CNAME
NSns1-05.azure-dns.com, ns2-05.azure-dns.net, ns3-05.azure-dns.org, ns4-05.azure-dns.info
MX
TXT
SPF v=spf1 include:_spf.silverchair.com -all
gpssy7lwxv5qlnp2lhs5kmbhp92xm2sx
CAALookup not available with standard resolver
Resolved in 7 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
0 redirect(s), 15 ms total
PASS
0 redirect(s), 15 ms total

https://diabetesjournals.org

15 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://diabetesjournals.org40315 msHTTP/1.1cloudflare
A+
IPv6 Readiness
IPv6 reachable (1 ms)
PASS
IPv6 reachable (1 ms)
Info::
IPv6 is configured and reachable at 2606:4700::6812:db3, 2606:4700::6812:cb3
Got: 1 ms connect
IPv6 Ready
AAAA Records 2606:4700::6812:db3, 2606:4700::6812:cb3 Connection Reachable (1 ms)
A
Crawlability
robots.txt present, no sitemap
PASS
robots.txt present, no sitemap
Info::
robots.txt is present
Got: 930 bytes
Info::
No sitemap.xml found
A sitemap helps search engines discover and index your pages more efficiently.
Info::
robots.txt references 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

robots.txt 200 OK
Size 930 B Sitemaps referenced 2 User-agents 008, * Blocking No — crawling allowed

User-agent: 008

Disallow: /


User-agent: *

Disallow: /bin/

Disallow: /config/

Disallow: /app_data/

Disallow: /dlls/

Disallow: /App_Themes/

Disallow: /signin.aspx

Disallow: /searchresults.aspx

Disallow: /search-results

Disallow: /advancedsearch.aspx

Disallow: /advanced-search

Disallow: /DownloadFile/

Disallow: /downloadimage.aspx

Disallow: /Citation/Download

Disallow: /Shibboleth.sso/

Disallow: /SignInShibboleth.aspx

Disallow: /lookup/external-ref

Disallow: /user/logout

Disallow: /cgi/pmidlookup

Disallow: /Themes/Client/app/img/favicons/manifest.json

Disallow: /lookup/google-scholar

Disallow: /store/*

Allow: /cassette.axd/stylesheet/

Allow: /cassette.axd/script/

Allow: /cassette.axd/manifest.xml

Disallow: /*.axd

Disallow: /specificToClient1/

Sitemap: https://diabetesjournals.org/data/sitemap/Site_1/sitemap_books_site1.xml

Sitemap: https://diabetesjournals.org/data/sitemap/sitemap.xml


sitemap.xml No sitemap found

No sitemap found

Adding a sitemap helps search engines discover your pages.

A+
Domain Intelligence
diabetesjournals.org — via GoDaddy.com, LLC, 25 years, 5 months old
PASS
diabetesjournals.org — via GoDaddy.com, LLC, 25 years, 5 months old
Info::
Domain registered until Mar 9, 2028 (1 years, 10 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: GoDaddy.com, 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.
Domain expiry

600 days

March 9, 2028

SSL certificate

72 days

Issued by Let's Encrypt

Domain age

25 years, 5 months

Registered March 9, 2001

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

Unknown

2606:4700::6812:cb3

Registrar

GoDaddy.com, LLC

Unlocked 4 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 GoDaddy.com, LLC
Created March 9, 2001 (25 years, 5 months ago)
Expires March 9, 2028 (1 years, 10 months)
Last Updated March 15, 2026
Name Servers ns3-05.azure-dns.org, ns1-05.azure-dns.com, ns2-05.azure-dns.net, ns4-05.azure-dns.info
DNSSEC Not enabled
Hosting
IP Address 2606:4700::6812:cb3
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 16 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
PASS
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
5 ms
TCP Connect TCP Connect — time to establish a TCP connection to the server.
1 ms
TLS Handshake TLS Handshake — time to complete the HTTPS encryption handshake.
7 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
16 ms
Total Time Total request time from DNS lookup through full response.
16 ms

Connection waterfall

DNS Lookup 5 ms TCP Connect 1 ms TLS Handshake 7 ms Server Processing 3 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