Infrastructure
· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.DURL VariantsActionwww/non-www, trailing slash, HTTP→HTTPSFIX
www / non-www
Inconsistent — duplicate content risk
HTTP → HTTPS
HTTP version does not redirect to HTTPS
CIPv6 ReadinessActionNo IPv6 supportREVIEW
IPv6 support is increasingly important for global accessibility. About 40% of internet users have IPv6 connectivity.
No AAAA records — same impact as 'no IPv6 (AAAA) records'; IPv6-preferring clients pay extra latency falling back to IPv4.
Source: Google IPv6 stats
BTLS Certificate Expiry & Recommendations59 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 & DeliveryGoogle Cloud CDNREVIEW
A+DNS Records1 A records, 46 ms lookupPASS
| A | 34.36.185.49 |
| AAAA | — |
| CNAME | — |
| NS | ns4-03.azure-dns.info, ns2-03.azure-dns.net, ns3-03.azure-dns.org, ns1-03.azure-dns.com |
| MX | 0 kitco-com.mail.protection.outlook.com |
| TXT | MS=ms33623696 openai-domain-verification=dv-XNiD29ViA54D6DIgOHTHfhbS se9cbthjb2acj15jqs1059u1et SPF v=spf1 mx include:_spf.ultipro.com include:spf.zoho.com include:transmail.net in... _globalsign-domain-verification=kfMq-Xsq8rng3kmcygtA5qy0W_fjUBd1dyg5KY2ZlA ktchv725hobnr9bbomob2bm1g5 ehcqu2mvgio1qn3b2of8j9fjht da5490964u82i1lccaupfqrb4m fastly-domain-delegation-a3gxsjpaqpinhejpisao-726976-2023-12-22 kaz-mtl1-kitco-com-redirect.azurewebsites.net google-site-verification=9f6Mo6ZW-IcS3nxtIOvjhv4zIywYKnC8L-YaoYjULAQ google-site-verification=-mif1IHNRTkBiZPGJHkt0-7QWLbC0l3ijcap2udldRI 5qjgg7klmkhnr7sc54iscm88g2 VGnarliGlKW1KAJ1QpubnTxcKWZIWQqb6tE1iBvhNJOXcMMpM7UZSR0df1HUkajxvqkvhwLUpUeIi2Ud... |
| 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.
ARedirect Chain1 redirect(s), 354 ms totalPASS
https://kitco.com
154 ms · HTTP/1.1
http://www.kitco.com/
200 ms · HTTP/1.1 FINAL
| # | URL | Status | Time | Protocol | Server |
|---|---|---|---|---|---|
| 1 | https://kitco.com | 301 | 154 ms | HTTP/1.1 | Varnish |
| 2 | http://www.kitco.com/ | 200 | 200 ms | HTTP/1.1 |
See the visual redirect chain in the HTTP Probe tab →
A+Crawlabilityrobots.txt present, sitemap with 7 URLsPASS
# *
User-agent: *
Allow: /
# Host
Host: https://www.kitco.com
# Sitemaps
Sitemap: https://www.kitco.com/sitemap.xml
Sitemap: https://www.kitco.com/sitemap/dynamic.xml
Sitemap: https://www.kitco.com/static-sitemaps/news.xml
Sitemap: https://www.kitco.com/static-sitemaps/off-the-wire.xml
Sitemap: https://www.kitco.com/static-sitemaps/opinions.xml
Sitemap: https://www.kitco.com/static-sitemaps/video.xml
Sitemap: https://www.kitco.com/static-sitemaps/symbols-index.xml
A+Domain Intelligencekitco.com — via Network Solutions, LLC, 31 years, 1 months old, hosted on Google CloudPASS
1887 days
August 14, 2031
59 days
Issued by Google Trust Services
31 years, 1 months
Registered August 15, 1995
Not enabled
Protects against DNS spoofing
Google Cloud
ASN AS396982
34.36.185.49
Network Solutions, 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