Infrastructure
· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.BCrawlabilityrobots.txt present, no sitemapREVIEW
A sitemap helps search engines discover and index your pages more efficiently.
No sitemap.xml — Google relies on crawl-graph discovery alone, slowing indexing of deep or fresh URLs.
Learn more ▾ ▴
A sitemap accelerates Google's discovery of new and updated content. Most CMSes auto-generate one; static-site frameworks need a build-step plugin. Reference it from robots.txt and submit in Search Console to confirm Google can fetch it.
Source: sitemaps.org / Google Search Central
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: Mediapartners-Google*
Disallow:
User-agent: Slurp
Crawl-delay: 1
User-agent: AdsBot-Google*
Disallow:
User-agent: *
Disallow: /*.pdf$
Disallow: /*.txt$
Disallow: /*.html$
Disallow: /file/*
Disallow: /howto/*
Disallow: /image/*
No sitemap found
Adding a sitemap helps search engines discover your pages.
BURL Variantswww/non-www, trailing slash, HTTP→HTTPSREVIEW
www / non-www
Inconsistent — duplicate content risk
HTTP → HTTPS
Consistent
BTLS Certificate Expiry & Recommendations163 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 & DeliveryAWS CloudFront (FunctionGeneratedResponse from cloudfront)REVIEW
A+DNS Records4 A records, 94 ms lookupPASS
| A | 108.158.147.44, 108.158.147.56, 108.158.147.110, 108.158.147.67 |
| AAAA | 2600:9000:238f:aa00:c:1faa:6800:93a1, 2600:9000:238f:3200:c:1faa:6800:93a1, 2600:9000:238f:ec00:c:1faa:6800:93a1, 2600:9000:238f:7600:c:1faa:6800:93a1, 2600:9000:238f:b200:c:1faa:6800:93a1, 2600:9000:238f:4800:c:1faa:6800:93a1, 2600:9000:238f:ac00:c:1faa:6800:93a1, 2600:9000:238f:e400:c:1faa:6800:93a1 |
| CNAME | — |
| NS | ns-104.awsdns-13.com, ns-1163.awsdns-17.org, ns-1777.awsdns-30.co.uk, ns-557.awsdns-05.net |
| MX | 10 instructables-com.mail.protection.outlook.com |
| TXT | 554kz8j691dnm1t21mwm87jctmnnsdzj 8ymdk8vbmflslk0gsn5cwf493vgxkfcn MS=ms97751969 facebook-domain-verification=j8ezjcbwhfykmj7wqvqpe34zrx81wy facebook-domain-verification=qg9kaa5826ixuz46vsm5kmzkqa0hqc google-site-verification=aJwf2CzmW8LrvqB3rvJz3QIA7ogz4xXhPS94jzaMpNw google-site-verification=wezeEJNzmS1TwrPQOStlFIw9ZA_22X3pFv_7Ll4vu24 SPF v=spf1 include:u1654969.wl.sendgrid.net include:spf.protection.outlook.com -all |
| 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), 129 ms totalPASS
https://instructables.com
102 ms · HTTP/1.1
https://www.instructables.com/
26 ms · HTTP/1.1 FINAL
| # | URL | Status | Time | Protocol | Server |
|---|---|---|---|---|---|
| 1 | https://instructables.com | 301 | 102 ms | HTTP/1.1 | CloudFront |
| 2 | https://www.instructables.com/ | 200 | 26 ms | HTTP/1.1 | CloudFront |
See the visual redirect chain in the HTTP Probe tab →
A+IPv6 ReadinessIPv6 reachable (1 ms)PASS
ADomain Intelligenceinstructables.com — via CSC Corporate Domains, Inc., 21 years, 1 months oldPASS
6 days
June 22, 2026
163 days
Issued by Amazon
21 years, 1 months
Registered June 22, 2005
Not enabled
Protects against DNS spoofing
Unknown
2600:9000:238f:9e00:c:1faa:6800:93a1
CSC Corporate Domains, Inc.
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
Consider enabling auto-renewal to prevent accidental expiration.
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.
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