Infrastructure
· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.BRedirect Chain1 redirect(s), 1422 ms totalREVIEW
https://usenix.org
590 ms · HTTP/1.1
https://www.usenix.org/
832 ms · HTTP/1.1 FINAL
| # | URL | Status | Time | Protocol | Server |
|---|---|---|---|---|---|
| 1 | https://usenix.org | 301 | 590 ms | HTTP/1.1 | cloudflare |
| 2 | https://www.usenix.org/ | 200 | 832 ms | HTTP/1.1 | cloudflare |
See the visual redirect chain in the HTTP Probe tab →
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
#
# robots.txt
#
# This file is to prevent the crawling and indexing of certain parts
# of your site by web crawlers and spiders run by sites like Yahoo!
# and Google. By telling these "robots" where not to go on your site,
# you save bandwidth and server resources.
#
# This file will be ignored unless it is at the root of your host:
# Used: http://example.com/robots.txt
# Ignored: http://example.com/site/robots.txt
#
# For more information about the robots.txt standard, see:
# http://www.robotstxt.org/robotstxt.html
#
# For syntax checking, see:
# http://www.robotstxt.org/checker.html
User-agent: *
Crawl-delay: 10
# CSS, JS, Images
Allow: /core/misc/*.css$
Allow: /core/misc/*.css?
Allow: /core/misc/*.js$
Allow: /core/misc/*.js?
Allow: /core/misc/*.gif
Allow: /core/misc/*.jpg
Allow: /core/misc/*.jpeg
Allow: /core/misc/*.png
Allow: /core/modules/*.css$
Allow: /core/modules/*.css?
Allow: /core/modules/*.js$
Allow: /core/modules/*.js?
Allow: /core/modules/*.gif
Allow: /core/modules/*.jpg
Allow: /core/modules/*.jpeg
Allow: /core/modules/*.png
Allow: /core/profiles/*.css$
Allow: /core/profiles/*.css?
Allow: /core/profiles/*.js$
Allow: /core/profiles/*.js?
Allow: /core/profiles/*.gif
Allow: /core/profiles/*.jpg
Allow: /core/profiles/*.jpeg
Allow: /core/profiles/*.png
Allow: /core/themes/*.css$
Allow: /core/themes/*.css?
Allow: /core/themes/*.js$
Allow: /core/themes/*.js?
Allow: /core/themes/*.gif
Allow: /core/themes/*.jpg
Allow: /core/themes/*.jpeg
Allow: /core/themes/*.png
# Directories
Disallow: /core/
Disallow: /profiles/
# Files
Disallow: /README.md
Disallow: /web.config
# Paths (clean URLs)
Disallow: /admin
Disallow: /comment/reply
Disallow: /filter/tips
Disallow: /node/add
Disallow: /publications/proceedings
Disallow: /search
Disallow: /semantic-views-demo
Disallow: /user/register
Disallow: /user/password
Disallow: /user/login
Disallow: /user/logout
# Paths (no clean URLs)
Disallow: /?q=admin
Disallow: /?q=comment/reply
Disallow: /?q=filter/tips
Disallow: /?q=node/add
Disallow: /?q=publications/proceedings
Disallow: /?q=search
Disallow: /?q=semantic-views-demo
Disallow: /?q=user/password
Disallow: /?q=user/register
Disallow: /?q=user/login
Disallow: /?q=user/logout
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 & Recommendations34 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 Records2 A records, 31 ms lookupPASS
| A | 172.67.159.52, 104.21.9.67 |
| AAAA | 2606:4700:3034::ac43:9f34, 2606:4700:3033::6815:943 |
| CNAME | — |
| NS | amalia.ns.cloudflare.com, duke.ns.cloudflare.com |
| MX | 1 aspmx.l.google.com 5 alt1.aspmx.l.google.com 5 alt2.aspmx.l.google.com 5 aspmx2.googlemail.com 10 aspmx3.googlemail.com |
| TXT | sophos-domain-verification=a57c5be5f56331d9aa0762c379ced2559c2ab6e13189020ae0cd5... MS=ms35918051 MS=ms74434625 SPF v=spf1 include:%{i}._ip.%{h}._ehlo.%{d}._spf.vali.email ~all MS=1C9777014BBA1311A8D73006D88E8171BD2C45F1 apple-domain-verification=pMupuJTB7hD1o7CP google-site-verification=NWZh1b4m1muqzcGTUY41ERnLVVU1U0nU1knFu0v-Y5g facebook-domain-verification=k4ln5v10rpbl30ycqf3adsmx5wdxer 1password-site-verification=A4FZ5FEBIBGCJIZETBURXRBIF4 jamf-site-verification=9jpXV9Kj0zUc4Hmh7xQhBA |
| 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.
A+IPv6 ReadinessIPv6 reachable (16 ms)PASS
A+Domain Intelligenceusenix.org — via easyDNS Technologies Inc., 39 years, 4 months oldPASS
359 days
July 13, 2027
34 days
Issued by Google Trust Services
39 years, 4 months
Registered July 14, 1987
Not enabled
Protects against DNS spoofing
Unknown
2606:4700:3033::6815:943
easyDNS Technologies Inc.
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