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.
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
CCrawlabilityActionrobots.txt present, sitemap with 0 URLsREVIEW
Search engines may not be able to parse the sitemap. Fix XML validation errors.
An unparseable sitemap is silently ignored by Google — the URLs it advertises are never queued for crawl.
Learn more ▾ ▴
Google's sitemap parser is strict about XML validity. A single unescaped `&` or unclosed tag invalidates the whole file. Run your sitemap through a validator (Search Console's Sitemaps report flags it) and fix the offending entry. Most generators escape correctly; mistakes usually come from manually-written entries.
Source: sitemaps.org / Google Search Central
An empty sitemap provides no value. Add <url> entries for your pages.
An empty sitemap signals 'no content to index' to Google — actively harmful versus having no sitemap at all.
Learn more ▾ ▴
Google compares URLs in the sitemap against URLs it has crawled. An empty sitemap on a site with thousands of pages signals abandonment. Either populate it correctly (most CMSes auto-generate) or delete the file and let Google crawl normally.
Source: Google Search Central / sitemaps.org
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
User-agent: *
Disallow:
CURL VariantsActionwww/non-www, trailing slash, HTTP→HTTPSREVIEW
www / non-www
Inconsistent — duplicate content risk
HTTP → HTTPS
Use 301 (permanent) instead of 302 (temporary)
BTLS Certificate Expiry & Recommendations52 days until leaf cert expires — 4 issues to addressREVIEW
Certificate validity
Recommended actions
- Prefer TLS 1.3 — TLS 1.2 is acceptable but TLS 1.3 removes RSA key exchange and improves latency
- Submit your domain to hstspreload.org to be added to the Chrome preload list
- 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 Records1 A records, 145 ms lookupPASS
| A | 128.248.155.93 |
| AAAA | — |
| CNAME | — |
| NS | uic-dns2.uic.edu, uic-dns3.uic.edu, uic-dns1.uic.edu |
| MX | 10 uic-edu.mail.protection.outlook.com |
| TXT | notion-domain-verification=3UYmROFSWtEXb9pMsOESMg3suYQLzVibcXlFkdM7mbo airtable-verification=f5ab485517e406b932e08e766125f2b0 canva-site-verification=wi7y9f1U0xQffg1MOUAhnA brevo-code:35c986ca399ccc34813660f1bcb4ee24 ZOOM_verify_Et7PeOIQeaNFJGtukmqwqM d365mktkey=Dsu7EX4wt9bU6eHCxl9yb6Y4odjprWWu8xuyzAO0Nw8x brevo-code:909631822e346d28db914a25a31638d3 airtable-verification=70c446769cba9cec133577dea1ce6063 ZOOM_verify_hy5tbQ0syKMMFdwuTW0kRG Sendinblue-code:5984f9c1dd7d7ac012331f8dc7773bf6 mdt-site-verification=0c765af108bb0b059d2b2e82881ffba92d44fe0bf26aed738aeb3eea89... d365mktkey=ZF70t5zujud8evLGpDNN8RkeM1sVtfRUrrpqxxX3KVsx openai-domain-verification=dv-U1pC5jfvjVY5sWb9Ope46I7L google-site-verification=XmZQrIGyAoXlHgb_AqXS6cxZwCcfJHD6cZJe0sejyHw miro-verification=6f86b16dbd160af6f01c0846dc4d1144693d881a google-site-verification=FCePwUDiYhK6A6yTGUI6hHJwzbYRc2DCyGeuxA6hBuY facebook-domain-verification=dac2huk0r4m1x42kev4tnp5a56fq71 bw=GXDiP74viJCGoyBTQgyYph2uu6WxnWBVuylCMY4VZYeA atlassian-domain-verification=dlVw2u/HjFYH339/f2b1r4cainmyYM2L1ZblqRaEEjzcCkzTdY... atlassian-domain-verification=aqQt0HWqnOv3o2lycUVjLbORCxnZGa6/ZinSIfyuWUnQFIKmaF... atlassian-domain-verification=XWqRpTNOinCaGkItT0p0V9wnEs63Os1GTlZeEk7vTaFHddy3ej... atlassian-sending-domain-verification=35215dbd-8897-43f9-99d0-189c81bf006a cisco-ci-domain-verification=3f88ba67b4b75fe51b75bc6286efd0dfd954a799e141fd885e6... SPF v=spf1 include:spf.uic.edu ip4:192.17.86.0/24 ip4:128.174.180.0/24 ip4:64.22.178... |
| 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.
ARedirect Chain1 redirect(s), 337 ms totalPASS
https://uic.edu
139 ms · HTTP/1.1
https://www.uic.edu/
198 ms · HTTP/1.1 FINAL
| # | URL | Status | Time | Protocol | Server |
|---|---|---|---|---|---|
| 1 | https://uic.edu | 301 | 139 ms | HTTP/1.1 | nginx/1.27.2 |
| 2 | https://www.uic.edu/ | 200 | 198 ms | HTTP/1.1 | nginx/1.27.2 |
See the visual redirect chain in the HTTP Probe tab →
A+Domain Intelligenceuic.edu — 38 years, 8 months old, hosted on UIC-AS - University of Illinois Chicago, USPASS
745 days
July 31, 2028
52 days
Issued by Internet2
38 years, 8 months
Registered February 25, 1988
Status unknown
Protects against DNS spoofing
UIC-AS - University of Illinois Chicago, US
ASN AS6200
128.248.155.93
Registrar unknown