Skip to content
https://skynet.be

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
65
GRADE
D
FIX
2
REVIEW
5
PASS
2
INFO
0
Probed from Singapore, Singapore
301 Moved Permanently
Checks
9
2 PASS 5 REVIEW 2 FIX
F
Redirect Chain
Action
4 redirect(s), 7991 ms total
FIX
4 redirect(s), 7991 ms total
Warning::
4 redirects before reaching final URL
Each redirect adds latency. Try to minimize the chain to 1 hop.
Info::
HTTP to HTTPS redirect present
Info::
WWW normalization redirect
Warning::
4-hop chain could be reduced to 1 hop
Redirect directly from https://skynet.be to https://www.pickx.be/
Info::
Uses 302 (temporary) redirect
If permanent, use 301 instead.
Got: http://www.skynet.be/
Warning::
Redirect overhead: 7991 ms total
Got: 7991 ms
Info::
Cross-domain redirect detected

https://skynet.be

797 ms · HTTP/1.1

301

http://www.skynet.be/

1815 ms · HTTP/1.1

302

https://www.proximus.be/pickx

1582 ms · HTTP/1.1

301

https://www.pickx.be/pickx

1897 ms · HTTP/1.1

302

https://www.pickx.be/

1900 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://skynet.be301797 msHTTP/1.1nginx
2http://www.skynet.be/3021815 msHTTP/1.1Apache
3https://www.proximus.be/pickx3011582 msHTTP/1.1
4https://www.pickx.be/pickx3021897 msHTTP/1.1
5https://www.pickx.be/2001900 msHTTP/1.1

See the visual redirect chain in the HTTP Probe tab →

Each redirect adds latency. Try to minimize the chain to 1 hop.

Why this matters

Redirect chain — each hop adds latency; combine into one redirect where possible.

Source: Google Search Central / web.dev

Redirect directly from https://skynet.be to https://www.pickx.be/

Why this matters

Redirect chain could be flattened to one hop — server config tweak removes intermediate latency.

Source: web.dev

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

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
Crawlability
Action
no robots.txt, sitemap with 0 URLs
REVIEW
no robots.txt, sitemap with 0 URLs
Info::
No robots.txt found
robots.txt is optional but recommended. It tells search engine crawlers which pages to index.
Info::
sitemap.xml is present
Warning::
sitemap.xml contains invalid XML
Search engines may not be able to parse the sitemap. Fix XML validation errors.
Warning::
sitemap.xml is empty — no URLs found
An empty sitemap provides no value. Add <url> entries for your pages.

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

Search engines may not be able to parse the sitemap. Fix XML validation errors.

Why this matters

An unparseable sitemap is silently ignored by Google — the URLs it advertises are never queued for crawl.

Learn more ▾

Google's sitemap parser is strict about XML validity. A single unescaped `&` or unclosed tag invalidates the whole file. Run your sitemap through a validator (Search Console's Sitemaps report flags it) and fix the offending entry. Most generators escape correctly; mistakes usually come from manually-written entries.

Source: sitemaps.org / Google Search Central

An empty sitemap provides no value. Add <url> entries for your pages.

Why this matters

An empty sitemap signals 'no content to index' to Google — actively harmful versus having no sitemap at all.

Learn more ▾

Google compares URLs in the sitemap against URLs it has crawled. An empty sitemap on a site with thousands of pages signals abandonment. Either populate it correctly (most CMSes auto-generate) or delete the file and let Google crawl normally.

Source: Google Search Central / sitemaps.org

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 200 OK
Type URL Set URLs 0 entries Valid XML No
B
URL Variants
www/non-www, trailing slash, HTTP→HTTPS
REVIEW
www/non-www, trailing slash, HTTP→HTTPS
Info::
www/non-www redirect configured correctly (preferred: non-www)
Critical::
HTTP version does not redirect to HTTPS
Got: HTTP 301 Expected: 301 redirect to HTTPS

www / non-www

302https://www.skynet.be/
200https://skynet.be/

Preferred variant: non-www

HTTP → HTTPS

301http://skynet.be/ → http://www.skynet.be/

HTTP version does not redirect to HTTPS

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

Connection waterfall

DNS Lookup 633 ms TCP Connect 157 ms TLS Handshake 161 ms Server Processing 163 ms Content Transfer 0 ms
B
TLS Certificate Expiry & Recommendations
81 days until leaf cert expires — 3 issues to address
REVIEW

Certificate validity

81
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, 634 ms lookup
PASS
1 A records, 634 ms lookup
Info::
Resolves to 1 IPv4 address(es)
Got: 195.238.25.201
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: ns4.skynet.be, ns1.skynet.be, ns3.skynet.be, ns2.skynet.be
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 (634 ms)
Slow DNS adds latency to every page load. Consider a faster DNS provider.
Got: 634 ms
A195.238.25.201
AAAA—
CNAME—
NSns4.skynet.be, ns1.skynet.be, ns3.skynet.be, ns2.skynet.be
MX
10 mx.glb.proximus.be
TXT
_globalsign-domain-verification=PKLTA2-qg0e6D8VUkfLco8wd5kwXl7I-v8MQ8ItQL4
etd-domain-verification=Q7WIHN6T0hJgXos0x4nV1aZEiSdyinKs
6tZOYDOKmjP6GkkDRK3kv02EBRx/okRhLV4yq6KABJQ=
_globalsign-domain-verification=lKB0EubTrx3NTx971J-1phu9vg-Bu-TZJx9Hm4egSQ
_globalsign-domain-verification=CnIZ6JEnXw3e4F2lNuRpDcEopjfYHlukPzgm4uHVVK
3dIpPsPBYkhRktL3JqygEReh1rlKXMnxK4OMLZJax8s=
bxFUY8tKxmEPybSuzylaguenrH67JOtcibYY62Gixlk=
google-site-verification=7ccl8E65UEakcGWBOD8S21PaErgkT_Y089Nz705PgNs
_globalsign-domain-verification=NuiPynXr6QAn5o0Om8wCmPLiTFMgeIN1VXtbAVIOXb
_globalsign-domain-verification=LryWfOGk08qx52XfIzvAiIi-Q9pp-sBy5e6KtJqctq
_globalsign-domain-verification=bTyz9wrnBverZWBeI6b4xDfKWhsC8LYSdUoJMWNThl
_globalsign-domain-verification=ARGseqouIVp9cQ2g8hCfBnL9LUuPoux6B04nowend6
SPF v=spf1 include:ispmail.spf.secure-mail.be include:bgc.spf.secure-mail.be ip4:193...
facebook-domain-verification=vl6mab2pxfwsntj0x9bpjrwy3iwu4t
CAALookup not available with standard resolver
Resolved in 634 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+
Domain Intelligence
skynet.be — hosted on PROXIMUS-ISP-AS, BE
PASS
skynet.be — hosted on PROXIMUS-ISP-AS, BE
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: PROXIMUS-ISP-AS, BE
Got: AS5432
Domain expiry

Unknown

SSL certificate

81 days

Issued by GlobalSign nv-sa

Domain age

Unknown

DNSSEC

Status unknown

Protects against DNS spoofing

Hosting

PROXIMUS-ISP-AS, BE

ASN AS5432

195.238.25.201

Registrar

Registrar unknown

Unlocked 4 NS records
Expiry timeline
Today
+1 year
SSL expiry Danger zone (≤30 days)
Recommended actions
  • Enable registrar lock (clientTransferProhibited) to block unauthorized domain transfers
Registrar
Name Servers ns1.skynet.be, ns2.skynet.be, ns3.skynet.be, ns4.skynet.be
Registrant Not shown, please visit www.dnsbelgium.be for webbased whois.
Hosting
IP Address 195.238.25.201
ASN AS5432 (PROXIMUS-ISP-AS, BE)
Provider PROXIMUS-ISP-AS, BE
Data source: whois (1.7s)

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