Skip to content
https://financesonline.com

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
99
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
57 days until leaf cert expires — 3 issues to address
REVIEW

Certificate validity

57
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
3 A records, 48 ms lookup
PASS
3 A records, 48 ms lookup
Info::
Resolves to 3 IPv4 address(es)
Got: 104.26.1.204, 172.67.71.236, 104.26.0.204
Info::
Has 3 IPv6 (AAAA) record(s)
Got: 2606:4700:20::681a:1cc, 2606:4700:20::681a:cc, 2606:4700:20::ac43:47ec
Info::
2 nameserver(s) configured
Got: katja.ns.cloudflare.com, gabe.ns.cloudflare.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: 48 ms
Got: 48 ms
A104.26.1.204, 172.67.71.236, 104.26.0.204
AAAA2606:4700:20::681a:1cc, 2606:4700:20::681a:cc, 2606:4700:20::ac43:47ec
CNAME
NSkatja.ns.cloudflare.com, gabe.ns.cloudflare.com
MX
10 mxa.mailgun.org
10 mxb.mailgun.org
TXT
1df28e684df175b24f9ce1d1b85494ba6508c96c8cbe904bb9310f261ca7cfb
SPF v=spf1 a include:_spf.google.com include:mailgun.org ~all
google-site-verification=xzP9cfC7X3FYc_EZQQXkJn15Yn5n968XcXOjR_tTIqM
google-site-verification=j48X6pUONJddW_NtoHI3ji6Lnwl3KU8w2BQ6Z2gziAk
CAALookup not available with standard resolver
Resolved in 48 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://financesonline.com

https://financesonline.com

73 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://financesonline.com20073 msHTTP/1.1cloudflare
A+
IPv6 Readiness
IPv6 reachable (17 ms)
PASS
IPv6 reachable (17 ms)
Info::
IPv6 is configured and reachable at 2606:4700:20::681a:1cc, 2606:4700:20::681a:cc, 2606:4700:20::ac43:47ec
Got: 17 ms connect
IPv6 Ready
AAAA Records 2606:4700:20::681a:1cc, 2606:4700:20::681a:cc, 2606:4700:20::ac43:47ec Connection Reachable (17 ms)
A+
Crawlability
robots.txt present, sitemap with 38 URLs
PASS
robots.txt present, sitemap with 38 URLs
Info::
robots.txt is present
Got: 575 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 38 entries
Info::
Sitemap index with 38 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 575 B Sitemaps referenced 0 User-agents CCBot, GPTBot, Rogerbot, QuetextBot, PetalBot, *, Dotbot, SemrushBot, MJ12bot, MegaIndex.ru, wotbox, Cliqzbot Blocking No — crawling allowed
User-agent: Rogerbot

Disallow: /


User-agent: Dotbot

Disallow: /


User-agent: SemrushBot

Disallow: /


User-agent: MJ12bot

Disallow: /


User-agent: MegaIndex.ru

Disallow: /


User-agent: wotbox

Disallow: /


User-agent: QuetextBot

Disallow: /


User-agent: Cliqzbot

Disallow: /  


User-agent: PetalBot

Disallow: /


User-agent: CCBot

Disallow: /


User-agent: GPTBot

Disallow: /


User-agent: *

Disallow: /wp-admin/

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

Disallow: /*?s=*

Disallow: /*&s=*

Allow: /seal/*

Disallow: /see/

Disallow: /add-user-review/


sitemap.xml 200 OK
Type Sitemap Index URLs 38 entries Valid XML Yes
Child Sitemaps:
A+
URL Variants
www/non-www, trailing slash, HTTP→HTTPS
PASS
www/non-www, trailing slash, HTTP→HTTPS
Info::
HTTP correctly 301-redirects to HTTPS

www / non-www

https://www.financesonline.com/
200https://financesonline.com/

HTTP → HTTPS

301http://financesonline.com/ https://financesonline.com/

Consistent

A+
Domain Intelligence
financesonline.com — via Name.com, Inc., 23 years, 8 months old
PASS
financesonline.com — via Name.com, Inc., 23 years, 8 months old
Info::
Domain registered until Dec 1, 2026 (7 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: Name.com, 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

139 days

December 1, 2026

SSL certificate

57 days

Issued by Google Trust Services

Domain age

23 years, 8 months

Registered December 1, 2002

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

Unknown

2606:4700:20::681a:cc

Registrar

Name.com, 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 Name.com, Inc.
Created December 1, 2002 (23 years, 8 months ago)
Expires December 1, 2026 (7 months)
Last Updated June 10, 2025
Name Servers gabe.ns.cloudflare.com, katja.ns.cloudflare.com
DNSSEC Not enabled
Hosting
IP Address 2606:4700:20::681a:cc
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 115 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
PASS
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
41 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.
114 ms
Total Time Total request time from DNS lookup through full response.
116 ms

Connection waterfall

DNS Lookup 41 ms TCP Connect 17 ms TLS Handshake 22 ms Server Processing 34 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: 9f07b9a2c9eb3219-CDG
Info::
CDN cache status: HIT
CDN Detected: Cloudflare
Provider Cloudflare Cache Status HIT Evidence cf-ray: 9f07b9a2c9eb3219-CDG
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback