Skip to content
https://provenexpert.com

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
85
GRADE
B
FIX
1
REVIEW
3
PASS
5
INFO
0
Probed from Madrid, Spain
308 Permanent Redirect
Checks
9
5 PASS 3 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
2 redirect(s), 333 ms total
REVIEW
2 redirect(s), 333 ms total
Warning::
2 redirects before reaching final URL
Each redirect adds latency. Try to minimize the chain to 1 hop.
Info::
WWW normalization redirect
Info::
Uses 302 (temporary) redirect
If permanent, use 301 instead.
Got: https://www.provenexpert.com/

https://provenexpert.com

61 ms · HTTP/1.1

308

https://www.provenexpert.com/

138 ms · HTTP/1.1

302

https://www.provenexpert.com/en-us/

134 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://provenexpert.com30861 msHTTP/1.1
2https://www.provenexpert.com/302138 msHTTP/1.1nginx
3https://www.provenexpert.com/en-us/200134 msHTTP/1.1nginx

See the visual redirect chain in the HTTP Probe tab →

Each redirect adds latency. Try to minimize the chain to 1 hop.

Why this matters

Redirect chain — each hop adds latency; combine into one redirect where possible.

Source: Google Search Central / web.dev

If permanent, use 301 instead.

Why this matters

302 (Found) is for genuinely temporary redirects — if this redirect is permanent, switch to 301 to preserve SEO equity.

Learn more ▾

Search engines treat 302 as temporary, keeping the original URL indexed and not transferring full link equity to the destination. Use 301 (Moved Permanently) for permanent redirects (HTTP→HTTPS, www-vs-non-www, URL restructures).

Source: Google Search Central

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
TLS Certificate Expiry & Recommendations
42 days until leaf cert expires — 3 issues to address
REVIEW

Certificate validity

42
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
1 A records, 29 ms lookup
PASS
1 A records, 29 ms lookup
Info::
Resolves to 1 IPv4 address(es)
Got: 34.102.149.160
Info::
Single A record — no DNS redundancy
Multiple A records provide failover if one server goes down.
Info::
No IPv6 (AAAA) records
Info::
4 nameserver(s) configured
Got: ns-cloud-c4.googledomains.com, ns-cloud-c2.googledomains.com, ns-cloud-c3.googledomains.com, ns-cloud-c1.googledomains.com
Info::
1 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: 29 ms
Got: 29 ms
A34.102.149.160
AAAA—
CNAME—
NSns-cloud-c4.googledomains.com, ns-cloud-c2.googledomains.com, ns-cloud-c3.googledomains.com, ns-cloud-c1.googledomains.com
MX
10 provenexpert-com.mail.protection.outlook.com
TXT
atlassian-domain-verification=56I9HEdQlSXBpofoaz74za+6YhdefiwXcO/4awPPcY+wronCQB...
openai-domain-verification=dv-nbcoaLeRoUFx2bIMNnyfwFXe
brevo-code:5e88cf24a255781ec96d6fe968a95624
202008192102555fewr9l8wo0f8hhmuw5jld50ipdzsk6ljyl1yv9ye6gobqppui
SPF v=spf1 ip4:168.245.40.123 include:spf.protection.outlook.com include:6890244.spf...
google-site-verification=0RxVmkXXTIw8ghhgLYecmoHV0TGnqmXlvKTghdh9vlI
openai-domain-verification=dv-2BGMN3DSx4bMIiWz4zelHy0C
google-site-verification=7kTcnyT240rN_B--t_XOlvWGG9oq6BXju6hhBVblnL8
google-site-verification=hKTtC7Mel-N24waF2E3ZkNttiT7X2ZQYeS_oRJkgqJE
yrd9jlkpgjszncqv3d6cps0tzf00lfy4
MS=ms85138941
brevo-code:d210db75b0c4cd9ef1099e33d74b476e
apple-domain-verification=ynmWHU2Fwk6kh99W
atlassian-sending-domain-verification=e7048f60-fbbe-4b08-9e4d-1b2a5683e609
CAALookup not available with standard resolver
Resolved in 29 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 256 URLs
PASS
robots.txt present, sitemap with 256 URLs
Info::
robots.txt is present
Got: 168 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 256 entries
Info::
Sitemap index with 256 child sitemaps
Info::
robots.txt references sitemap
robots.txt 200 OK
Size 168 B Sitemaps referenced 2 User-agents * Blocking No — crawling allowed
User-agent: *
Sitemap: https://www.provenexpert.com/www-sitemap-index.xml
Sitemap: https://www.provenexpert.com/sitemaps/expert-compass-index.xml
Disallow: /downloads/
sitemap.xml 200 OK
Type Sitemap Index URLs 256 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::
www/non-www redirect configured correctly (preferred: non-www)
Warning::
HTTP→HTTPS redirect uses 302 instead of 301
Got: 302 temporary redirect Expected: 301 permanent redirect

www / non-www

302https://www.provenexpert.com/
200https://provenexpert.com/

Preferred variant: non-www

HTTP → HTTPS

302http://provenexpert.com/ → https://www.provenexpert.com:443/

Use 301 (permanent) instead of 302 (temporary)

A+
Domain Intelligence
provenexpert.com — via OVH sas, 13 years, 6 months old, hosted on Google Cloud
PASS
provenexpert.com — via OVH sas, 13 years, 6 months old, hosted on Google Cloud
Info::
Domain registered until Dec 21, 2026 (8 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: OVH sas
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: Google Cloud
Got: AS396982
Domain expiry

156 days

December 21, 2026

SSL certificate

42 days

Issued by Google Trust Services

Domain age

13 years, 6 months

Registered December 21, 2012

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

Google Cloud

ASN AS396982

34.102.149.160

Registrar

OVH sas

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 OVH sas
Created December 21, 2012 (13 years, 6 months ago)
Expires December 21, 2026 (8 months)
Last Updated December 22, 2025
Name Servers ns-cloud-c1.googledomains.com, ns-cloud-c2.googledomains.com, ns-cloud-c3.googledomains.com, ns-cloud-c4.googledomains.com
DNSSEC Not enabled
Hosting
IP Address 34.102.149.160
ASN AS396982 (GOOGLE-CLOUD-PLATFORM - Google LLC, US)
Provider Google Cloud
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 92 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
PASS
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
33 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.
25 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
92 ms
Total Time Total request time from DNS lookup through full response.
93 ms

Connection waterfall

DNS Lookup 33 ms TCP Connect 17 ms TLS Handshake 25 ms Server Processing 18 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