Skip to content
https://veeam.com

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
80
GRADE
B
FIX
2
REVIEW
2
PASS
5
INFO
0
Probed from Santa Clara, United States
301 Moved Permanently
Checks
9
5 PASS 2 REVIEW 2 FIX
F
IPv6 Readiness
Action
IPv6 records exist but unreachable
FIX
IPv6 records exist but unreachable
Warning::
IPv6 DNS records exist but server is not reachable
Having AAAA records but an unreachable server is worse than no AAAA — clients may experience delays before falling back to IPv4.
Got: 2600:1f10:49b4:320c:a24d:803:c58d:2f08, 2600:1f10:49b4:320d:d6f2:8231:f8a4:eb1e
Info::
IPv6 connection error
Got: dial tcp6 [2600:1f10:49b4:320c:a24d:803:c58d:2f08]:443: connect: network is unreachable
IPv6 Misconfigured
AAAA Records 2600:1f10:49b4:320c:a24d:803:c58d:2f08, 2600:1f10:49b4:320d:d6f2:8231:f8a4:eb1e Connection UNREACHABLE

Having AAAA records but an unreachable server is worse than no AAAA — clients may experience delays before falling back to IPv4.

Why this matters

Advertising IPv6 (AAAA records) without a reachable server means IPv6-preferring clients silently fail every connection.

Learn more

Modern browsers prefer IPv6 if AAAA exists (Happy Eyeballs algorithm). If the IPv6 server isn't reachable, browsers fall back to IPv4 — but with seconds of added latency per request. Either fix IPv6 reachability or remove the AAAA records.

Source: RFC 8305 (Happy Eyeballs)

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

Inconsistent — duplicate content risk

HTTP → HTTPS

301http://veeam.com/ https://veeam.com/

Consistent

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

Certificate validity

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

Recommended actions

  • Submit your domain to hstspreload.org to be added to the Chrome preload list
  • 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
2 A records, 147 ms lookup
PASS
2 A records, 147 ms lookup
Info::
Resolves to 2 IPv4 address(es)
Got: 98.90.93.33, 54.205.215.227
Info::
Has 2 IPv6 (AAAA) record(s)
Got: 2600:1f10:49b4:320c:a24d:803:c58d:2f08, 2600:1f10:49b4:320d:d6f2:8231:f8a4:eb1e
Info::
4 nameserver(s) configured
Got: ns-1133.awsdns-13.org, ns-1824.awsdns-36.co.uk, ns-187.awsdns-23.com, ns-581.awsdns-08.net
Info::
3 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: 147 ms
Got: 147 ms
A98.90.93.33, 54.205.215.227
AAAA2600:1f10:49b4:320c:a24d:803:c58d:2f08, 2600:1f10:49b4:320d:d6f2:8231:f8a4:eb1e
CNAME
NSns-1133.awsdns-13.org, ns-1824.awsdns-36.co.uk, ns-187.awsdns-23.com, ns-581.awsdns-08.net
MX
10 mx1.veeam.com
10 mx2.veeam.com
10 mx5.veeam.com
TXT
2pstz7rrsdzq36cv8gpmkqqhlckbyd01
Securiti-verification-id=OW8nxgndgmcr26JSj1fntEstiz1R/nAtHlQNNpJj7n0=
adobe-idp-site-verification=885cdb9c5464071d5fafc8b793e3eb2dfa4dfd1c35c846964782...
apple-domain-verification=LXdFmmkDGb8CJG6S
atlassian-domain-verification=V4XWNb3296t7bRIG2DlVoWXtGKgQSoyQvDHJo2GrTN3FowDYHy...
atlassian-sending-domain-verification=c1904824-439a-4e7d-8d44-56b3d0458953
canva-site-verification=b9Ff6_iTwYvVDAlPuG0_Mw
cursor-domain-verification-9cffjf=765SkBSij0IIDTlE0VutyRF2f
google-site-verification=02BHW6A8wQXTnywL_JFHTgCDMXbjDbS4yGp-ThLmavo
google-site-verification=Al5MoytlENGBht50jO1j5S9FQUMppo0aP0PJIUolHQk
google-site-verification=P3Nvam2C7ONbgz88RAqKtTnn__Fng8Tj9edDQ3k3NT0
google-site-verification=S-k0tnanwu_JrUF7SqFtjmLoUVWsCUzI28stNPDRfxE
google-site-verification=WF5QoU27EtkDScNEdVh5KA1lNb7_jDSSdFkyp3D1kZk
h1-domain-verification=r6z4VhDR9kLFo5fbLPpDascF3mfTy3FkXfkAfE2RSGCNY7kr
infoblox-domain-mastery=51ba1de8ffc009b008faf8ec86c28a558f26192c65409572176b9f0c...
jamf-site-verification=2cUUS22wdwAGzToD0OCTig
mgverify=c29800353c03046c71a6f70e01960c35ed651b58312df54b1a4d5fa13c5fdb67
oci-domain-verification=yKPrvvGc50DjOogTG1so0sGitlQUKUmOKT3f7UUgYIB3A
openai-domain-verification=dv-gXONtk3lIXAWWzYr9ycGw5P0
teamviewer-sso-verification=8100c167a4574b7a8b6876fe55f8ee68
uber-domain-verification=fa4bdf3e-ffe7-4aa4-982d-d636c2b8fbf4
SPF v=spf1 include:_spf.mta.veeam.com include:mktomail.com include:mailsenders.netsu...
wiz-domain-verification=6a31834848503e4ca3d7d4d3126b6320078ec9d01e2d32d5d3546a4e...
CAALookup not available with standard resolver
Resolved in 147 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), 490 ms total
PASS
1 redirect(s), 490 ms total
Info::
Single redirect
Got: https://veeam.com → https://www.veeam.com/ (301)
Info::
WWW normalization redirect

https://veeam.com

244 ms · HTTP/1.1

301

https://www.veeam.com/

245 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://veeam.com301244 msHTTP/1.1nginx
2https://www.veeam.com/200245 msHTTP/1.1nginx

See the visual redirect chain in the HTTP Probe tab →

A+
Crawlability
robots.txt present, sitemap with 4161 URLs
PASS
robots.txt present, sitemap with 4161 URLs
Info::
robots.txt is present
Got: 1846 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 4161 entries
Info::
robots.txt references sitemap
robots.txt 200 OK
Size 1846 B Sitemaps referenced 17 User-agents * Blocking No — crawling allowed
User-agent: *

Disallow: /*.doc

Disallow: /*_wpp.pdf

Disallow: /*_rn.pdf

Disallow: /*_wn.pdf

Disallow: /*_pg.pdf

Disallow: /*_ds.pdf

Disallow: /*_ss.pdf

Disallow: /*_local.pdf

Disallow: /files/release_notes/*.pdf

Disallow: /files/guide/*.pdf

Disallow: /files/report/

Disallow: /pdf/

Disallow: /inc/

Disallow: /message.html

Disallow: /*/message.html

Disallow: /*_prod/

Disallow: /*-free-key

Disallow: /*-form-

Disallow: /*-form/

Disallow: /*-form$

Disallow: /*-form.html

Disallow: /university-archive/

Disallow: /*signin.html

Disallow: /signout

Disallow: /*/download.html

Disallow: */prm_download_x64.html

Disallow: */alt_download.html

Disallow: */alt_download_x64.html

Disallow: */prm_download.html

Disallow: /blog/*tag/

Disallow: /blog/*?s=

Disallow: /blog/*.php

Disallow: /*wp_validate/

Disallow: /wp_list/

Disallow: /*/plugins/

Disallow: /source/

Disallow: /beta/*

Disallow: */test/

Disallow: */tests/

Disallow: */resource-registration/

Disallow: */veeam-search-distributors.html

Sitemap: https://www.veeam.com/sitemap.xml

Sitemap: https://www.veeam.com/de/sitemap.xml

Sitemap: https://www.veeam.com/jp/sitemap.xml

Sitemap: https://www.veeam.com/cn/sitemap.xml

Sitemap: https://www.veeam.com/es-lat/sitemap.xml

Sitemap: https://www.veeam.com/br/sitemap.xml

Sitemap: https://www.veeam.com/tr/sitemap.xml

Sitemap: https://www.veeam.com/cz/sitemap.xml

Sitemap: https://www.veeam.com/pl/sitemap.xml

Sitemap: https://www.veeam.com/nl/sitemap.xml

Sitemap: https://www.veeam.com/es/sitemap.xml

Sitemap: https://www.veeam.com/ru/sitemap.xml

Sitemap: https://www.veeam.com/it/sitemap.xml

Sitemap: https://www.veeam.com/fr/sitemap.xml

Sitemap: https://www.veeam.com/blog/post-sitemap1.xml

Sitemap: https://www.veeam.com/blog/post-sitemap2.xml

Sitemap: https://www.veeam.com/blog/post-sitemap3.xml
A
Domain Intelligence
veeam.com — via GoDaddy.com, LLC, 20 years, 1 months old, hosted on AWS
PASS
veeam.com — via GoDaddy.com, LLC, 20 years, 1 months old, hosted on AWS
Warning::
Domain expires in 45 days
Consider enabling auto-renewal to prevent accidental expiration.
Got: Expires Jun 7, 2026
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: AWS
Got: AS14618
Domain expiry

EXPIRED

June 7, 2026

SSL certificate

189 days

Issued by Amazon

Domain age

20 years, 1 months

Registered June 7, 2006

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

AWS

ASN AS14618

98.90.93.33

Registrar

GoDaddy.com, LLC

Unlocked 4 NS records
Expiry timeline
Today
+1 year
Domain expiry SSL expiry Danger zone (≤30 days)
Recommended actions
  • Domain has EXPIRED — renew immediately to avoid total site outage
  • Enable DNSSEC to protect visitors from DNS spoofing
  • Enable registrar lock (clientTransferProhibited) to block unauthorized domain transfers
Registrar GoDaddy.com, LLC
Created June 7, 2006 (20 years, 1 months ago)
Expires June 7, 2026 (1 months)
Last Updated September 4, 2022
Name Servers ns-1133.awsdns-13.org, ns-1824.awsdns-36.co.uk, ns-187.awsdns-23.com, ns-581.awsdns-08.net
DNSSEC Not enabled
Hosting
IP Address 98.90.93.33
ASN AS14618 (AMAZON-AES - Amazon.com, Inc., US)
Provider AWS
Data source: rdap (0.2s)

Consider enabling auto-renewal to prevent accidental expiration.

Why this matters

Domain expiry approaching — renew immediately and ensure auto-renew + alerting are configured.

Source: ICANN renewal policy

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 242 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
PASS
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
31 ms
TCP Connect TCP Connect — time to establish a TCP connection to the server.
69 ms
TLS Handshake TLS Handshake — time to complete the HTTPS encryption handshake.
70 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
242 ms
Total Time Total request time from DNS lookup through full response.
242 ms

Connection waterfall

DNS Lookup 31 ms TCP Connect 69 ms TLS Handshake 70 ms Server Processing 72 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