Infrastructure
· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.DCDN & DeliveryActionNo CDN detectedFIX
Consider using a CDN to improve global delivery speed and reduce origin load.
CTLS Certificate Expiry & RecommendationsAction21 days until leaf cert expires — 5 issues to addressREVIEW
Certificate validity
Recommended actions
- Renew certificate — 21 days remaining
- Add includeSubDomains to the HSTS directive
- Add the preload directive and submit to hstspreload.org once max-age + includeSubDomains are in place
- 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
ADNS Records1 A records, 268 ms lookupPASS
| A | 212.224.123.69 |
| AAAA | 2a01:7e0:0:424::12 |
| CNAME | — |
| NS | ns2.kapper.net, ns5.kapper.net, ns1.kapper.net, ns6.kapper.net, ns7.kapper.net, ns3.kapper.net, ns8.kapper.net, ns4.kapper.net |
| MX | 10 mail.proxmox.com |
| TXT | SPF v=spf1 a mx ptr ip4:79.133.36.241/28 ip4:212.224.123.65/29 ip4:212.186.127.178/2... linkedin-site-verification=e67431e2-0049-4a87-9f51-0aebf7d7cf33 |
| CAA | Lookup not available with standard resolver |
Multiple A records provide failover if one server goes down.
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.
Informational: CAA (Certification Authority Authorization) records weren't checked in this scan.
Slow DNS adds latency to every page load. Consider a faster DNS provider.
DNS resolution is slow — anycast DNS providers (Cloudflare, Route 53) typically resolve <50ms globally.
Source: DNS performance benchmarks
ARedirect Chain1 redirect(s), 788 ms totalPASS
https://proxmox.com
384 ms · HTTP/1.1
https://proxmox.com/en/
404 ms · HTTP/1.1 FINAL
| # | URL | Status | Time | Protocol | Server |
|---|---|---|---|---|---|
| 1 | https://proxmox.com | 301 | 384 ms | HTTP/1.1 | |
| 2 | https://proxmox.com/en/ | 200 | 404 ms | HTTP/1.1 |
See the visual redirect chain in the HTTP Probe tab →
A+IPv6 ReadinessIPv6 reachable (82 ms)PASS
A+Crawlabilityrobots.txt present, sitemap with 475 URLsPASS
# If the Joomla site is installed within a folder such as at
# e.g. www.example.com/joomla/ the robots.txt file MUST be
# moved to the site root at e.g. www.example.com/robots.txt
# AND the joomla folder name MUST be prefixed to the disallowed
# path, e.g. the Disallow rule for the /administrator/ folder
# MUST be changed to read Disallow: /joomla/administrator/
#
# For more information about the robots.txt standard, see:
# http://www.robotstxt.org/orig.html
#
# For syntax checking, see:
# http://www.sxw.org.uk/computing/robots/check.html
User-agent: *
Disallow: /administrator/
Disallow: /cache/
Disallow: /cli/
Disallow: /components/
Disallow: /images/
Disallow: /includes/
Disallow: /installation/
Disallow: /language/
Disallow: /libraries/
Disallow: /logs/
Disallow: /media/
Disallow: /modules/
Disallow: /plugins/
Disallow: /templates/
Disallow: /tmp/
Sitemap: https://www.proxmox.com/en/component/osmap/?view=xml&id=1&format=xml
Sitemap: https://www.proxmox.com/de/component/osmap/?view=xml&id=1&format=xml
- https://www.proxmox.com/en/
- https://www.proxmox.com/en/products/proxmox-virtual-environment/overview
- https://www.proxmox.com/en/products/proxmox-virtual-environment/features
- https://www.proxmox.com/en/products/proxmox-virtual-environment/get-started
- https://www.proxmox.com/en/products/proxmox-virtual-environment/requirements
A+URL Variantswww/non-www, trailing slash, HTTP→HTTPSPASS
www / non-www
Preferred variant: non-www
HTTP → HTTPS
Consistent
A+Domain Intelligenceproxmox.com — via eNom, LLC, 22 years, 5 months oldPASS
268 days
March 8, 2027
21 days
Issued by Let's Encrypt
22 years, 5 months
Registered March 8, 2004
Not enabled
Protects against DNS spoofing
Unknown
2a01:7e0:0:424::12
eNom, LLC
Expiry timeline
Recommended actions
- Renew the TLS certificate or verify auto-renewal is working
- Enable DNSSEC to protect visitors from DNS spoofing
- Enable registrar lock (clientTransferProhibited) to block unauthorized domain transfers
DNSSEC protects against DNS spoofing attacks. While not required, enabling DNSSEC adds an additional layer of security. Contact your DNS provider to enable it.
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.
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