Skip to content
https://fullerton.edu

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
86
GRADE
B
FIX
1
REVIEW
3
PASS
5
INFO
0
Probed from Madrid, Spain
200 OK
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
URL Variants
www/non-www, trailing slash, HTTP→HTTPS
REVIEW
www/non-www, trailing slash, HTTP→HTTPS
Critical::
HTTP version does not redirect to HTTPS
Got: HTTP 200 Expected: 301 redirect to HTTPS

www / non-www

200https://www.fullerton.edu/
https://fullerton.edu/

HTTP → HTTPS

200http://www.fullerton.edu/

HTTP version does not redirect to HTTPS

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

Certificate validity

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

Recommended actions

  • Extend HSTS max-age to at least 31536000 (1 year) to meet the preload list criteria
  • 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, 49 ms lookup
PASS
1 A records, 49 ms lookup
Info::
Resolves to 1 IPv4 address(es)
Got: 137.151.127.120
Info::
Single A record — no DNS redundancy
Multiple A records provide failover if one server goes down.
Info::
No IPv6 (AAAA) records
Info::
No NS records found
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::
No SPF record found in TXT records
SPF helps prevent email spoofing. Add a TXT record starting with 'v=spf1'.
Info::
DNS resolution time: 49 ms
Got: 49 ms
A137.151.127.120
AAAA—
CNAME—
NS—
MX
10 mail.fullerton.edu
TXT—
CAALookup not available with standard resolver
Resolved in 49 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.

SPF helps prevent email spoofing. Add a TXT record starting with 'v=spf1'.

Why this matters

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+
Redirect Chain
No redirects — direct access
PASS
No redirects — direct access
Info::
No redirects — direct access
Got: https://www.fullerton.edu

https://www.fullerton.edu

525 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://www.fullerton.edu200525 msHTTP/1.1Microsoft-IIS/10.0
A+
Crawlability
robots.txt present, sitemap with 500 URLs
PASS
robots.txt present, sitemap with 500 URLs
Info::
robots.txt is present
Got: 46 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 500 entries
Info::
robots.txt references sitemap
robots.txt 200 OK
Size 46 B Sitemaps referenced 1 User-agents Blocking No — crawling allowed
SITEMAP: https://www.fullerton.edu/sitemap.xml
sitemap.xml 200 OK
Type URL Set URLs 500 entries Valid XML Yes
Sample URLs:
A+
Domain Intelligence
fullerton.edu — 36 years, 11 months old, hosted on CENIC-2152 - CENIC, US
PASS
fullerton.edu — 36 years, 11 months old, hosted on CENIC-2152 - CENIC, US
Info::
Domain registered until Jul 31, 2026 (3 months remaining)
Info::
Hosting: CENIC-2152 - CENIC, US
Got: AS2152
Domain expiry

45 days

July 31, 2026

SSL certificate

131 days

Issued by Internet2

Domain age

36 years, 11 months

Registered December 1, 1989

DNSSEC

Status unknown

Protects against DNS spoofing

Hosting

CENIC-2152 - CENIC, US

ASN AS2152

137.151.127.120

Registrar

Registrar unknown

Lock status unknown 3 NS records
Expiry timeline
Today
+1 year
Domain expiry SSL expiry Danger zone (≤30 days)
Recommended actions
  • Renew the domain or enable auto-renewal to prevent accidental expiry
Registrar
Created December 1, 1989 (36 years, 11 months ago)
Expires July 31, 2026 (3 months)
Last Updated August 12, 2025
Name Servers gold.foundationdns.com, gold.foundationdns.net, gold.foundationdns.org
Registrant California State University, Fullerton
Hosting
IP Address 137.151.127.120
ASN AS2152 (CENIC-2152 - CENIC, US)
Provider CENIC-2152 - CENIC, US
Data source: whois (1.0s)
A
HTTP Probe Timing
Total 723 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
PASS
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
46 ms
TCP Connect TCP Connect — time to establish a TCP connection to the server.
167 ms
TLS Handshake TLS Handshake — time to complete the HTTPS encryption handshake.
173 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
556 ms
Total Time Total request time from DNS lookup through full response.
723 ms

Connection waterfall

DNS Lookup 46 ms TCP Connect 167 ms TLS Handshake 173 ms Server Processing 171 ms Content Transfer 167 ms
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback