Infrastructure
· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.DCrawlabilityActionrobots.txt present, no sitemapFIX
Disallow: / for all user-agents prevents search engines from indexing any page. This will remove the site from search results.
Disallow: / in robots.txt blocks every search crawler — the site becomes invisible in organic search.
Learn more ▾ ▴
Common deployment mistake: a staging robots.txt with `User-agent: * / Disallow: /` ships to prod. The site falls out of search results within days. Verify your robots.txt is the production-intended version. If this is intentional (private site), no action needed.
Source: Google Search Central
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 https://secure.smugmug.com/help/contact if you'd like to apply to be allowlisted for crawling SmugMug.
user-agent: Adsbot-Google
user-agent: Alexabot
user-agent: BingPreview
user-agent: CloudflarePrefetch
user-agent: FriendFeedBot
user-agent: FunnelBack
user-agent: Google
user-agent: Google Favicon
user-agent: Google-Site-Verification
user-agent: Google-Sitemaps
user-agent: Googlebot
user-agent: Googlebot-Image
user-agent: Googlebot-Mobile
user-agent: Googlebot-News
user-agent: Googlebot-Video
user-agent: Mediapartners-Google
user-agent: Pingdom
user-agent: Pinterest
user-agent: ScoutJet
user-agent: Slurp
user-agent: Spinn3r
user-agent: Teoma
user-agent: Twitterbot
user-agent: Yandex
user-agent: YandexImages
user-agent: YandexVideoParser
user-agent: Yeti
user-agent: archive.org_bot
user-agent: baiduspider
user-agent: bingbot
user-agent: facebookexternalhit
user-agent: gsa-crawler
user-agent: houzzbot
user-agent: ia_archiver
user-agent: msnbot
user-agent: rogerbot
disallow: /404
disallow: /access-denied
disallow: /admin
disallow: /api
disallow: /cart
disallow: /checkout
disallow: /date
disallow: /downloads
disallow: /go
disallow: /hack
disallow: /keyword
disallow: /order
disallow: /password
disallow: /popular
disallow: /search
disallow: /services/api/php
disallow: /services/api/rest
disallow: /services/api/xmlrpc
disallow: /test
allow: /api/developer
allow: /api/doc
allow: /api/v2
user-agent: Google
user-agent: Twitterbot
user-agent: facebookexternalhit
user-agent: houzzbot
allow: /date
allow: /keyword
allow: /popular
user-agent: zombies
disallow: /brains
user-agent: werewolves
disallow: /villagers
user-agent: *
disallow: /
No sitemap found
Adding a sitemap helps search engines discover your pages.
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
BURL Variantswww/non-www, trailing slash, HTTP→HTTPSREVIEW
www / non-www
Inconsistent — duplicate content risk
HTTP → HTTPS
Consistent
BTLS Certificate Expiry & Recommendations248 days until leaf cert expires — 4 issues to addressREVIEW
Certificate validity
Recommended actions
- Add includeSubDomains to the HSTS directive
- 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 Records3 A records, 38 ms lookupPASS
| A | 34.196.90.248, 54.205.100.138, 54.243.200.48 |
| AAAA | — |
| CNAME | — |
| NS | ns-798.awsdns-35.net, ns-1488.awsdns-58.org, ns-1569.awsdns-04.co.uk, ns-160.awsdns-20.com |
| MX | 1 aspmx.l.google.com 5 alt1.aspmx.l.google.com 5 alt2.aspmx.l.google.com 10 alt4.aspmx.l.google.com 10 alt3.aspmx.l.google.com |
| TXT | docusign=db2c269a-ec4f-4e67-ae5f-1ef42b248990 TAILSCALE-2SnWDnM6RXvoBqRCJXyE lovable_verification=mUkuMoOCniK09G3hpvMK status-page-domain-verification=2z6n94xyr5tj atlassian-domain-verification=TgOLLHFpQq2Vo30Hxzddllz1ji7PkMt0vV2E5B3rUCP2ICBlTY... google-site-verification=-nck5ImlodD2x9hVKFtLY2lgmH0nTzkkhqrYMGTbATQ SPF v=spf1 include:_spf.smugmug_com._d.easydmarc.pro ~all miro-verification=57e9f2368bcc8d66648f3d731cb9a81eda2d084b asv=b9dfbae46b15612f6607a68ae19a7e2e easydmarc-verification:c41a276a-ac1c-4df4-afb0-24d13abb4082 |
| 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), 979 ms totalPASS
https://smugmug.com
317 ms · HTTP/1.1
https://www.smugmug.com/
662 ms · HTTP/1.1 FINAL
| # | URL | Status | Time | Protocol | Server |
|---|---|---|---|---|---|
| 1 | https://smugmug.com | 301 | 317 ms | HTTP/1.1 | nginx |
| 2 | https://www.smugmug.com/ | 200 | 662 ms | HTTP/1.1 | nginx |
See the visual redirect chain in the HTTP Probe tab →
A+Domain Intelligencesmugmug.com — via GoDaddy Corporate Domains, LLC, 24 years old, hosted on AWSPASS
25 days
August 6, 2026
248 days
Issued by Amazon
24 years
Registered August 6, 2002
Not enabled
Protects against DNS spoofing
AWS
ASN AS16509
54.243.200.48
GoDaddy Corporate Domains, LLC
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