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.
BRedirect Chain1 redirect(s), 1390 ms totalREVIEW
https://awwwards.com
624 ms · HTTP/1.1
https://www.awwwards.com/
767 ms · HTTP/1.1 FINAL
| # | URL | Status | Time | Protocol | Server |
|---|---|---|---|---|---|
| 1 | https://awwwards.com | 301 | 624 ms | HTTP/1.1 | nginx |
| 2 | https://www.awwwards.com/ | 200 | 767 ms | HTTP/1.1 | nginx |
See the visual redirect chain in the HTTP Probe tab →
BURL Variantswww/non-www, trailing slash, HTTP→HTTPSREVIEW
www / non-www
Inconsistent — duplicate content risk
HTTP → HTTPS
Consistent
BTLS Certificate Expiry & Recommendations290 days until leaf cert expires — 6 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
- Extend HSTS max-age to at least 31536000 (1 year) to meet the preload list criteria
- 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 Records1 A records, 7 ms lookupPASS
| A | 5.57.227.251 |
| AAAA | 2a00:de40:10:316::100 |
| CNAME | — |
| NS | ns3.dnsmadeeasy.com, ns0.dnsmadeeasy.com, ns2.dnsmadeeasy.com, ns1.dnsmadeeasy.com, ns4.dnsmadeeasy.com |
| MX | 1 aspmx.l.google.com 5 alt1.aspmx.l.google.com 5 alt2.aspmx.l.google.com 10 aspmx2.googlemail.com 10 aspmx3.googlemail.com |
| TXT | google-site-verification=-OM-kR81zA6R4Px_mPFUrT8B4oBr_ElVigoTmGjdSIc njlu5p0dl83km70fkogefsbhh5 SPF v=spf1 mx a include:email.freshdesk.com include:amazonses.com include:_spf.googl... google-site-verification=E0EC8D0n45LolN2a-kYPkSKJzvafsBOb1M-7gl3Ch4w apevofo2vjbgrlv5af4o14ush sg4cmlub6crhjaeh5csh9gj1kk facebook-domain-verification=6w4hbkw0xfls6by0f3ow82ra9s3ufq tmb02ihpjiou9tgdk22ecn7oq6 |
| 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.
A+IPv6 ReadinessIPv6 reachable (158 ms)PASS
ACrawlabilityrobots.txt present, no sitemapPASS
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
Sitemap: https://www.awwwards.com/sitemap.xml
User-agent: *
Disallow: /feed
Disallow: /vote/
Disallow: /tag/
Disallow: /11d12designs/
Disallow: /publicclass/
Disallow: /design-products/
Disallow: /submission/
Disallow: /app.php/
Disallow: /gallery/
Disallow: /search-websites
Disallow: /events/tag/
Disallow: *favourites?page
Disallow: /preview/
Disallow: /search-articles
Disallow: /inspiration/search
Disallow: /websites/?
Disallow: /directory/search/?
Disallow: /*/likes$
Disallow: /*/awards$
Disallow: /*/follow$
Disallow: /*/votes$
Disallow: /*/favorites$
Disallow: /elements/*
Disallow: /inspiration_search/?
Disallow: /*/mobile-excellence-report
Disallow: /academy/new/courses/*
Disallow: /profile/user-project/show-project/*
User-agent: MSIECrawler
Disallow: /
User-agent: psbot
Disallow: /
User-agent: Fasterfox
Disallow: /
User-agent: Xenu
Disallow: /
User-agent: SiteSucker
Disallow: /
User-agent: dotbot
Disallow: /
No sitemap found
Adding a sitemap helps search engines discover your pages.
A+Domain Intelligenceawwwards.com — via OVH sas, 15 years, 9 months oldPASS
437 days
September 28, 2027
290 days
Issued by GoDaddy.com, Inc.
15 years, 9 months
Registered September 28, 2010
Not enabled
Protects against DNS spoofing
Unknown
2a00:de40:10:316::100
OVH sas
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