Skip to content
https://udel.edu

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
83
GRADE
B
FIX
1
REVIEW
4
PASS
4
INFO
0
Probed from Madrid, Spain
302 Found
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: 71 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 71 B Sitemaps referenced 0 User-agents * Blocking No — crawling allowed
User-Agent: *
Disallow: /dam/udelImages/student-life/reslife/floorplans
sitemap.xml No sitemap found

No sitemap found

Adding a sitemap helps search engines discover your pages.

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.udel.edu/
200https://udel.edu/

Inconsistent — duplicate content risk

HTTP → HTTPS

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

Consistent

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

Certificate validity

150
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, 111 ms lookup
PASS
1 A records, 111 ms lookup
Info::
Resolves to 1 IPv4 address(es)
Got: 128.175.13.247
Info::
Single A record — no DNS redundancy
Multiple A records provide failover if one server goes down.
Info::
No IPv6 (AAAA) records
Info::
5 nameserver(s) configured
Got: adns2.nnn.upenn.edu, adns3.nnn.upenn.edu, dns2.udel.edu, adns1.nnn.upenn.edu, dns1.udel.edu
Info::
7 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: 111 ms
Got: 111 ms
A128.175.13.247
AAAA—
CNAME—
NSadns2.nnn.upenn.edu, adns3.nnn.upenn.edu, dns2.udel.edu, adns1.nnn.upenn.edu, dns1.udel.edu
MX
10 aspmx.l.google.com
20 alt1.aspmx.l.google.com
20 alt2.aspmx.l.google.com
30 aspmx5.googlemail.com
30 aspmx2.googlemail.com
30 aspmx3.googlemail.com
30 aspmx4.googlemail.com
TXT
apple-domain-verification=5n78usXJfZ0vgTey
atlassian-sending-domain-verification=41dba828-b297-4b7c-bafe-a2ccf4d25f2b
URu4AGWOcDvKe4PwSDHvdS762TlVseaVc+du0jd4Gv3vIq0YI3VUuJ/6eTiiAxqSEfU4P7imWQeO7jWK...
MS=ms22927527
SPF v=spf1 ip4:128.175.0.0/16 ip4:128.4.0.0/16 ip4:216.52.6.88 ip4:216.52.6.188 ip4:...
atlassian-domain-verification=kG5tMbcO4mksxqW6e8BuXdMh5ZfICECWRBFNGQYAp9BJNVUWHy...
sending_domain1080123=dcdd9207f11fd0a6c2ef603dc43fa59e33707821671c9616c6587b550d...
iCAuIRbjTdvds2zAtzMRfrlOF/PjOQmGhPXSNyhAd0Tqum3hGk8R9kXUAJqvsHTlLujXmlAtKC2b/Kqa...
pardot1080123=37ec00bb9c8c1b3c5165ed96c9e2a52482eef50ee2518a4d9523f82b32ecc241
CAALookup not available with standard resolver
Resolved in 111 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
1 redirect(s), 941 ms total
PASS
1 redirect(s), 941 ms total
Info::
Single redirect
Got: https://udel.edu → https://www.udel.edu/ (302)
Info::
WWW normalization redirect
Info::
Uses 302 (temporary) redirect
If permanent, use 301 instead.
Got: https://udel.edu
Info::
Redirect overhead: 941 ms total
Got: 941 ms

https://udel.edu

304 ms · HTTP/1.1

302

https://www.udel.edu/

637 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://udel.edu302304 msHTTP/1.1Apache/2.4.37 (Rocky Linux) OpenSSL/1.1.1k
2https://www.udel.edu/200637 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+
Domain Intelligence
udel.edu — 41 years, 4 months old, hosted on UDELNET - University of Delaware, US
PASS
udel.edu — 41 years, 4 months old, hosted on UDELNET - University of Delaware, US
Info::
Domain registered until Jul 31, 2027 (1 years, 3 months remaining)
Info::
Hosting: UDELNET - University of Delaware, US
Got: AS34
Domain expiry

410 days

July 31, 2027

SSL certificate

150 days

Issued by GlobalSign nv-sa

Domain age

41 years, 4 months

Registered July 24, 1985

DNSSEC

Status unknown

Protects against DNS spoofing

Hosting

UDELNET - University of Delaware, US

ASN AS34

128.175.13.247

Registrar

Registrar unknown

Lock status unknown 5 NS records
Expiry timeline
Today
+1 year
Domain expiry SSL expiry Danger zone (≤30 days)
Registrar
Created July 24, 1985 (41 years, 4 months ago)
Expires July 31, 2027 (1 years, 3 months)
Last Updated June 4, 2024
Name Servers adns3.nnn.upenn.edu, adns1.nnn.upenn.edu, adns2.nnn.upenn.edu, dns1.udel.edu, dns2.udel.edu
Registrant University of Delaware
Hosting
IP Address 128.175.13.247
ASN AS34 (UDELNET - University of Delaware, US)
Provider UDELNET - University of Delaware, US
Data source: whois (0.9s)
A
HTTP Probe Timing
Total 417 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
PASS
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
104 ms
TCP Connect TCP Connect — time to establish a TCP connection to the server.
102 ms
TLS Handshake TLS Handshake — time to complete the HTTPS encryption handshake.
109 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
418 ms
Total Time Total request time from DNS lookup through full response.
418 ms

Connection waterfall

DNS Lookup 104 ms TCP Connect 102 ms TLS Handshake 109 ms Server Processing 102 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