Skip to content
https://elte.hu

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
84
GRADE
B
FIX
1
REVIEW
4
PASS
4
INFO
0
Probed from Sao Paulo, Brazil
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

C
URL Variants
Action
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
Warning::
HTTP→HTTPS redirect uses 302 instead of 301
Got: 302 temporary redirect Expected: 301 permanent redirect

www / non-www

200https://www.elte.hu/
200https://elte.hu/

Inconsistent — duplicate content risk

HTTP → HTTPS

302http://elte.hu/ https://elte.hu/

Use 301 (permanent) instead of 302 (temporary)

B
HTTP Probe Timing
Total 1274 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
REVIEW
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
212 ms
TCP Connect TCP Connect — time to establish a TCP connection to the server.
210 ms
TLS Handshake TLS Handshake — time to complete the HTTPS encryption handshake.
221 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
914 ms
Total Time Total request time from DNS lookup through full response.
1.27 s

Connection waterfall

DNS Lookup 212 ms TCP Connect 210 ms TLS Handshake 221 ms Server Processing 271 ms Content Transfer 360 ms
B
TLS Certificate Expiry & Recommendations
212 days until leaf cert expires — 3 issues to address
REVIEW

Certificate validity

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

Recommended actions

  • 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, 882 ms lookup
PASS
1 A records, 882 ms lookup
Info::
Resolves to 1 IPv4 address(es)
Got: 157.181.152.2
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: darmol.elte.hu, filippa.elte.hu, unistar.bke.hu
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::
SPF record present in TXT
Warning::
DNS resolution is slow (882 ms)
Slow DNS adds latency to every page load. Consider a faster DNS provider.
Got: 882 ms
A157.181.152.2
AAAA
CNAME
NSdarmol.elte.hu, filippa.elte.hu, unistar.bke.hu
MX
0 elte-hu.mail.protection.outlook.com
TXT
HARICA-t3Srp7x9YenGlw1P46f
google-site-verification=fmI6itoEhW1gYBxrSpMMeD8rKzoziaSRku9ECiLwgm4
SPF v=spf1 include:spf.protection.outlook.com -all
MS=ABEEC841FCC486257F51A913DC32843A9D1C0BC2
CAALookup not available with standard resolver
Resolved in 882 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
No redirects — direct access
PASS
No redirects — direct access
Info::
No redirects — direct access
Got: https://elte.hu

https://elte.hu

1203 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://elte.hu2001203 msHTTP/1.1Apache/2.4.58 (Ubuntu)
A+
Crawlability
robots.txt present, sitemap with 14 URLs
PASS
robots.txt present, sitemap with 14 URLs
Info::
robots.txt is present
Got: 3171 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 14 entries
Info::
Sitemap index with 14 child sitemaps
Info::
robots.txt does not reference a sitemap
Add a 'Sitemap:' directive to robots.txt so search engines can discover your sitemap.

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 3171 B Sitemaps referenced 0 User-agents Scrapy, GPTBot, CCBot, SemrushBot, Baiduspider, AhrefsBot, ChatGPT-User, * Blocking No — crawling allowed
#
# robots.txt
#
# This file is to prevent the crawling and indexing of certain parts
# of your site by web crawlers and spiders run by sites like Yahoo!
# and Google. By telling these "robots" where not to go on your site,
# you save bandwidth and server resources.
#
# This file will be ignored unless it is at the root of your host:
# Used:    http://example.com/robots.txt
# Ignored: http://example.com/site/robots.txt
#
# For more information about the robots.txt standard, see:
# http://www.robotstxt.org/robotstxt.html

User-agent: *
# CSS, JS, Images
Allow: /core/*.css$
Allow: /core/*.css?
Allow: /core/*.js$
Allow: /core/*.js?
Allow: /core/*.gif
Allow: /core/*.jpg
Allow: /core/*.jpeg
Allow: /core/*.png
Allow: /core/*.svg
Allow: /profiles/*.css$
Allow: /profiles/*.css?
Allow: /profiles/*.js$
Allow: /profiles/*.js?
Allow: /profiles/*.gif
Allow: /profiles/*.jpg
Allow: /profiles/*.jpeg
Allow: /profiles/*.png
Allow: /profiles/*.svg
# Directories
Disallow: /core/
Disallow: /profiles/
# Files
Disallow: /README.md
Disallow: /composer/Metapackage/README.txt
Disallow: /composer/Plugin/ProjectMessage/README.md
Disallow: /composer/Plugin/Scaffold/README.md
Disallow: /composer/Plugin/VendorHardening/README.txt
Disallow: /composer/Template/README.txt
Disallow: /modules/README.txt
Disallow: /sites/README.txt
Disallow: /themes/README.txt
# Paths (clean URLs)
Disallow: /admin/
Disallow: /comment/reply/
Disallow: /filter/tips
Disallow: /node/add/
Disallow: /search/
Disallow: /user/register
Disallow: /user/password
Disallow: /user/login
Disallow: /user/logout
Disallow: /media/oembed
Disallow: /*/media/oembed
# Paths (no clean URLs)
Disallow: /index.php/admin/
Disallow: /index.php/comment/reply/
Disallow: /index.php/filter/tips
Disallow: /index.php/node/add/
Disallow: /index.php/search/
Disallow: /index.php/user/password
Disallow: /index.php/user/register
Disallow: /index.php/user/login
Disallow: /index.php/user/logout
Disallow: /index.php/media/oembed
Disallow: /index.php/*/media/oembed

# Disallow query strings in URLs.
Disallow: /*?*

# Prevent bots from crawling SAML login redirects.
# Googlebot was generating ~1758 requests/2h to these URLs, causing
# unnecessary PHP-FPM load for authentication redirects.
# @see https://gitlab.studiopresent.com/k8s/drupal/elte/-/issues/266
Disallow: /saml/login

# Block aggressive crawlers that cause server overload.
# Scrapy bots: 27K+ requests/day, crawling entire site including SAML endpoints.
User-agent: Scrapy
Disallow: /

# GPTBot: OpenAI training crawler.
User-agent: GPTBot
Disallow: /

# CCBot: Common Crawl bot used for AI training.
User-agent: CCBot
Disallow: /

# SemrushBot: aggressive SEO crawler, 9K+ requests/day.
User-agent: SemrushBot
Crawl-delay: 10
Disallow: /saml/
Disallow: /node/
Disallow: /user/

# Baiduspider: 6K+ requests/day.
User-agent: Baiduspider
Crawl-delay: 10
Disallow: /saml/
Disallow: /node/
Disallow: /user/

# AhrefsBot: aggressive SEO crawler.
User-agent: AhrefsBot
Crawl-delay: 10
Disallow: /saml/
Disallow: /node/
Disallow: /user/

# ChatGPT: AI crawler, 4K+ requests/day.
User-agent: ChatGPT-User
Crawl-delay: 10
Disallow: /saml/
Disallow: /node/
Disallow: /user/

A+
Domain Intelligence
elte.hu — 34 years, 1 months old, hosted on ELTENET ELTENET, HU
PASS
elte.hu — 34 years, 1 months old, hosted on ELTENET ELTENET, HU
Info::
Hosting: ELTENET ELTENET, HU
Got: AS2012
Domain expiry

Unknown

SSL certificate

212 days

Issued by Hellenic Academic and Research Institutions CA

Domain age

34 years, 1 months

Registered September 10, 1992

DNSSEC

Status unknown

Protects against DNS spoofing

Hosting

ELTENET ELTENET, HU

ASN AS2012

157.181.152.2

Registrar

Registrar unknown

Lock status unknown Name servers unknown
Expiry timeline
Today
+1 year
SSL expiry Danger zone (≤30 days)
Registrar
Created September 10, 1992 (34 years, 1 months ago)
Hosting
IP Address 157.181.152.2
ASN AS2012 (ELTENET ELTENET, HU)
Provider ELTENET ELTENET, HU
Data source: whois (2.4s)
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback