Skip to content
https://nyu.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
3
PASS
5
INFO
0
Probed from Madrid, Spain
302 Found
Checks
9
5 PASS 3 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
no robots.txt, no sitemap
REVIEW
no robots.txt, no sitemap
Info::
No robots.txt found
robots.txt is optional but recommended. It tells search engine crawlers which pages to index.
Info::
No sitemap.xml found
A sitemap helps search engines discover and index your pages more efficiently.

robots.txt is optional but recommended. It tells search engine crawlers which pages to index.

Why this matters

No robots.txt — crawlers fetch /robots.txt and get 404; not breaking but means default crawl behavior with no directives or sitemap reference.

Learn more ▾

A minimal robots.txt with `User-agent: * / Allow: / / Sitemap: https://example.com/sitemap.xml` covers the basics. Without it, crawlers behave fine but lose the sitemap signal and can't be selectively blocked from crawl-traps.

Source: robotstxt.org

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

robots.txt No robots.txt found

No robots.txt found

This is fine for most sites — a missing robots.txt allows all crawling by default.

sitemap.xml No sitemap found

No sitemap found

Adding a sitemap helps search engines discover your pages.

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

Certificate validity

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

Recommended actions

  • Prefer TLS 1.3 — TLS 1.2 is acceptable but TLS 1.3 removes RSA key exchange and improves latency
  • 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
A
DNS Records
1 A records, 296 ms lookup
PASS
1 A records, 296 ms lookup
Info::
Resolves to 1 IPv4 address(es)
Got: 216.165.61.24
Info::
Single A record — no DNS redundancy
Multiple A records provide failover if one server goes down.
Info::
No IPv6 (AAAA) records
Info::
3 nameserver(s) configured
Got: ns4.nyu.edu, ns1.nyu.net, ns2.nyu.org
Info::
2 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
Warning::
DNS resolution is slow (296 ms)
Slow DNS adds latency to every page load. Consider a faster DNS provider.
Got: 296 ms
A216.165.61.24
AAAA—
CNAME—
NSns4.nyu.edu, ns1.nyu.net, ns2.nyu.org
MX
10 mxa-00256a01.gslb.pphosted.com
10 mxb-00256a01.gslb.pphosted.com
TXT
fastly-domain-delegation-z2mk2ugh5up86i4m3az9-289772-2020-09-23
MS=DC3CF354465F9F4FB5A01B09FBFF180ED22F296C
infoblox-domain-mastery=34facf1fc7d3bbbc27457d106c559122e02312d49fde17ae8af4fc8e...
SPF v=spf1 include:%{ir}.%{v}.%{d}.spf.has.pphosted.com include:mail.zendesk.com inc...
amazonses:570vvekbLUPOzboZxNoWw+sQztEzLFPmxOpAnKV2bcw=
Sendinblue-code:e570a8676ae98699a5ff860a7eff1f38
d365mktkey=wrgr4CmP8fLV3AGrcx3N8ppM80ssEtRxg1EvuEn3YL8x
notion-domain-verification=SPirDap4YasviSkGht7tvBz1Q6flwoQMQjfY5gC0RuD
sprout-social-8f958e49-63d8-4bfc-9826-271d23da83cc
apple-domain-verification=b6TUc4cksQQdpGfJ
formstack-domain-verification=92470a030e0c70d94bc0f74574679e7e
smartsheet-site-validation=nhaTPBPFyQPTo87tE7JYDUOzHmkSWQ94
1password-site-verification=7PVAWVJIPJH6PBUL24EYBA2GQE
brevo-code:45b781e69c3502b604156676945c1a5a
mandrill_verify.weV9vV4c5CxYgyg5rdIX3g
censys-domain-verification=gW6wBmek3RvgWxn-gVUHCOqRfKjuGKJB5xGZHj3N1FTw
docusign=dd188105-e05e-45be-95e9-3fbf59fc4a45
e2ma-verification=kv5eb
duo_sso_verification=WTYBcV6czONMrarxL7YUdpWbXrsnglElX9TsJCwW7J5XSEVh5asGM0CDeqk...
cisco-ci-domain-verification=5f8c1a91a88665fdf1306c4d97c57901e8f2b9134a468e369ac...
MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQDJe9uQvNP61RpaFRKJNGfkpYiyJ5/GNSoCizWm2guv...
e2ma-verification=ruzcb
apple-domain-verification=cGRUsgQrf98HFTVr
neat-pulse-domain-verification-9v8BGLM=3f2a3344-0174-4eaf-b982-7efe3e83fbb2
google-site-verification=zYK4YgpQpLb40VbmgUANCDqzDBkd6JWxG89WBqW-AvE
atlassian-domain-verification=wBl6PljSgaRhrZFeBYJmqW9h0irs5eYWCr4gCFcYpodIiXdhot...
google-site-verification=-5tfUFiJkZOeA4CLwhvxUV_9sv3_k1j4LwpwA_eWz3A
MS=ms25525126
docusign=a6da09da-1d59-4ede-baad-41ce0f74dd59
MS=ms46861818
adobe-idp-site-verification=d9edc0076f1d016844f8cb979364915c0407390e3fd34be8922a...
cmverification-2022
openai-domain-verification=dv-qwQyMcxw8InCnG2WTqxg7wJJ
drift-domain-verification=f2f0cda12b9a530f386b71c8fe79981375c876029c5b491606fe89...
82OWAZWDRS1RMM6JHOBC0JJF26SQLAO344GD276PD
d365mktkey=wiyHM4COTROERLhtFKfxLmXtPO25ZmPPeKGwIvUsv1Ax
zapier-domain-verification-challenge=cf19207c-42d6-4983-9372-cb01572729a2
airslate-domain-verification={C8C31474-7200-0000-0000D981}
airtable-verification=dda843c916cb87d00978ad8654a4aa76
apple-domain-verification=gUTv6Uz1Gdi14obE
CAALookup not available with standard resolver
Resolved in 296 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.

Slow DNS adds latency to every page load. Consider a faster DNS provider.

Why this matters

DNS resolution is slow — anycast DNS providers (Cloudflare, Route 53) typically resolve <50ms globally.

Source: DNS performance benchmarks

A
Redirect Chain
1 redirect(s), 599 ms total
PASS
1 redirect(s), 599 ms total
Info::
Single redirect
Got: https://nyu.edu → https://www.nyu.edu/ (302)
Info::
WWW normalization redirect
Info::
Uses 302 (temporary) redirect
If permanent, use 301 instead.
Got: https://nyu.edu
Info::
Redirect overhead: 599 ms total
Got: 599 ms

https://nyu.edu

422 ms · HTTP/1.0

302

https://www.nyu.edu/

176 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://nyu.edu302422 msHTTP/1.0BigIP
2https://www.nyu.edu/405176 msHTTP/1.1CloudFront

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
URL Variants
www/non-www, trailing slash, HTTP→HTTPS
PASS
www/non-www, trailing slash, HTTP→HTTPS
Warning::
HTTP→HTTPS redirect uses 302 instead of 301
Got: 302 temporary redirect Expected: 301 permanent redirect

www / non-www

405https://www.nyu.edu/
200https://nyu.edu/

HTTP → HTTPS

302http://nyu.edu/ → https://www.nyu.edu/

Use 301 (permanent) instead of 302 (temporary)

A+
Domain Intelligence
nyu.edu — 40 years, 1 months old, hosted on NYU-DOMAIN - New York University, US
PASS
nyu.edu — 40 years, 1 months old, hosted on NYU-DOMAIN - New York University, US
Info::
Domain registered until Jul 31, 2027 (1 years, 3 months remaining)
Info::
Hosting: NYU-DOMAIN - New York University, US
Got: AS12
Domain expiry

410 days

July 31, 2027

SSL certificate

170 days

Issued by Internet2

Domain age

40 years, 1 months

Registered October 8, 1986

DNSSEC

Status unknown

Protects against DNS spoofing

Hosting

NYU-DOMAIN - New York University, US

ASN AS12

216.165.61.24

Registrar

Registrar unknown

Lock status unknown 3 NS records
Expiry timeline
Today
+1 year
Domain expiry SSL expiry Danger zone (≤30 days)
Registrar
Created October 8, 1986 (40 years, 1 months ago)
Expires July 31, 2027 (1 years, 3 months)
Last Updated June 20, 2025
Name Servers ns2.nyu.org, ns1.nyu.net, ns4.nyu.edu
Registrant New York University
Hosting
IP Address 216.165.61.24
ASN AS12 (NYU-DOMAIN - New York University, US)
Provider NYU-DOMAIN - New York University, US
Data source: whois (0.9s)
A
HTTP Probe Timing
Total 503 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
PASS
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
106 ms
TCP Connect TCP Connect — time to establish a TCP connection to the server.
96 ms
TLS Handshake TLS Handshake — time to complete the HTTPS encryption handshake.
205 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
503 ms
Total Time Total request time from DNS lookup through full response.
503 ms

Connection waterfall

DNS Lookup 106 ms TCP Connect 96 ms TLS Handshake 205 ms Server Processing 96 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