Skip to content
https://brandeis.edu

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
86
GRADE
B
FIX
1
REVIEW
3
PASS
5
INFO
0
Probed from Amsterdam, Netherlands
302 Found
Checks
9
5 PASS 3 REVIEW 1 FIX
D
CDN & Delivery
Action
No CDN detected
FIX
No CDN detected
Warning::
No CDN detected
A CDN can significantly improve load times for users around the world by caching content at edge nodes closer to them.
No CDN detected

Consider using a CDN to improve global delivery speed and reduce origin load.

C
IPv6 Readiness
Action
No IPv6 support
REVIEW
No IPv6 support
Info::
No IPv6 (AAAA) records found
IPv6 support is increasingly important for global accessibility. About 40% of internet users have IPv6 connectivity.
No IPv6 Support
About 40% of internet users have IPv6. Consider adding AAAA records.

IPv6 support is increasingly important for global accessibility. About 40% of internet users have IPv6 connectivity.

Why this matters

No AAAA records — same impact as 'no IPv6 (AAAA) records'; IPv6-preferring clients pay extra latency falling back to IPv4.

Source: Google IPv6 stats

B
URL Variants
www/non-www, trailing slash, HTTP→HTTPS
REVIEW
www/non-www, trailing slash, HTTP→HTTPS
Critical::
Both www and non-www versions serve content
Got: Both variants return 200 Expected: One variant 301-redirects to the other
Info::
HTTP correctly 301-redirects to HTTPS

www / non-www

200https://www.brandeis.edu/
200https://brandeis.edu/

Inconsistent — duplicate content risk

HTTP → HTTPS

301http://brandeis.edu/ → https://brandeis.edu:443/

Consistent

B
TLS Certificate Expiry & Recommendations
185 days until leaf cert expires — 4 issues to address
REVIEW

Certificate validity

185
days left
0d 30d 60d 90d+

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 Records
2 A records, 12 ms lookup
PASS
2 A records, 12 ms lookup
Info::
Resolves to 2 IPv4 address(es)
Got: 13.248.151.114, 76.223.22.0
Info::
No IPv6 (AAAA) records
Info::
7 nameserver(s) configured
Got: ns-1198.awsdns-21.org, ns-1349.awsdns-40.org, ns-1678.awsdns-17.co.uk, ns-1953.awsdns-52.co.uk, ns-21.awsdns-02.com, ns-622.awsdns-13.net, ns-852.awsdns-42.net
Info::
2 mail exchanger(s) configured
Info::
CAA records not checked
CAA record lookup requires a specialized DNS resolver. This check will be available in a future update.
Info::
SPF record present in TXT
Info::
DNS resolution time: 12 ms
Got: 12 ms
A13.248.151.114, 76.223.22.0
AAAA—
CNAME—
NSns-1198.awsdns-21.org, ns-1349.awsdns-40.org, ns-1678.awsdns-17.co.uk, ns-1953.awsdns-52.co.uk, ns-21.awsdns-02.com, ns-622.awsdns-13.net, ns-852.awsdns-42.net
MX
10 mxb-002d6a01.gslb.pphosted.com
10 mxa-002d6a01.gslb.pphosted.com
TXT
ZOOM_verify_atyj8r3uRJaTgpvPCRcpXw
adobe-idp-site-verification=ccb8f93b-7377-48b5-912b-524b649319b5
apple-domain-verification=iWmG0RdEjGLD5NE5
cisco-ci-domain-verification=452172cfe20cac084c5f57fa757c2e1ffcaf78aced9dc2ad57d...
google-site-verification=LZGrmGTjU0m4L8a06t1IGWRF99nH2Y2vcxMLZO-jpiU
pardot884863=9b12168d378a340a39313fd8351d16379f30d67388ed333b477013dab8ada244
pardot884863=bdf69fe374739180421aee9129b4faa07d000bab10e8c48cc94d9fe4093f7bc7
pardot960012=1d76a06ec56ebb6dd2644031e62db71d5b55b3c3ba7a9cff65468fa9531ad2ca
pardot960012=747ba153c1dec8ff21b5dd034a1909f14e9e664dfa6e292604dda2d7c2bfb467
sending_domain960012=8c14fc32ec1596dc18ecc3926dbc59758c775013815e0bde5bf832d6b16...
status-page-domain-verification=tgjcp68x25sn
SPF v=spf1 mx ip4:129.64.0.0/17 ip4:129.64.252.160/28 include:_spf.google.com includ...
CAALookup not available with standard resolver
Resolved in 12 ms

CAA record lookup requires a specialized DNS resolver. This check will be available in a future update.

Why this matters

Informational: CAA (Certification Authority Authorization) records weren't checked in this scan.

A
Redirect Chain
1 redirect(s), 704 ms total
PASS
1 redirect(s), 704 ms total
Info::
Single redirect
Got: https://brandeis.edu → https://www.brandeis.edu/ (302)
Info::
WWW normalization redirect
Info::
Uses 302 (temporary) redirect
If permanent, use 301 instead.
Got: https://brandeis.edu
Info::
Redirect overhead: 704 ms total
Got: 704 ms

https://brandeis.edu

344 ms · HTTP/1.1

302

https://www.brandeis.edu/

360 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://brandeis.edu302344 msHTTP/1.1Apache
2https://www.brandeis.edu/200360 msHTTP/1.1Apache

See the visual redirect chain in the HTTP Probe tab →

If permanent, use 301 instead.

Why this matters

302 (Found) is for genuinely temporary redirects — if this redirect is permanent, switch to 301 to preserve SEO equity.

Learn more ▾

Search engines treat 302 as temporary, keeping the original URL indexed and not transferring full link equity to the destination. Use 301 (Moved Permanently) for permanent redirects (HTTP→HTTPS, www-vs-non-www, URL restructures).

Source: Google Search Central

A+
Crawlability
robots.txt present, sitemap with 17020 URLs
PASS
robots.txt present, sitemap with 17020 URLs
Info::
robots.txt is present
Got: 496 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 17020 entries
Info::
robots.txt does not reference a sitemap
Add a 'Sitemap:' directive to robots.txt so search engines can discover your sitemap.

Add a 'Sitemap:' directive to robots.txt so search engines can discover your sitemap.

Why this matters

robots.txt omits Sitemap: directive — crawlers must fetch /sitemap.xml by convention; reliable but missing the explicit hint.

Source: sitemaps.org

robots.txt 200 OK
Size 496 B Sitemaps referenced 0 User-agents * Blocking No — crawling allowed
User-agent: *
Disallow: /noshoes.html
Disallow: /home-zeta/index-newflash.html
Disallow: /addresses
Disallow: /webservices/temp/
Disallow: /webservices/archive/
Disallow: /search/
Disallow: /registrar/schedule/search.php
Disallow: /registrar/schedule/pre-schedule.php
Disallow: /registrar/schedule/cur-schedule.php
Disallow: /registrar/schedule/future-schedule.php
Disallow: /registrar/schedule/stats.php
Disallow: /directory/
Disallow: /registrar/bulletin/provisional/arts-sciences/tuition.html
sitemap.xml 200 OK
Type URL Set URLs 17020 entries Valid XML Yes
Sample URLs:
A+
Domain Intelligence
brandeis.edu — 39 years, 5 months old, hosted on AWS
PASS
brandeis.edu — 39 years, 5 months old, hosted on AWS
Info::
Domain registered until Jul 31, 2026 (3 months remaining)
Info::
Hosting: AWS
Got: AS16509
Domain expiry

45 days

July 31, 2026

SSL certificate

185 days

Issued by Amazon

Domain age

39 years, 5 months

Registered May 27, 1987

DNSSEC

Status unknown

Protects against DNS spoofing

Hosting

AWS

ASN AS16509

13.248.151.114

Registrar

Registrar unknown

Lock status unknown 4 NS records
Expiry timeline
Today
+1 year
Domain expiry SSL expiry Danger zone (≤30 days)
Recommended actions
  • Renew the domain or enable auto-renewal to prevent accidental expiry
Registrar
Created May 27, 1987 (39 years, 5 months ago)
Expires July 31, 2026 (3 months)
Last Updated July 15, 2025
Name Servers ns-21.awsdns-02.com, ns-1198.awsdns-21.org, ns-1953.awsdns-52.co.uk, ns-852.awsdns-42.net
Registrant Brandeis University
Hosting
IP Address 13.248.151.114
ASN AS16509 (AMAZON-02 - Amazon.com, Inc., US)
Provider AWS
Data source: whois (0.6s)
A+
HTTP Probe Timing
Total 341 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
PASS
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
6 ms
TCP Connect TCP Connect — time to establish a TCP connection to the server.
1 ms
TLS Handshake TLS Handshake — time to complete the HTTPS encryption handshake.
250 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
342 ms
Total Time Total request time from DNS lookup through full response.
342 ms

Connection waterfall

DNS Lookup 6 ms TCP Connect 1 ms TLS Handshake 250 ms Server Processing 84 ms Content Transfer 0 ms
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback