Skip to content
https://redalyc.org

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
88
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
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.redalyc.org/
200https://redalyc.org/

Inconsistent — duplicate content risk

HTTP → HTTPS

301http://redalyc.org/ → https://www.redalyc.org/

Consistent

C
HTTP Probe Timing
Action
Total 1910 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
REVIEW
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.
148 ms
TLS Handshake TLS Handshake — time to complete the HTTPS encryption handshake.
317 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
1.17 s
Total Time Total request time from DNS lookup through full response.
1.91 s

Connection waterfall

DNS Lookup 46 ms TCP Connect 148 ms TLS Handshake 317 ms Server Processing 662 ms Content Transfer 739 ms
B
TLS Certificate Expiry & Recommendations
272 days until leaf cert expires — 4 issues to address
REVIEW

Certificate validity

272
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, 61 ms lookup
PASS
1 A records, 61 ms lookup
Info::
Resolves to 1 IPv4 address(es)
Got: 148.215.2.1
Info::
Single A record — no DNS redundancy
Multiple A records provide failover if one server goes down.
Info::
No IPv6 (AAAA) records
Info::
4 nameserver(s) configured
Got: ns2-05.azure-dns.net, ns3-05.azure-dns.org, ns1-05.azure-dns.com, ns4-05.azure-dns.info
Info::
5 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: 61 ms
Got: 61 ms
A148.215.2.1
AAAA—
CNAME—
NSns2-05.azure-dns.net, ns3-05.azure-dns.org, ns1-05.azure-dns.com, ns4-05.azure-dns.info
MX
1 aspmx.l.google.com
5 alt2.aspmx.google.com
5 alt1.aspmx.google.com
10 aspmx3.googlemail.com
10 aspmx2.googlemail.com
TXT
MS=ms15618709
SPF v=spf1 include:_spf.google.com -all
17s1tf1as249qi53dibdilaluh
CAALookup not available with standard resolver
Resolved in 61 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://redalyc.org

https://redalyc.org

732 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://redalyc.org200732 msHTTP/1.1WebSphere Application Server/8.5
A+
Crawlability
robots.txt present, sitemap with 142 URLs
PASS
robots.txt present, sitemap with 142 URLs
Info::
robots.txt is present
Got: 778 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 142 entries
Info::
Sitemap index with 142 child sitemaps
Info::
robots.txt references sitemap
robots.txt 200 OK
Size 778 B Sitemaps referenced 1 User-agents Mediapartners-Google*, dotbot, Bingbot, IstellaBot, SemrushBot, CCBot, Googlebot-Image, AhrefsBot, msnbot, turnitinbot, SemrushBot-SA, Yandex, * Blocking No — crawling allowed
User-agent: *

Disallow: /redalyc/indexfiles

Disallow: /redalyc/lib

Disallow: /redalyc/xmlindex

Disallow: /indicador/

Allow: /redalyc/media


 
# Google Image

User-agent: Googlebot-Image

Disallow:

Allow: /*

 
# Google AdSense

User-agent: Mediapartners-Google*

Disallow:

Allow: /*


User-agent: AhrefsBot

Crawl-delay: 50
Disallow: /


User-agent: msnbot

Crawl-delay: 10
Disallow: /


User-agent: dotbot

Disallow: /


User-agent: turnitinbot

Disallow: /


User-agent: Bingbot

Crawl-delay: 1
Disallow: 


User-agent: IstellaBot

Disallow: /


User-agent: SemrushBot

Disallow: /

 
User-agent: SemrushBot-SA

Disallow: /


User-agent: Yandex

Allow: /


User-agent: CCBot

Disallow: /


Sitemap: https://www.redalyc.org/sitemaps/sitemap-index.xml
sitemap.xml 200 OK
Type Sitemap Index URLs 142 entries Valid XML Yes
Child Sitemaps:
A+
Domain Intelligence
redalyc.org — via NameSilo, LLC, 22 years, 10 months old, hosted on Universidad Autonoma del Estado de Mexico, MX
PASS
redalyc.org — via NameSilo, LLC, 22 years, 10 months old, hosted on Universidad Autonoma del Estado de Mexico, MX
Info::
Domain registered until Oct 8, 2029 (3 years, 6 months remaining)
Info::
DNSSEC is not enabled
DNSSEC protects against DNS spoofing attacks. While not required, enabling DNSSEC adds an additional layer of security. Contact your DNS provider to enable it.
Info::
Registrar: NameSilo, LLC
Warning::
Registrar lock is NOT enabled
The domain can be transferred without an unlock step. Enable registrar lock (clientTransferProhibited) in your registrar's control panel to protect against unauthorized or accidental transfers.
Info::
Hosting: Universidad Autonoma del Estado de Mexico, MX
Got: AS28526
Domain expiry

1211 days

October 8, 2029

SSL certificate

272 days

Issued by GoDaddy.com, Inc.

Domain age

22 years, 10 months

Registered October 8, 2003

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

Universidad Autonoma del Estado de Mexico, MX

ASN AS28526

148.215.2.1

Registrar

NameSilo, LLC

Unlocked 2 NS records
Expiry timeline
Today
+1 year
Domain expiry SSL expiry Danger zone (≤30 days)
Recommended actions
  • Enable DNSSEC to protect visitors from DNS spoofing
  • Enable registrar lock (clientTransferProhibited) to block unauthorized domain transfers
Registrar NameSilo, LLC
Created October 8, 2003 (22 years, 10 months ago)
Expires October 8, 2029 (3 years, 6 months)
Last Updated May 17, 2025
Name Servers ns1-05.azure-dns.com, ns2-05.azure-dns.net
DNSSEC Not enabled
Hosting
IP Address 148.215.2.1
ASN AS28526 (Universidad Autonoma del Estado de Mexico, MX)
Provider Universidad Autonoma del Estado de Mexico, MX
Data source: rdap (0.6s)

DNSSEC protects against DNS spoofing attacks. While not required, enabling DNSSEC adds an additional layer of security. Contact your DNS provider to enable it.

Why this matters

Without DNSSEC, an attacker who can poison your DNS can hijack your domain — and SSL certs alone don't stop them.

Learn more ▾

DNSSEC adds cryptographic signatures to DNS records, preventing forged responses from poisoning resolver caches. Without it, an attacker who controls the network path can redirect your domain to a malicious server before any HTTPS handshake happens. Most modern registrars (Cloudflare, Google Domains, Route 53) enable it with one toggle.

Source: ICANN / RFC 4033

The domain can be transferred without an unlock step. Enable registrar lock (clientTransferProhibited) in your registrar's control panel to protect against unauthorized or accidental transfers.

Why this matters

Without registrar lock, an attacker who phishes your registrar credentials can transfer the domain in minutes — total brand hijack.

Learn more ▾

Registrar lock (clientTransferProhibited, clientUpdateProhibited, clientDeleteProhibited) requires extra verification before any transfer/update/delete. Every major registrar offers it free. Combined with 2FA on your registrar account, it's the strongest defense against domain hijacking.

Source: ICANN / domain-security best practice

All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback