Infrastructure
· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.BURL Variantswww/non-www, trailing slash, HTTP→HTTPSREVIEW
www / non-www
Inconsistent — duplicate content risk
HTTP → HTTPS
Consistent
BTLS Certificate Expiry & Recommendations84 days until leaf cert expires — 3 issues to addressREVIEW
Certificate validity
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
BCDN & DeliveryCloudflareREVIEW
A+DNS Records2 A records, 30 ms lookupPASS
| A | 172.66.138.195, 172.66.135.106 |
| AAAA | 2606:4700:10::ac42:876a, 2606:4700:10::ac42:8ac3 |
| CNAME | — |
| NS | pat.ns.cloudflare.com, woz.ns.cloudflare.com |
| MX | 0 pingdom-com.mail.protection.outlook.com |
| TXT | obhajrktlvoho0qlm1dnrt28fo g5930cc1fsqtrcx2qq8vwmrl45x6p6gp google-site-verification=gxY1tyzepm9DKdreXvG-NfghTQRqX6J6VTgsK72Sa7w lrjf6w5p77s6c4mhwgw0cx2t715qsdsm google-site-verification=aQXIsXpQ7XeExx4ypAX0UIYourUqs4mjui7kMyuIBg8 _nuyjwd76j8c2vbc9hl99iaiiiumdzef MS=ms68254763 62c912g1gh00nnl2m7329w41d4tpjm04 SPF v=spf1 ip4:176.221.80.4 ip4:176.221.80.5 include:_spf.google.com include:sendgri... |
| CAA | Lookup not available with standard resolver |
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.
ARedirect Chain1 redirect(s), 187 ms totalPASS
https://pingdom.com
56 ms · HTTP/1.1
https://www.pingdom.com/
131 ms · HTTP/1.1 FINAL
| # | URL | Status | Time | Protocol | Server |
|---|---|---|---|---|---|
| 1 | https://pingdom.com | 301 | 56 ms | HTTP/1.1 | cloudflare |
| 2 | https://www.pingdom.com/ | 200 | 131 ms | HTTP/1.1 | nginx |
See the visual redirect chain in the HTTP Probe tab →
A+IPv6 ReadinessIPv6 reachable (17 ms)PASS
A+Crawlabilityrobots.txt present, sitemap with 19 URLsPASS
Add a 'Sitemap:' directive to robots.txt so search engines can discover your sitemap.
robots.txt omits Sitemap: directive — crawlers must fetch /sitemap.xml by convention; reliable but missing the explicit hint.
Source: sitemaps.org
User-agent: *
Disallow: /feature/
Noindex: /feature/
Disallow: /signup-b/
Noindex: /signup-b/
Disallow: /tag/
Disallow: /5e3a728225507ce63f3ee8d2f8f702cf
Disallow: /monitor/
Disallow: /demo-request/
Disallow: /contact-sales/
- https://www.pingdom.com/page-sitemap.xml
- https://www.pingdom.com/banner-sitemap.x...
- https://www.pingdom.com/product-sitemap....
- https://www.pingdom.com/api-sitemap.xml
- https://www.pingdom.com/tutorial-sitemap...
- https://www.pingdom.com/customers-sitema...
- https://www.pingdom.com/feature-sitemap....
- https://www.pingdom.com/legal-sitemap.xm...
- https://www.pingdom.com/pricing-sitemap....
- https://www.pingdom.com/company-sitemap....
- https://www.pingdom.com/topic-sitemap.xm...
- https://www.pingdom.com/lp-sitemap.xml
- https://www.pingdom.com/use_cases-sitema...
- https://www.pingdom.com/resources-sitema...
- https://www.pingdom.com/outages-sitemap....
- https://www.pingdom.com/blog-sitemap.xml
- https://www.pingdom.com/blog-sitemap2.xm...
- https://www.pingdom.com/category-sitemap...
- https://www.pingdom.com/resource_types-s...
A+Domain Intelligencepingdom.com — via Key-Systems GmbH, 20 years, 11 months oldPASS
39 days
August 26, 2026
84 days
Issued by Let's Encrypt
20 years, 11 months
Registered August 26, 2005
Not enabled
Protects against DNS spoofing
Unknown
2606:4700:10::ac42:8ac3
Key-Systems GmbH
Expiry timeline
Recommended actions
- Renew the domain or enable auto-renewal to prevent accidental expiry
- 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