Infrastructure
· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.BURL Variantswww/non-www, trailing slash, HTTP→HTTPSREVIEW
www / non-www
Inconsistent — duplicate content risk
HTTP → HTTPS
Consistent
BTLS Certificate Expiry & Recommendations136 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
A+DNS Records4 A records, 41 ms lookupPASS
| A | 13.249.228.59, 13.249.228.61, 13.249.228.63, 13.249.228.90 |
| AAAA | 2600:9000:204e:2400:4:2b2a:34c0:93a1, 2600:9000:204e:7000:4:2b2a:34c0:93a1, 2600:9000:204e:b600:4:2b2a:34c0:93a1, 2600:9000:204e:f800:4:2b2a:34c0:93a1, 2600:9000:204e:c800:4:2b2a:34c0:93a1, 2600:9000:204e:be00:4:2b2a:34c0:93a1, 2600:9000:204e:7600:4:2b2a:34c0:93a1, 2600:9000:204e:6400:4:2b2a:34c0:93a1 |
| CNAME | — |
| NS | ns-1950.awsdns-51.co.uk, ns-293.awsdns-36.com, ns-712.awsdns-25.net, ns-1056.awsdns-04.org |
| MX | 1 aspmx.l.google.com 5 alt2.aspmx.l.google.com 5 alt1.aspmx.l.google.com 10 alt4.aspmx.l.google.com 10 alt3.aspmx.l.google.com |
| TXT | google-site-verification=4wwlBtIcKrsZBEwdzWz5Qms3OGczeKHWMMOcYrHXutg google-site-verification=xV-YEOcS6jcZS5L-xoApyy-PPRf6fPjlfrJII9jV_H4 google-site-verification=c2sONU9v6lndrJHC5JYyPV8SZjFxbApLBBO0qJ8IJuE atlassian-domain-verification=AYkYz1xeXsulzP+7UlToarKBfcTQa9oXDb0b/uF/vnm6OHdAAY... google-site-verification=bubMDyJ344hbAn66Ogw4r3srvWDhd-RtlnH48BRLX18 SPF v=spf1 include:_spf.google.com include:sendgrid.net include:spf.mandrillapp.com ... _globalsign-domain-verification=VPemhDee0EKRXi0IPzeSUrn849jHevrjIaTeDYOTZ4 google-site-verification=CQuIhYUR0EErworNvXwWQUkGeKPsKH0jb4KSl0Q6OVA facebook-domain-verification=f8irkbummzdvqfbdawbx0iqaixd7rg |
| 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), 954 ms totalPASS
https://archdaily.com
58 ms · HTTP/1.1
https://www.archdaily.com/
896 ms · HTTP/1.1 FINAL
| # | URL | Status | Time | Protocol | Server |
|---|---|---|---|---|---|
| 1 | https://archdaily.com | 301 | 58 ms | HTTP/1.1 | nginx/1.14.2 |
| 2 | https://www.archdaily.com/ | 200 | 896 ms | HTTP/1.1 | nginx/1.14.2 |
See the visual redirect chain in the HTTP Probe tab →
A+IPv6 ReadinessIPv6 reachable (17 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
User-agent: *
Disallow: *?replytocom
Allow: /
Disallow: /cl/
Disallow: /catalog/cl/
Disallow: /cn/
Disallow: /br/
Disallow: /catalog/br/
Disallow: /us/
Disallow: /mx/
Disallow: /catalog/mx/
Disallow: /co/
Disallow: /catalog/co/
Disallow: /pe/
Disallow: /catalog/pe/
Disallow: /1021178/AD
User-agent: AhrefsBot
Crawl-delay: 300
User-agent: msnbot
Crawl-delay: 10
Sitemap: https://www.archdaily.com/sitemap.xml
No sitemap found
Adding a sitemap helps search engines discover your pages.
A+Domain Intelligencearchdaily.com — via DreamHost, LLC, 18 years, 8 months oldPASS
127 days
November 20, 2026
136 days
Issued by Amazon
18 years, 8 months
Registered November 20, 2007
Not enabled
Protects against DNS spoofing
Unknown
2600:9000:204e:be00:4:2b2a:34c0:93a1
DreamHost, 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