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 & Recommendations48 days until leaf cert expires — 4 issues to addressREVIEW
Certificate validity
Recommended actions
- Extend HSTS max-age to at least 31536000 (1 year) to meet the preload list criteria
- 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
A+DNS Records2 A records, 100 ms lookupPASS
| A | 104.18.24.124, 104.18.25.124 |
| AAAA | 2606:4700::6812:187c, 2606:4700::6812:197c |
| CNAME | — |
| NS | kim.ns.cloudflare.com, walt.ns.cloudflare.com |
| MX | 10 mxb-0093f001.gslb.pphosted.com 10 mxa-0093f001.gslb.pphosted.com |
| TXT | teamviewer-sso-verification=2c9f1da52e964eb6af9909d750893d27 cursor-domain-verification-dykhgk=CncrAVCaEn9fpKh4kYVqXhNqN apple-domain-verification=r6mYNkXsl7aPGYix7vkxJelk1vvcwXQEYeo-c38c_40 atlassian-domain-verification=J/xb1Xyrh4gIZ44OZ4/F6AbPeNu02GCPAcyhimvAOrrolKXEt4... google-site-verification=sm1wOgCx2R8LH4n37000yeWT5X1e8umjcLG-z9qZpKw anthropic-domain-verification-ghjdqw=yVkhk5wNElqkeWQZz149ol6ji MS=ms37211348 google-site-verification=UPbTTnPs4ha3fqxmKjpHcaabnAEZWX-Q85OUbizAKJQ google-site-verification=RmQrKmhBwPWTpf1_d_0RkJ5oRULLqI5A86GdNE9tCCs SPF v=spf1 ip4:50.28.61.47 ip4:67.227.214.177 ip4:67.227.254.101 ip4:107.170.51.15 i... google-site-verification=nnse0iSgkrdPAaeQ3LtacrOxEi-I67k7Qp8lnExYWnU ca3-3ef4d86701134ab4b167fe16df3f1af7 apple-domain-verification=OE2DhhQMqrE2N3ywAHwDvADUQI93KQYTw56Z3eofA8E zapier-domain-verification-challenge=67896ef7-21b5-48ae-a1ed-eb0581f41f14 google-site-verification=xZSpvWYkBkbz0d2l394Bfno3fgeMk6gck8SWuQ7FxqY ca3-fe7a1b78b031458fb64e655ab3ddd034 google-site-verification=vz715gfpCYxG9BAxAgNY3CvyMUVY23Va3zbqnE3EKSU google-site-verification=q8U4PTDO4zM9KrdDT_TX7ufKSpqTqj2JLzMjpJ_Zdhk 0ed1fe018a9151acd1af774dc18afb836fcafe11f6 google-site-verification=UZMPc0mdFc1Brq1qKBoTfCBtsFO0wcd3XqTaAr1iniU apple-domain-verification=uUz6Sn07zHo6QNhn |
| 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), 383 ms totalPASS
https://webfx.com
212 ms · HTTP/1.1
https://www.webfx.com/
172 ms · HTTP/1.1 FINAL
| # | URL | Status | Time | Protocol | Server |
|---|---|---|---|---|---|
| 1 | https://webfx.com | 301 | 212 ms | HTTP/1.1 | cloudflare |
| 2 | https://www.webfx.com/ | 200 | 172 ms | HTTP/1.1 | cloudflare |
See the visual redirect chain in the HTTP Probe tab →
A+IPv6 ReadinessIPv6 reachable (17 ms)PASS
A+Crawlabilityrobots.txt present, sitemap with 11 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: ia_archiver
Disallow: /
User-agent: *
Disallow: /referral/
Disallow: /old/
Disallow: /PDF/
Disallow: /PPT/
Disallow: /mobile/
Disallow: /jobs/
Disallow: /tools/read-able/check.php*
Disallow: /lp/
Disallow: /new-templates/
Disallow: /fx-testimonials/
Disallow: /clientpoint/
Disallow: /wp-admin/
Disallow: /testimonial/
Disallow: /case-studies/
Disallow: /stats/
Disallow: /style/
Disallow: /*?action=fx_tracking_data
Disallow: /wp-list-pages-by-q-schema.php
Disallow: /wp-list-pages-by-q.php
Disallow: /wp-list-pages-by-cta-id.php
Noindex: /demo/
Allow: /wp-admin/admin-ajax.php
- https://www.webfx.com/post-sitemap.xml
- https://www.webfx.com/post-sitemap2.xml
- https://www.webfx.com/post-sitemap3.xml
- https://www.webfx.com/post-sitemap4.xml
- https://www.webfx.com/post-sitemap5.xml
- https://www.webfx.com/page-sitemap.xml
- https://www.webfx.com/page-sitemap2.xml
- https://www.webfx.com/page-sitemap3.xml
- https://www.webfx.com/page-sitemap4.xml
- https://www.webfx.com/marketing-guide-si...
- https://www.webfx.com/category-sitemap.x...
A+Domain Intelligencewebfx.com — via GoDaddy.com, LLC, 31 years, 5 months oldPASS
624 days
March 1, 2028
48 days
Issued by Google Trust Services
31 years, 5 months
Registered April 24, 1995
Not enabled
Protects against DNS spoofing
Unknown
2606:4700::6812:197c
GoDaddy.com, LLC
Expiry timeline
Recommended actions
- 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