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), 1257 ms totalREVIEW
https://rutgers.edu
548 ms · HTTP/1.1
https://www.rutgers.edu/
709 ms · HTTP/1.1 FINAL
| # | URL | Status | Time | Protocol | Server |
|---|---|---|---|---|---|
| 1 | https://rutgers.edu | 302 | 548 ms | HTTP/1.1 | |
| 2 | https://www.rutgers.edu/ | 200 | 709 ms | HTTP/1.1 | nginx/1.12.2 |
See the visual redirect chain in the HTTP Probe tab →
If permanent, use 301 instead.
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
CIPv6 ReadinessActionNo IPv6 supportREVIEW
IPv6 support is increasingly important for global accessibility. About 40% of internet users have IPv6 connectivity.
No AAAA records — same impact as 'no IPv6 (AAAA) records'; IPv6-preferring clients pay extra latency falling back to IPv4.
Source: Google IPv6 stats
BURL Variantswww/non-www, trailing slash, HTTP→HTTPSREVIEW
www / non-www
Inconsistent — duplicate content risk
HTTP → HTTPS
Consistent
BTLS Certificate Expiry & Recommendations162 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
ADNS Records1 A records, 161 ms lookupPASS
| A | 128.6.82.29 |
| AAAA | — |
| CNAME | — |
| NS | ns1.rutgers.edu, ns6.dnsmadeeasy.com, ns5.dnsmadeeasy.com, runs2.rutgers.edu, ns7.dnsmadeeasy.com |
| MX | 10 mx2.rutgers.edu 10 mx2kb.rutgers.edu |
| TXT | cisco-ci-domain-verification=420d80e8cad072010212486ea398d1347c3bccbfc861c33ce64... ZOOM_verify_aVexM4cQQqSH-y-2irswNg smartsheet-site-validation=Eg14sT1HmnvMeG7DwWs8o-BcUE77ym1x facebook-domain-verification=cpbqm6wfj2xixv4oj6ztg3dp4pcupg klaviyo-site-verification=SGwc3U klaviyo-site-verification=YiWL4U google-site-verification=n_ksBYYay2p9_3lPEKBnW-OrnkIxOD1jyu53ZeNFp_w atlassian-domain-verification=0JEWwucVWsqYpPvZyPTyNYGnL0kfnEjabbGXvPlueWPXh9e/ey... atlassian-domain-verification=h3OHpvFP/BT1l56DvZRkNgSGTPLMerO8riQo6uXRZn9/PGvYfa... graphpad.com:domain-verification=J-wC-W8JyYzGNswWs63PyA sj35th8fmsss9h43er8tlk8kop anthropic-domain-verification-ajcvse=YdGyd3ARqp5N9J9lesyBfLpOv abuseipdb-verification=AwWTkbmR docusign=add3baaa-240f-4cb9-8b97-f97ee0a191f0 docusign=acda1f44-e204-43a7-9bf4-4942f6f62ad8 docusign=c39f311c-ede0-4045-b551-b6f049cefec0 apple-domain-verification=73WjNAUVKdqIsYLK |
| 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.
SPF helps prevent email spoofing. Add a TXT record starting with 'v=spf1'.
Without SPF, receiving servers can't validate sending IPs — your domain is easier to spoof in phishing.
Learn more ▾ ▴
SPF complements DMARC. Both should be published. SPF records list authorized sending IPs (e.g., `v=spf1 include:_spf.google.com ~all` for Google Workspace). After publishing, verify in Google Postmaster Tools or mxtoolbox.
Source: RFC 7208 (SPF)
A+Crawlabilityrobots.txt present, sitemap with 6 URLsPASS
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
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+Domain Intelligencerutgers.edu — 41 years, 7 months old, hosted on RUTGERS - Rutgers, The State University, USPASS
EXPIRED
July 31, 2026
162 days
Issued by Internet2
41 years, 7 months
Registered April 25, 1985
Status unknown
Protects against DNS spoofing
RUTGERS - Rutgers, The State University, US
ASN AS46
128.6.82.29
Registrar unknown
Expiry timeline
Recommended actions
- Domain has EXPIRED — renew immediately to avoid total site outage