| 1. General Results, most used to calculate the result |
| A | name "filehaus.su" is domain, public suffix is ".su", top-level-domain is ".su", top-level-domain-type is "country-code", Country is Soviet Union (USSR), tld-manager is "Russian Institute for Development of Public Networks
(ROSNIIROS)", num .su-domains preloaded: 116 (complete: 245733)
|
| A | Good: All ip addresses are public addresses
|
| A | Good: Minimal 2 ip addresses per domain name found: filehaus.su has 2 different ip addresses (authoritative).
|
| A | Good: Minimal 2 ip addresses per domain name found: www.filehaus.su has 2 different ip addresses (authoritative).
|
| A | Good: Ipv4 and Ipv6 addresses per domain name found: filehaus.su has 1 ipv4, 1 ipv6 addresses
|
| A | Good: Ipv4 and Ipv6 addresses per domain name found: www.filehaus.su has 1 ipv4, 1 ipv6 addresses
|
| 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: More then one ip address per domain name found, checking all ip addresses the same http status and the same certificate found: Domain filehaus.su, 2 ip addresses.
|
| 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 www.filehaus.su, 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 filehaus.su, 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.filehaus.su, 2 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.filehaus.su
|
| 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:: 10 Root-climbing DNS Queries required to find all IPv4- and IPv6-Addresses of 3 Name Servers.
|
| A | Info:: 10 Queries complete, 4 with IPv6, 6 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.
|
| Ok (4 - 8):: An average of 3.3 queries per domain name server required to find all ip addresses of all name servers.
|
| A | Info:: 3 different Name Servers found: a.dnspod.com, b.dnspod.com, c.dnspod.com, 3 Name Servers included in Delegation: a.dnspod.com, b.dnspod.com, c.dnspod.com, 3 Name Servers included in 1 Zone definitions: a.dnspod.com, b.dnspod.com, c.dnspod.com, 1 Name Servers listed in SOA.Primary: a.dnspod.com.
|
| A | Good: Only one SOA.Primary Name Server found.: a.dnspod.com.
|
| A | Good: SOA.Primary Name Server included in the delegation set.: a.dnspod.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: a.dnspod.com, b.dnspod.com, c.dnspod.com
|
| 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: 3 different Name Servers found
|
| Warning: No Name Server IPv6 address found. IPv6 is the future, so your name servers should be visible via IPv6.: 3 different Name Servers found
|
| Warning: All Name Servers have the same Top Level Domain / Public Suffix. If there is a problem with that Top Level Domain, your domain may be affected. Better: Use Name Servers with different top level domains.: 3 Name Servers, 1 Top Level Domain: com
|
| Warning: All Name Servers have the same domain name. If there is a problem with that domain name (or with the name servers of that domain name), your domain may be affected. Better: Use Name Servers with different domain names / different top level domains.: Only one domain name used: dnspod.com
|
| A | Good: Name servers with different Country locations found: 3 Name Servers, 3 Countries: CN, HK, US
|
| A | Info: Ipv4-Subnet-list: 10 Name Servers, 8 different subnets (first Byte): 112., 117., 125., 129., 163., 170., 36., 43., 9 different subnets (first two Bytes): 112.80., 117.135., 117.89., 125.94., 129.226., 163.177., 170.106., 36.155., 43.135., 10 different subnets (first three Bytes): 112.80.181., 117.135.128., 117.89.178., 125.94.59., 129.226.102., 163.177.5., 170.106.49., 170.106.61., 36.155.149., 43.135.105.
|
| A | Good: Name Server IPv4-addresses from different subnet found:
|
| A | Good: Nameserver supports TCP connections: 10 good Nameserver
|
| X | Nameserver Timeout checking Echo Capitalization: a.dnspod.com
|
| X | Nameserver Timeout checking Echo Capitalization: a.dnspod.com / 43.135.105.134
|
| X | Nameserver Timeout checking Echo Capitalization: c.dnspod.com / 129.226.102.246
|
| X | Nameserver Timeout checking EDNS512: c.dnspod.com / 129.226.102.246
|
| Nameserver doesn't pass all EDNS-Checks: a.dnspod.com: OP100: fatal timeout. FLAGS: fatal timeout. V1: fatal timeout. V1OP100: fatal timeout. V1FLAGS: ok. DNSSEC: fatal timeout. V1DNSSEC: ok. NSID: fatal timeout. COOKIE: fatal timeout. CLIENTSUBNET: fatal timeout.
|
| Nameserver doesn't pass all EDNS-Checks: a.dnspod.com / 43.135.105.134: OP100: fatal timeout. FLAGS: fatal timeout. V1: fatal timeout. V1OP100: fatal timeout. V1FLAGS: fatal timeout. DNSSEC: ok. V1DNSSEC: fatal timeout. NSID: fatal timeout. COOKIE: fatal timeout. CLIENTSUBNET: fatal timeout.
|
| Nameserver doesn't pass all EDNS-Checks: b.dns.ripn.net: OP100: ok. FLAGS: ok. V1: ok. V1OP100: ok. V1FLAGS: ok. DNSSEC: ok. V1DNSSEC: ok. NSID: ok (std-tau-02.ripn.net). COOKIE: ok. CLIENTSUBNET: ok.
|
| Nameserver doesn't pass all EDNS-Checks: c.dnspod.com / 125.94.59.203: OP100: ok. FLAGS: ok. V1: ok. V1OP100: ok. V1FLAGS: fatal timeout. DNSSEC: ok. V1DNSSEC: ok. NSID: ok. COOKIE: ok. CLIENTSUBNET: ok.
|
| Nameserver doesn't pass all EDNS-Checks: c.dnspod.com / 129.226.102.246: OP100: fatal timeout. FLAGS: fatal timeout. V1: fatal timeout. V1OP100: fatal timeout. V1FLAGS: ok. DNSSEC: fatal timeout. V1DNSSEC: ok. NSID: ok. COOKIE: fatal timeout. CLIENTSUBNET: fatal timeout.
|
| 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://filehaus.su/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 89.213.174.204
|
| 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://filehaus.su/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 2a0f:9400:7e11:93e9::1
|
| 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.filehaus.su/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 89.213.174.204
|
| 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.filehaus.su/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 2a0f:9400:7e11:93e9::1
|
| 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.
|
| 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: 431464 milliseconds, 431.464 seconds
|