| 1. General Results, most used to calculate the result |
| A | name "bytebunker.space" is domain, public suffix is ".space", top-level-domain is ".space", top-level-domain-type is "generic", tld-manager is "DotSpace Inc.", num .space-domains preloaded: 348 (complete: 245733)
|
| A | Good: All ip addresses are public addresses
|
| A | Good: Minimal 2 ip addresses per domain name found: bytebunker.space has 2 different ip addresses (authoritative).
|
| A | Good: Ipv4 and Ipv6 addresses per domain name found: bytebunker.space has 1 ipv4, 1 ipv6 addresses
|
| Warning: Only one ip address found: www.bytebunker.space has only one ip address.
|
| Warning: No ipv6 address found. Ipv6 is the future with a lot of new features. So every domain name should have an ipv6 address. See https://en.wikipedia.org/wiki/IPv6: www.bytebunker.space has no ipv6 address.
|
| A | Good: No asked Authoritative Name Server had a timeout
|
| A | Good - only one version with Http-Status 200
|
| A | Good: No cookie sent via http.
|
| HSTS-Preload-Status: unknown. Domain never included in the Preload-list. Check https://hstspreload.org/ to learn some basics about the Google-Preload-List.
|
| A | Good: Some urls with http status 200/404 have a complete Content-Type header (MediaType / MediaSubType + correct charset):0 complete Content-Type - header (2 urls)
|
| http://bytebunker.space/ 2a00:5da0:1000:1::28e5
|
| Url with incomplete Content-Type - header - missing charset
|
| http://bytebunker.space/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 2a00:5da0:1000:1::28e5
|
| Url with incomplete Content-Type - header - missing charset
|
| H | Fatal error: No https - result with http-status 200, no encryption
|
| H | Fatal error: http result with http-status 200, no encryption. Add a redirect http ⇒ https, so every connection is secure. Perhaps in your port 80 vHost something like "RewriteEngine on" + "RewriteRule ^ https://%{SERVER_NAME}%{REQUEST_URI} [END,QSA,R=permanent]" (two rows, without the "). Don't add this in your port 443 vHost, that would create a loop.
|
| K | http://bytebunker.space/ 185.146.3.52, Status -14
| http://bytebunker.space/ 2a00:5da0:1000:1::28e5, Status 200
| Configuration problem - different ip addresses with different status
|
| K | https://bytebunker.space/ 185.146.3.52, Status -14
| https://bytebunker.space/ 2a00:5da0:1000:1::28e5, Status -102
| Configuration problem - different ip addresses with different status
|
| K | http://bytebunker.space/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 185.146.3.52, Status -14
| http://bytebunker.space/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 2a00:5da0:1000:1::28e5, Status 404
| Configuration problem - different ip addresses with different status
|
| V | https://bytebunker.space/ 2a00:5da0:1000:1::28e5
|
| Connect failure - perhaps firewall
|
| V | https://[2a00:5da0:1000:0001:0000:0000:0000:28e5]/ 2a00:5da0:1000:1::28e5
|
| Connect failure - perhaps firewall
|
| A | Good: More then one ip address per domain name found, checking all ip addresses the same http status and the same certificate found: Domain bytebunker.space, 2 ip addresses.
|
| Info: Checking the ip addresses of that domain name not exact one certificate found. So it's impossible to check if that domain requires Server Name Indication (SNI).: Domain bytebunker.space, 2 ip addresses.
|
| Info: Checking the ip addresses of that domain name not exact one certificate found. So it's impossible to check if that domain requires Server Name Indication (SNI).: Domain www.bytebunker.space, 1 ip addresses.
|
| B | No _mta-sts TXT record found (mta-sts: Mail Transfer Agent Strict Transport Security - see RFC 8461). Read the result of server-daten.de (Url-Checks, Comments, Connections and DomainServiceRecords) to see a complete definition. Domainname: _mta-sts.bytebunker.space
|
| 2. Header-Checks (Cross-Origin-* headers are alpha - started 2024-06-05) |
| U |
|
| No https result with http status 2** or 4** (standard-check) found, no header checked.
|
| 3. DNS- and NameServer - Checks |
| A | Info:: 11 Root-climbing DNS Queries required to find all IPv4- and IPv6-Addresses of 4 Name Servers.
|
| A | Info:: 11 Queries complete, 7 with IPv6, 4 with IPv4.
|
| Warning: Only some DNS Queries done via ipv6. IPv6 is the future, so the name servers of your name servers should have ipv6 addresses.
|
| A | Good: Some ip addresses of name servers found with the minimum of two DNS Queries. One to find the TLD-Zone, one to ask the TLD-Zone.ns1.beget.com (5.101.159.11), ns1.beget.pro (5.101.159.11), ns2.beget.com (185.50.27.12), ns2.beget.pro (185.50.27.12)
|
| A | Good (1 - 3.0):: An average of 2.8 queries per domain name server required to find all ip addresses of all name servers.
|
| A | Info:: 4 different Name Servers found: ns1.beget.com, ns1.beget.pro, ns2.beget.com, ns2.beget.pro, 4 Name Servers included in Delegation: ns1.beget.com, ns1.beget.pro, ns2.beget.com, ns2.beget.pro, 4 Name Servers included in 1 Zone definitions: ns1.beget.com, ns1.beget.pro, ns2.beget.com, ns2.beget.pro, 1 Name Servers listed in SOA.Primary: ns1.beget.com.
|
| A | Good: Only one SOA.Primary Name Server found.: ns1.beget.com.
|
| A | Good: SOA.Primary Name Server included in the delegation set.: ns1.beget.com.
|
| A | Good: Consistency between delegation and zone. The set of NS records served by the authoritative name servers must match those proposed for the delegation in the parent zone. Ordered list of name servers: ns1.beget.com, ns1.beget.pro, ns2.beget.com, ns2.beget.pro
|
| A | Good: All Name Server Domain Names have a Public Suffix.
|
| A | Good: All Name Server Domain Names ending with a Public Suffix have minimal one IPv4- or IPv6 address.
|
| A | Good: All Name Server ip addresses are public.
|
| A | Good: Minimal 2 different name servers (public suffix and public ip address) found: 4 different Name Servers found
|
| Warning: No Name Server IPv6 address found. IPv6 is the future, so your name servers should be visible via IPv6.: 4 different Name Servers found
|
| A | Good: Name servers with different Top Level Domains / Public Suffix List entries found: 4 Name Servers, 2 Top Level Domains: pro, com
|
| A | Good: Name Servers with different domain names found.: 2 different Domains found
|
| Warning: All Name Servers from the same Country / IP location.: 4 Name Servers, 1 Countries: RU
|
| A | Info: Ipv4-Subnet-list: 4 Name Servers, 2 different subnets (first Byte): 185., 5., 2 different subnets (first two Bytes): 185.50., 5.101., 2 different subnets (first three Bytes): 185.50.27., 5.101.159.
|
| A | Good: Name Server IPv4-addresses from different subnet found:
|
| A | Good: Nameserver supports TCP connections: 4 good Nameserver
|
| A | Good: Nameserver supports Echo Capitalization: 4 good Nameserver
|
| A | Good: Nameserver supports EDNS with max. 512 Byte Udp payload, message is smaller: 4 good Nameserver
|
| A | Good: Nameserver has passed 10 EDNS-Checks (OP100, FLAGS, V1, V1OP100, V1FLAGS, DNSSEC, V1DNSSEC, NSID, COOKIE, CLIENTSUBNET): 4 good Nameserver
|
| Nameserver doesn't pass all EDNS-Checks: a.nic.space: OP100: ok. FLAGS: ok. V1: ok. V1OP100: ok. V1FLAGS: ok. DNSSEC: ok. V1DNSSEC: ok. NSID: ok (SFQY-BG7AF9-XTW0MS). COOKIE: SOA expected, but NOT found, NOERR expected, BADVER found, Version 0 expectend and found. CLIENTSUBNET: ok.
|
| Nameserver doesn't pass all EDNS-Checks: e.nic.space: OP100: ok. FLAGS: ok. V1: ok. V1OP100: ok. V1FLAGS: ok. DNSSEC: ok. V1DNSSEC: ok. NSID: ok (SFQY-BG7AF9-XTW0MS). COOKIE: SOA expected, but NOT found, NOERR expected, BADVER found, Version 0 expectend and found. CLIENTSUBNET: ok.
|
| Nameserver doesn't pass all EDNS-Checks: ns0.centralnic.net: OP100: no result. FLAGS: no result. V1: no result. V1OP100: no result. V1FLAGS: no result. DNSSEC: no result. V1DNSSEC: no result. NSID: no result. COOKIE: no result. CLIENTSUBNET: no result.
|
| A | Good: All SOA have the same Serial Number
|
| Warning: No CAA entry with issue/issuewild found, every CAA can create a certificate. Read https://en.wikipedia.org/wiki/DNS_Certification_Authority_Authorization to learn some basics about the idea of CAA. Your name server must support such an entry. Not all dns providers support CAA entries.
|
| 4. Content- and Performance-critical Checks |
| http://bytebunker.space/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 185.146.3.52
|
| Fatal: Check of /.well-known/acme-challenge/random-filename has a timeout. Creating a Letsencrypt certificate via http-01 challenge can't work. You need a running webserver (http) and an open port 80. If it's a home server + ipv4, perhaps a correct port forwarding port 80 extern ⇒ working port intern is required. Port 80 / http can redirect to another domain port 80 or port 443, but not other ports. If it's a home server, perhaps your ISP blocks port 80. Then you may use the dns-01 challenge. Trouble creating a certificate? Use https://community.letsencrypt.org/ to ask.
|
| http://www.bytebunker.space/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 185.146.3.52
|
| Fatal: Check of /.well-known/acme-challenge/random-filename has a timeout. Creating a Letsencrypt certificate via http-01 challenge can't work. You need a running webserver (http) and an open port 80. If it's a home server + ipv4, perhaps a correct port forwarding port 80 extern ⇒ working port intern is required. Port 80 / http can redirect to another domain port 80 or port 443, but not other ports. If it's a home server, perhaps your ISP blocks port 80. Then you may use the dns-01 challenge. Trouble creating a certificate? Use https://community.letsencrypt.org/ to ask.
|
| http://bytebunker.space/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 2a00:5da0:1000:1::28e5, Status 404
| http://bytebunker.space/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 185.146.3.52, Status -14
| Fatal: Check of /.well-known/acme-challenge/random-filename has different answers checking ipv6 / ipv4. Ipv6 doesn't have the expected result http status 404 - Not Found. Creating a Letsencrypt certificate via http-01 validation may not work. Checking the validation file in /.well-known/acme-challenge Letsencrypt prefers ipv6. Two options: Remove your ipv6 / AAAA DNS entry or (better) fix your ipv6, so your webserver handles ipv6 correct. Perhaps add "Listen [::]:80". Don't use <VirtualHost ip-address:80>, switch to <VirtualHost *:80>. If you use IIS, check your bindings. Don't select a single ip address. Use this tool to check your raw ipv6 address. Add your domain name in the "Hostname" - field. Trouble creating a certificate? Use https://community.letsencrypt.org/ to ask.
|
| A | Info: No img element found, no alt attribute checked
|
| A | Good: Domainname is not on the "Specially Designated Nationals And Blocked Persons List" (SDN). That's an US-list of individuals and companies owned or controlled by, or acting for or on behalf of, targeted countries. It also lists individuals, groups, and entities, such as terrorists and narcotics traffickers designated under programs that are not country-specific. Collectively, such individuals and companies are called "Specially Designated Nationals" or "SDNs." Their assets are blocked and U.S. persons are generally prohibited from dealing with them. So if a domain name is on that list, it's impossible to create a Letsencrypt certificate with that domain name. Check the list manual - https://www.treasury.gov/resource-center/sanctions/sdn-list/pages/default.aspx
|
| A | Duration: 195557 milliseconds, 195.557 seconds
|
%22%20style=%22background-color:rgb(255,255,255)%22%3e%3c/svg%3e)