Skip to content
https://atw.hu

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
89
GRADE
B
FIX
1
REVIEW
3
PASS
5
INFO
0
Probed from New York, United Stated
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
Crawlability
robots.txt present, no sitemap
REVIEW
robots.txt present, no sitemap
Info::
robots.txt is present
Got: 24 bytes
Info::
No sitemap.xml found
A sitemap helps search engines discover and index your pages more efficiently.
Info::
robots.txt does not reference a sitemap
Add a 'Sitemap:' directive to robots.txt so search engines can discover your sitemap.

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

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 24 B Sitemaps referenced 0 User-agents * Blocking No — crawling allowed
User-agent: *
Disallow:
sitemap.xml No sitemap found

No sitemap found

Adding a sitemap helps search engines discover your pages.

C
TLS Certificate Expiry & Recommendations
Action
23 days until leaf cert expires — 5 issues to address
REVIEW

Certificate validity

23
days left
0d 30d 60d 90d+
Renew soon — under 30 days remaining

Recommended actions

  • Renew certificate — 23 days remaining
  • 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, 101 ms lookup
PASS
1 A records, 101 ms lookup
Info::
Resolves to 1 IPv4 address(es)
Got: 94.125.176.29
Info::
Single A record — no DNS redundancy
Multiple A records provide failover if one server goes down.
Info::
No IPv6 (AAAA) records
Info::
2 nameserver(s) configured
Got: ns1.atw.hu, ns5.atw.hu
Info::
10 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: 101 ms
Got: 101 ms
A94.125.176.29
AAAA—
CNAME—
NSns1.atw.hu, ns5.atw.hu
MX
10 mail.atw.hu
20 mail2.atw.hu
30 sp000.m.atw.hu
30 sp006.m.atw.hu
30 sp003.m.atw.hu
30 sp007.m.atw.hu
30 sp001.m.atw.hu
30 sp005.m.atw.hu
30 sp004.m.atw.hu
30 sp002.m.atw.hu
TXT
SPF v=spf1 ip4:88.151.96.0/24 ip4:94.125.176.0/24 ip6:2a01:270::/48 -all
CAALookup not available with standard resolver
Resolved in 101 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://atw.hu

https://atw.hu

831 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://atw.hu200831 msHTTP/1.1atw-proxy
A+
URL Variants
www/non-www, trailing slash, HTTP→HTTPS
PASS
www/non-www, trailing slash, HTTP→HTTPS
Info::
www/non-www redirect configured correctly (preferred: non-www)
Info::
HTTP correctly 301-redirects to HTTPS

www / non-www

301https://www.atw.hu/
200https://atw.hu/

Preferred variant: non-www

HTTP → HTTPS

301http://atw.hu/ → https://atw.hu/

Consistent

A+
Domain Intelligence
atw.hu — 23 years, 3 months old, hosted on ATW-AS, HU
PASS
atw.hu — 23 years, 3 months old, hosted on ATW-AS, HU
Info::
Hosting: ATW-AS, HU
Got: AS41075
Domain expiry

Unknown

SSL certificate

23 days

Issued by Let's Encrypt

Domain age

23 years, 3 months

Registered May 22, 2003

DNSSEC

Status unknown

Protects against DNS spoofing

Hosting

ATW-AS, HU

ASN AS41075

94.125.176.29

Registrar

Registrar unknown

Lock status unknown Name servers unknown
Expiry timeline
Today
+1 year
SSL expiry Danger zone (≤30 days)
Recommended actions
  • Renew the TLS certificate or verify auto-renewal is working
Registrar
Created May 22, 2003 (23 years, 3 months ago)
Hosting
IP Address 94.125.176.29
ASN AS41075 (ATW-AS, HU)
Provider ATW-AS, HU
Data source: whois (0.6s)
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.
99 ms
TCP Connect TCP Connect — time to establish a TCP connection to the server.
146 ms
TLS Handshake TLS Handshake — time to complete the HTTPS encryption handshake.
295 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
723 ms
Total Time Total request time from DNS lookup through full response.
724 ms

Connection waterfall

DNS Lookup 99 ms TCP Connect 146 ms TLS Handshake 295 ms Server Processing 183 ms Content Transfer 1 ms
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback