Skip to content
https://insurancejournal.com

Infrastructure

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

B
Redirect Chain
1 redirect(s), 1189 ms total
REVIEW
1 redirect(s), 1189 ms total
Info::
Single redirect
Got: https://insurancejournal.com → https://www.insurancejournal.com/ (301)
Info::
WWW normalization redirect
Warning::
Redirect overhead: 1189 ms total
Got: 1189 ms

https://insurancejournal.com

469 ms · HTTP/1.1

301

https://www.insurancejournal.com/

721 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://insurancejournal.com301469 msHTTP/1.1Apache
2https://www.insurancejournal.com/200721 msHTTP/1.1Apache

See the visual redirect chain in the HTTP Probe tab →

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.insurancejournal.com/
200https://insurancejournal.com/

Inconsistent — duplicate content risk

HTTP → HTTPS

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

Consistent

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

Certificate validity

187
days left
0d 30d 60d 90d+

Recommended actions

  • Prefer TLS 1.3 — TLS 1.2 is acceptable but TLS 1.3 removes RSA key exchange and improves latency
  • 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
1 A records, 46 ms lookup
PASS
1 A records, 46 ms lookup
Info::
Resolves to 1 IPv4 address(es)
Got: 169.61.31.50
Info::
Single A record — no DNS redundancy
Multiple A records provide failover if one server goes down.
Info::
No IPv6 (AAAA) records
Info::
2 nameserver(s) configured
Got: ns1.softlayer.com, ns2.softlayer.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: 46 ms
Got: 46 ms
A169.61.31.50
AAAA—
CNAME—
NSns1.softlayer.com, ns2.softlayer.com
MX
10 insurancejournal.com.1.0001.arsmtp.com
20 insurancejournal.com.2.0001.arsmtp.com
TXT
facebook-domain-verification=r525ux9cbr3676asuljbicaeohwg67
SPF v=spf1 include:servers.mcsv.net include:spf.protection.outlook.com include:spf.m...
google-site-verification=ac4T5y3gvdYw6hL6Krck4PMiOxfgd9QCzMw4PB33iBw
MS=ms86773015
CAALookup not available with standard resolver
Resolved in 46 ms

Multiple A records provide failover if one server goes down.

Why this matters

Single A record means a single point of failure — if that IP goes down, your site is unreachable until DNS TTL expires.

Learn more ▾

Add multiple A records for round-robin failover, or use a managed DNS provider with health-checked failover (Route 53, Cloudflare, NS1). Short TTL (60-300s) lets clients recover faster on outages.

Source: SRE practice / DNS architecture

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+
Crawlability
robots.txt present, sitemap with 153 URLs
PASS
robots.txt present, sitemap with 153 URLs
Info::
robots.txt is present
Got: 1512 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 153 entries
Info::
Sitemap index with 153 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 1512 B Sitemaps referenced 0 User-agents Googlebot-News, trendkite-akashic-crawler, DataForSeoBot, SemrushBot-OCOB, SemrushBot-SWA, Diffbot, * Blocking No — crawling allowed
# Keep google news bot from certain areas
User-agent: Googlebot-News
Disallow: /*?comments$

# Block bad bots
User-agent: trendkite-akashic-crawler
User-agent: DataForSeoBot
User-agent: SemrushBot-OCOB
User-agent: SemrushBot-SWA
User-agent: Diffbot
Disallow: /

# Global rules
User-agent: *
# Core disallows
Disallow: /ads/
Disallow: /tmp/
Disallow: /example/
Disallow: /scholarship/
Disallow: /subscribe/unsubscribe.php
Disallow: /adshowcase/search/tag_article
Disallow: /feedback/
Disallow: /magazines/page/
Disallow: /phpadsnew/
Disallow: /openx/
Disallow: /directories-new/
Disallow: /advertise/about-us-2021/
Disallow: /wp/wp-admin/
Disallow: /wp-json/
Allow: /wp/wp-admin/admin-ajax.php
# currently meta robots noindexing
#Disallow: /*?download$
#Disallow: /forums/memberlist.php
#Disallow: /research/research/success/

# Crawl budget / index bloat controls
Disallow: /uncategorized/
Disallow: /2000/*/
Disallow: /2001/*/
Disallow: /2002/*/
Disallow: /2003/*/
Disallow: /2004/*/
Disallow: /2005/*/
Disallow: /2006/*/
Disallow: /2007/*/
Disallow: /2008/*/
Disallow: /2009/*/
Disallow: /2010/*/
Disallow: /2011/*/
Disallow: /2012/*/
Disallow: /2013/*/
Disallow: /2014/*/
Disallow: /2015/*/
Disallow: /2016/*/
Disallow: /2017/*/
Disallow: /2018/*/
Disallow: /2019/*/
Disallow: /2020/*/
Disallow: /2021/*/
Disallow: /2022/*/
Disallow: /2023/*/
Disallow: /2024/*/

# archives are duplicates of topics
Disallow: /archive/
Disallow: /archive/*

# linkto value is user-facing, not search intent
Disallow: /linkto/
sitemap.xml 200 OK
Type Sitemap Index URLs 153 entries Valid XML Yes
Child Sitemaps:
A+
Domain Intelligence
insurancejournal.com — via GoDaddy.com, LLC, 30 years, 2 months old, hosted on SOFTLAYER - IBM Cloud, US
PASS
insurancejournal.com — via GoDaddy.com, LLC, 30 years, 2 months old, hosted on SOFTLAYER - IBM Cloud, US
Info::
Domain registered until Jul 24, 2033 (7 years, 4 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.
Info::
Hosting: SOFTLAYER - IBM Cloud, US
Got: AS36351
Domain expiry

2595 days

July 24, 2033

SSL certificate

187 days

Issued by Sectigo Limited

Domain age

30 years, 2 months

Registered July 25, 1996

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

SOFTLAYER - IBM Cloud, US

ASN AS36351

169.61.31.50

Registrar

GoDaddy.com, 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 GoDaddy.com, LLC
Created July 25, 1996 (30 years, 2 months ago)
Expires July 24, 2033 (7 years, 4 months)
Last Updated March 20, 2024
Name Servers ns1.softlayer.com, ns2.softlayer.com
DNSSEC Not enabled
Hosting
IP Address 169.61.31.50
ASN AS36351 (SOFTLAYER - IBM Cloud, US)
Provider SOFTLAYER - IBM Cloud, US
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 504 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
PASS
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
46 ms
TCP Connect TCP Connect — time to establish a TCP connection to the server.
114 ms
TLS Handshake TLS Handshake — time to complete the HTTPS encryption handshake.
231 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
505 ms
Total Time Total request time from DNS lookup through full response.
505 ms

Connection waterfall

DNS Lookup 46 ms TCP Connect 114 ms TLS Handshake 231 ms Server Processing 114 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