Skip to content
https://tulane.edu

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
98
GRADE
A+
FIX
0
REVIEW
1
PASS
8
INFO
0
Probed from Madrid, Spain
200 OK
Checks
9
8 PASS 1 REVIEW
B
TLS Certificate Expiry & Recommendations
73 days until leaf cert expires — 5 issues to address
REVIEW

Certificate validity

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

Recommended actions

  • 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 Records
1 A records, 110 ms lookup
PASS
1 A records, 110 ms lookup
Info::
Resolves to 1 IPv4 address(es)
Got: 23.185.0.3
Info::
Single A record — no DNS redundancy
Multiple A records provide failover if one server goes down.
Info::
Has 2 IPv6 (AAAA) record(s)
Got: 2620:12a:8001::3, 2620:12a:8000::3
Info::
2 nameserver(s) configured
Got: megan.ns.cloudflare.com, ram.ns.cloudflare.com
Info::
1 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: 110 ms
Got: 110 ms
A23.185.0.3
AAAA2620:12a:8001::3, 2620:12a:8000::3
CNAME
NSmegan.ns.cloudflare.com, ram.ns.cloudflare.com
MX
0 tulane-edu.mail.protection.outlook.com
TXT
docusign=fad22bc9-0fc9-4933-9ae9-1b1760a20bf6
google-site-verification=UEAHp3baz1L_7btnv6H62BhtaH3voFZSYJcAUfwUbTE
d365mktkey=eIQ26eq0eX6AhUFnK6qzx01vrjlfFPQaEa1Z9wmpZM0x
docusign=34fd4f96-1489-4115-be61-0be4196d0f57
e2ma-verification=qr7eb
e2ma-verification=xj4fb
adobe-sign-verification=ac81dd89620ad923f21772b12c8a5dc
google-site-verification=kq0_3cWV871zP3J9dSs8pwQn6TPOG6fr80Tkq2KDu_0
d365mktkey=t9bj2oYxcWviVFcRJYkBjgYRzJZMX68xFPa2dxpmxx0x
atlassian-domain-verification=PWQo3wE63rhd0f1Q3j7tSobcdUESwH6eSiDthJPRD84UDW7TsQ...
docusign=349fbe8b-660f-4ea2-be35-3b0fc7046426
e2ma-verification=fqxeb
ZOOM_verify_j69jJkbWE4ry8IkWdUO6qi
rhino_accounts=bbe43d6f6a891dbac526b504e3c35f91
MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQC16vMJZRGjBGzpJKo/UvKEUg6/rBIjJplOdaLUft3A...
intersight=96cf5c1c5eca7b695a1069e8940a63c4473c6bf2ba0111be347aa43471a18c47
amazonses:bo6UOJuBKw6HOMmyavF7aY30YGwflHWCBtML4Qd0TnM=
jamf-site-verification=bfagen8Z8SUAMfQ47_0XrA
google-site-verification=LSUWqTnn0ZlVl9Sg1ybOiR6CcV9Jm5PsITtzyU_ALSI
SPF v=spf1 include:spf.protection.outlook.com include:mail.zendesk.com include:_u.tu...
PYWWE54OG8QNUSEJO8NMKFV2ITK8Z268FK9CQ1ZIO
airtable-manual-domain-verification=c5fd33f0-ef0e-4bb5-a994-0f9e9f7559ec
google-site-verification=rQ_SYjtcHsIgEKFRW9iLT6O5XMf5Nnf2DCF0lHa-12w
atlassian-sending-domain-verification=71e1dc47-a790-4122-b26b-8944f64cd020
onetrust-domain-verification=a4d531cde7154b5ca91bb3d5ffe5e12a
ALVTSPCD=e10675237d256218439f464843e2e85364a73cc8
CAALookup not available with standard resolver
Resolved in 110 ms

Multiple A records provide failover if one server goes down.

Why this matters

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.

Why this matters

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

A+
Redirect Chain
No redirects — direct access
PASS
No redirects — direct access
Info::
No redirects — direct access
Got: https://tulane.edu

https://tulane.edu

7 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://tulane.edu2007 msHTTP/1.1nginx
A+
IPv6 Readiness
IPv6 reachable (0 ms)
PASS
IPv6 reachable (0 ms)
Info::
IPv6 is configured and reachable at 2620:12a:8001::3, 2620:12a:8000::3
Got: 0 ms connect
IPv6 Ready
AAAA Records 2620:12a:8001::3, 2620:12a:8000::3 Connection Reachable (0 ms)
A+
Crawlability
robots.txt present, sitemap with 188 URLs
PASS
robots.txt present, sitemap with 188 URLs
Info::
robots.txt is present
Got: 2027 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 188 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 2027 B Sitemaps referenced 0 User-agents * Blocking No — crawling allowed
#
# 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

User-agent: *
# CSS, JS, Images
Allow: /core/*.css$
Allow: /core/*.css?
Allow: /core/*.js$
Allow: /core/*.js?
Allow: /core/*.gif
Allow: /core/*.jpg
Allow: /core/*.jpeg
Allow: /core/*.png
Allow: /core/*.svg
Allow: /profiles/*.css$
Allow: /profiles/*.css?
Allow: /profiles/*.js$
Allow: /profiles/*.js?
Allow: /profiles/*.gif
Allow: /profiles/*.jpg
Allow: /profiles/*.jpeg
Allow: /profiles/*.png
Allow: /profiles/*.svg
# Directories
Disallow: /core/
Disallow: /profiles/
# Files
Disallow: /README.md
Disallow: /composer/Metapackage/README.txt
Disallow: /composer/Plugin/ProjectMessage/README.md
Disallow: /composer/Plugin/Scaffold/README.md
Disallow: /composer/Plugin/VendorHardening/README.txt
Disallow: /composer/Template/README.txt
Disallow: /modules/README.txt
Disallow: /sites/README.txt
Disallow: /themes/README.txt
Disallow: /web.config
# Paths (clean URLs)
Disallow: /admin/
Disallow: /comment/reply/
Disallow: /filter/tips
Disallow: /node/add/
Disallow: /search/
Disallow: /user/register
Disallow: /user/password
Disallow: /user/login
Disallow: /user/logout
Disallow: /media/oembed
Disallow: /*/media/oembed
# Paths (no clean URLs)
Disallow: /index.php/admin/
Disallow: /index.php/comment/reply/
Disallow: /index.php/filter/tips
Disallow: /index.php/node/add/
Disallow: /index.php/search/
Disallow: /index.php/user/password
Disallow: /index.php/user/register
Disallow: /index.php/user/login
Disallow: /index.php/user/logout
Disallow: /index.php/media/oembed
Disallow: /index.php/*/media/oembed

A+
URL Variants
www/non-www, trailing slash, HTTP→HTTPS
PASS
www/non-www, trailing slash, HTTP→HTTPS
Info::
www/non-www redirect configured correctly (preferred: non-www)
Info::
HTTP correctly 301-redirects to HTTPS

www / non-www

301https://www.tulane.edu/
200https://tulane.edu/

Preferred variant: non-www

HTTP → HTTPS

301http://tulane.edu/ https://tulane.edu/

Consistent

A+
Domain Intelligence
tulane.edu — 39 years, 7 months old
PASS
tulane.edu — 39 years, 7 months old
Info::
Domain registered until Jul 31, 2028 (2 years, 3 months remaining)
Domain expiry

750 days

July 31, 2028

SSL certificate

73 days

Issued by Let's Encrypt

Domain age

39 years, 7 months

Registered April 14, 1987

DNSSEC

Status unknown

Protects against DNS spoofing

Hosting

Unknown

2620:12a:8000::3

Registrar

Registrar unknown

Lock status unknown 2 NS records
Expiry timeline
Today
+1 year
Domain expiry SSL expiry Danger zone (≤30 days)
Registrar
Created April 14, 1987 (39 years, 7 months ago)
Expires July 31, 2028 (2 years, 3 months)
Last Updated October 29, 2025
Name Servers megan.ns.cloudflare.com, ram.ns.cloudflare.com
Registrant Tulane University
Hosting
IP Address 2620:12a:8000::3
Data source: whois (0.8s)
A+
HTTP Probe Timing
Total 43 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
PASS
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
38 ms
TCP Connect TCP Connect — time to establish a TCP connection to the server.
0 ms
TLS Handshake TLS Handshake — time to complete the HTTPS encryption handshake.
3 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
43 ms
Total Time Total request time from DNS lookup through full response.
44 ms

Connection waterfall

DNS Lookup 38 ms TCP Connect 0 ms TLS Handshake 3 ms Server Processing 2 ms Content Transfer 1 ms
A+
CDN & Delivery
Fastly (HIT, HIT)
PASS
Fastly (HIT, HIT)
Info::
Site is served via Fastly CDN
Got: x-served-by: cache-chi-kigq8000169-CHI, cache-toj-leto2350068-TOJ
Info::
CDN cache status: HIT, HIT
CDN Detected: Fastly
Provider Fastly Cache Status HIT, HIT Evidence x-served-by: cache-chi-kigq8000169-CHI, cache-toj-leto2350068-TOJ
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback