Skip to content
https://drexel.edu

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
89
GRADE
B
FIX
1
REVIEW
4
PASS
4
INFO
0
Probed from Madrid, Spain
200 OK
Checks
9
4 PASS 4 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
Crawlability
robots.txt present, no sitemap
REVIEW
robots.txt present, no sitemap
Info::
robots.txt is present
Got: 588 bytes
Info::
No sitemap.xml found
A sitemap helps search engines discover and index your pages more efficiently.
Info::
robots.txt does not reference a sitemap
Add a 'Sitemap:' directive to robots.txt so search engines can discover your sitemap.

A sitemap helps search engines discover and index your pages more efficiently.

Why this matters

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.

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 588 B Sitemaps referenced 0 User-agents Amazonbot, * Blocking No — crawling allowed
User-agent: Amazonbot

Disallow: /


User-Agent: *

Disallow: /search

Disallow: /*/search

Disallow: /search/*

Disallow: /*/search/*

Disallow: /coas/search

Disallow: /api/du/search

Disallow: /siteSearch/

Disallow: /Search

Disallow: /*/Search

Disallow: /Search/*

Disallow: /*/Search/*

Disallow: /coas/Search

Disallow: /api/du/Search

Disallow: /SiteSearch/

Disallow: /SEARCH

Disallow: /*/SEARCH

Disallow: /SEARCH/*

Disallow: /*/SEARCH/*

Disallow: /coas/SEARCH

Disallow: /api/du/SEARCH

Disallow: /SITESEARCH/

Disallow: /sitecore

Disallow: /Sitecore

Disallow: /SITECORE
sitemap.xml No sitemap found

No sitemap found

Adding a sitemap helps search engines discover your pages.

B
HTTP Probe Timing
Total 1394 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
REVIEW
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
105 ms
TCP Connect TCP Connect — time to establish a TCP connection to the server.
97 ms
TLS Handshake TLS Handshake — time to complete the HTTPS encryption handshake.
103 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
618 ms
Total Time Total request time from DNS lookup through full response.
1.39 s

Connection waterfall

DNS Lookup 105 ms TCP Connect 97 ms TLS Handshake 103 ms Server Processing 313 ms Content Transfer 777 ms
B
TLS Certificate Expiry & Recommendations
179 days until leaf cert expires — 4 issues to address
REVIEW

Certificate validity

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

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 Records
1 A records, 113 ms lookup
PASS
1 A records, 113 ms lookup
Info::
Resolves to 1 IPv4 address(es)
Got: 144.118.67.10
Info::
Single A record — no DNS redundancy
Multiple A records provide failover if one server goes down.
Info::
No IPv6 (AAAA) records
Info::
2 nameserver(s) configured
Got: adns2.drexel.edu, adns1.drexel.edu
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: 113 ms
Got: 113 ms
A144.118.67.10
AAAA—
CNAME—
NSadns2.drexel.edu, adns1.drexel.edu
MX
10 drexel-edu.mail.protection.outlook.com
TXT
SPF v=spf1 include:%{i}._ip.%{h}._ehlo.%{d}._spf.vali.email include:mh.blackboard.co...
autodesk-domain-verification=FbJaxOCP5sTzVaRp8iLk
SFMC-kDdEV_OGWRvXtrrOvjSfLl_UvbJCYnyPVwyy6J-7
MS=ms70249944
atlassian-sending-domain-verification=e4c1eaa4-a548-4f1e-bce8-fcc857804d2a
d365mktkey=pm597a42hcczvf75jjtwcsze
apple-domain-verification=lzuoLwvsJzc0ZnCI
e2ma-verification=bv5fb
amazonses:F/rQC8NnKM3UF5CbKxcEgJUYNkJrTgRNWCRRzMKobfg=
adobe-idp-site-verification=5d032466012e98beaa9e6b954f03418d262606d7dff63bfec9c1...
0PONam/FUfNp7i8qu5r91iP+FHF8WTulERFqlydzrB8U6UfqWPJlBf61JEGpVyq+0IoaeQkiB3YvhMEx...
openai-domain-verification=dv-KqN598cZsmVksZ1fZIqDmiJA
d365mktkey=2bbe0ncw2ae7c8nlobwaeq6m7
CAALookup not available with standard resolver
Resolved in 113 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://drexel.edu

https://drexel.edu

713 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://drexel.edu200713 msHTTP/1.1
A+
URL Variants
www/non-www, trailing slash, HTTP→HTTPS
PASS
www/non-www, trailing slash, HTTP→HTTPS
Info::
HTTP correctly 301-redirects to HTTPS

www / non-www

https://www.drexel.edu/
200https://drexel.edu/

HTTP → HTTPS

301http://drexel.edu/ → https://drexel.edu/

Consistent

A+
Domain Intelligence
drexel.edu — 38 years, 9 months old, hosted on DREXEL-ASN - Drexel University, US
PASS
drexel.edu — 38 years, 9 months old, hosted on DREXEL-ASN - Drexel University, US
Info::
Domain registered until Jul 31, 2027 (1 years, 3 months remaining)
Info::
Hosting: DREXEL-ASN - Drexel University, US
Got: AS11834
Domain expiry

412 days

July 31, 2027

SSL certificate

179 days

Issued by Internet2

Domain age

38 years, 9 months

Registered February 8, 1988

DNSSEC

Status unknown

Protects against DNS spoofing

Hosting

DREXEL-ASN - Drexel University, US

ASN AS11834

144.118.67.10

Registrar

Registrar unknown

Lock status unknown 2 NS records
Expiry timeline
Today
+1 year
Domain expiry SSL expiry Danger zone (≤30 days)
Registrar
Created February 8, 1988 (38 years, 9 months ago)
Expires July 31, 2027 (1 years, 3 months)
Last Updated July 8, 2024
Name Servers adns1.drexel.edu, adns2.drexel.edu
Registrant Drexel University
Hosting
IP Address 144.118.67.10
ASN AS11834 (DREXEL-ASN - Drexel University, US)
Provider DREXEL-ASN - Drexel University, US
Data source: whois (0.9s)
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback