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.
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
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
# See http://www.robotstxt.org/wc/norobots.html for documentation on how to use the robots.txt file
User-agent: Mediapartners-Google*
Disallow:
User-agent: *
Disallow: /redirect
Disallow: /invitation
Disallow: /sign-in
Disallow: /sign-out
Disallow: /search
Disallow: /blog_this
Disallow: /import_all
Disallow: /roll
Disallow: /post
Disallow: /customize_search
Disallow: /people/like
Disallow: /people/search
Disallow: /buzz/justin
Disallow: /user_mana2
Disallow: /bookmark_mana2
Disallow: /tag_mana2
Disallow: /facebook
Disallow: /openid
Disallow: /toolbar
Disallow: /chappai
Disallow: /rss
Disallow: /cached
Disallow: /annotated
Disallow: /proxy
#Disallow: /user
Disallow: /user/*/
Disallow: /community
Disallow: /cloud/
Disallow: /*?
Disallow: /tag/*+
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 & Recommendations154 days until leaf cert expires — 4 issues to addressREVIEW
Certificate validity
Recommended actions
- Prefer TLS 1.3 — TLS 1.2 is acceptable but TLS 1.3 removes RSA key exchange and improves latency
- 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
A+DNS Records1 A records, 40 ms lookupPASS
| A | 54.148.192.94 |
| AAAA | — |
| CNAME | — |
| NS | ns3.zoneedit.com, ns18.zoneedit.com |
| MX | 0 ASPMX.L.GOOGLE.com 10 ALT1.ASPMX.L.GOOGLE.com 10 ALT2.ASPMX.L.GOOGLE.com 20 ASPMX5.GOOGLEMAIL.com 20 ASPMX4.GOOGLEMAIL.com 20 ASPMX2.GOOGLEMAIL.com 20 ASPMX3.GOOGLEMAIL.com |
| TXT | _lbqtqwfel2p2s1hzazwciypx34dtpov google-site-verification=jEyJnTdt9H3zybR7Jh0b3WI9GxKTmKU8m7ulcqrb7mQ SPF v=spf1 mx a:mail4.diigo.com a:mail3.diigo.com a:mail5.diigo.com a:mail6.diigo.co... _n8uwun3az6dfkrpcu82ztjpsz0nm99k xh4pys2kccpbb5f79r501gs19h6ctfy0 |
| 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), 606 ms totalPASS
https://diigo.com
293 ms · HTTP/1.1
https://www.diigo.com/
313 ms · HTTP/1.1 FINAL
| # | URL | Status | Time | Protocol | Server |
|---|---|---|---|---|---|
| 1 | https://diigo.com | 301 | 293 ms | HTTP/1.1 | nginx |
| 2 | https://www.diigo.com/ | 200 | 313 ms | HTTP/1.1 | nginx |
See the visual redirect chain in the HTTP Probe tab →
A+Domain Intelligencediigo.com — via GoDaddy.com, LLC, 21 years, 7 months old, hosted on AWSPASS
1255 days
December 22, 2029
154 days
Issued by DigiCert Inc
21 years, 7 months
Registered December 22, 2004
Not enabled
Protects against DNS spoofing
AWS
ASN AS16509
54.148.192.94
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