Check DNS, Urls + Redirects, Certificates and Content of your Website




V

Connect failure - perhaps firewall

Checked:
18.09.2023 23:37:15


Older results

No older results found


1. IP-Addresses

HostTypeIP-Addressis auth.∑ Queries∑ Timeout
nicolinux.org
A
80.67.16.8
Cologne/North Rhine-Westphalia/Germany (DE) - Host Europe GmbH
Hostname: twilight.ispgateway.de
yes
1
0

AAAA
2a00:1158:0:100::14
Strasbourg/Grand Est/France (FR) - Mass

yes


www.nicolinux.org
A
80.67.16.8
Cologne/North Rhine-Westphalia/Germany (DE) - Host Europe GmbH
Hostname: twilight.ispgateway.de
yes
1
0

AAAA
2a00:1158:0:100::14
Strasbourg/Grand Est/France (FR) - Mass

yes


*.nicolinux.org
A
80.67.16.8
yes



AAAA
2a00:1158:0:100::14
yes



CNAME

yes



2. DNSSEC

Zone (*)DNSSEC - Informations

Zone: (root)
(root)
1 DS RR published



DS with Algorithm 8, KeyTag 20326, DigestType 2 and Digest 4G1EuAuPHTmpXAsNfGXQhFjogECbvGg0VxBCN8f47I0=



Status: Valid because published



2 DNSKEY RR found



Public Key with Algorithm 8, KeyTag 11019, Flags 256



Public Key with Algorithm 8, KeyTag 20326, Flags 257 (SEP = Secure Entry Point)



1 RRSIG RR to validate DNSKEY RR found



RRSIG-Owner (root), Algorithm: 8, 0 Labels, original TTL: 172800 sec, Signature-expiration: 30.09.2023, 00:00:00 +, Signature-Inception: 09.09.2023, 00:00:00 +, KeyTag 20326, Signer-Name: (root)



Status: Good - Algorithmus 8 and DNSKEY with KeyTag 20326 used to validate the DNSKEY RRSet



Status: Valid Chain of trust. Parent-DS with Algorithm 8, KeyTag 20326, DigestType 2 and Digest "4G1EuAuPHTmpXAsNfGXQhFjogECbvGg0VxBCN8f47I0=" validates local Key with the same values, Key ist Secure Entry Point (SEP) of the zone

Zone: org
org
1 DS RR in the parent zone found



DS with Algorithm 8, KeyTag 26974, DigestType 2 and Digest T+3ilMU/Q4oVjEHTlInNeKhr6w2KCur/FHRcDRbh3jI=



1 RRSIG RR to validate DS RR found



RRSIG-Owner org., Algorithm: 8, 1 Labels, original TTL: 86400 sec, Signature-expiration: 01.10.2023, 21:00:00 +, Signature-Inception: 18.09.2023, 20:00:00 +, KeyTag 11019, Signer-Name: (root)



Status: Good - Algorithmus 8 and DNSKEY with KeyTag 11019 used to validate the DS RRSet in the parent zone



3 DNSKEY RR found



Public Key with Algorithm 8, KeyTag 26974, Flags 257 (SEP = Secure Entry Point)



Public Key with Algorithm 8, KeyTag 35418, Flags 256



Public Key with Algorithm 8, KeyTag 61110, Flags 256



1 RRSIG RR to validate DNSKEY RR found



RRSIG-Owner org., Algorithm: 8, 1 Labels, original TTL: 3600 sec, Signature-expiration: 08.10.2023, 15:23:17 +, Signature-Inception: 17.09.2023, 14:23:17 +, KeyTag 26974, Signer-Name: org



Status: Good - Algorithmus 8 and DNSKEY with KeyTag 26974 used to validate the DNSKEY RRSet



Status: Valid Chain of trust. Parent-DS with Algorithm 8, KeyTag 26974, DigestType 2 and Digest "T+3ilMU/Q4oVjEHTlInNeKhr6w2KCur/FHRcDRbh3jI=" validates local Key with the same values, Key ist Secure Entry Point (SEP) of the zone

Zone: nicolinux.org
nicolinux.org
0 DS RR in the parent zone found



DS-Query in the parent zone has a valid NSEC3 RR as result with the hashed query name "6mjogd7ido3u3juass0df5mbvhq9ked2" between the hashed NSEC3-owner "6mjhbt74v6d0hns98i56stha9gcfdsv1" and the hashed NextOwner "6mjovhq22cu669o34inbefbts9sbtere". So the parent zone confirmes the not-existence of a DS RR.
Bitmap: NS, DS, RRSIG Validated: RRSIG-Owner 6mjhbt74v6d0hns98i56stha9gcfdsv1.org., Algorithm: 8, 2 Labels, original TTL: 3600 sec, Signature-expiration: 08.10.2023, 15:23:17 +, Signature-Inception: 17.09.2023, 14:23:17 +, KeyTag 35418, Signer-Name: org



DS-Query in the parent zone sends valid NSEC3 RR with the Hash "gdtpongmpok61u9lvnipqor8lra9l4t0" as Owner. That's the Hash of "org" with the NextHashedOwnerName "gdtrea8kmj2rneqen4m2ogj26kfsukj7". So that domain name is the Closest Encloser of "nicolinux.org". Opt-Out: True.
Bitmap: NS, SOA, RRSIG, DNSKEY, NSEC3PARAM Validated: RRSIG-Owner gdtpongmpok61u9lvnipqor8lra9l4t0.org., Algorithm: 8, 2 Labels, original TTL: 3600 sec, Signature-expiration: 09.10.2023, 21:34:39 +, Signature-Inception: 18.09.2023, 20:34:39 +, KeyTag 35418, Signer-Name: org



0 DNSKEY RR found




Zone: www.nicolinux.org
www.nicolinux.org
0 DS RR in the parent zone found


3. Name Servers

DomainNameserverNS-IP
www.nicolinux.org
  ns71.domaincontrol.com / hex:0D 70 32 33

nicolinux.org
  ns71.domaincontrol.com / hex:0D 70 32 33
97.74.105.46
Tempe/Arizona/United States (US) - Host Europe GmbH


 
2603:5:2194::2e
Tempe/Arizona/United States (US) - Host Europe GmbH


  ns72.domaincontrol.com / hex:0D 70 30 38
173.201.73.46
Tempe/Arizona/United States (US) - Host Europe GmbH


 
2603:5:2294::2e
Tempe/Arizona/United States (US) - Host Europe GmbH

org
  a0.org.afilias-nst.info / app28.nrt1.hosts.meta.redstone.afilias-nst.info-1615580861


  a2.org.afilias-nst.info / FRA3


  b0.org.afilias-nst.org / app6.ams2.hosts.meta.redstone.afilias-nst.info-1615580861


  b2.org.afilias-nst.org / FRA4


  c0.org.afilias-nst.info / app21.nrt1.hosts.meta.redstone.afilias-nst.info-1615580861


  d0.org.afilias-nst.org / app28.nrt1.hosts.meta.redstone.afilias-nst.info-1615580861


4. SOA-Entries


Domain:org
Zone-Name:org
Primary:a0.org.afilias-nst.info
Mail:hostmaster.donuts.email
Serial:1695072477
Refresh:7200
Retry:900
Expire:1209600
TTL:3600
num Entries:6


Domain:nicolinux.org
Zone-Name:nicolinux.org
Primary:ns71.domaincontrol.com
Mail:dns.jomax.net
Serial:2023091801
Refresh:28800
Retry:7200
Expire:604800
TTL:600
num Entries:4


Domain:www.nicolinux.org
Zone-Name:nicolinux.org
Primary:ns71.domaincontrol.com
Mail:dns.jomax.net
Serial:2023091801
Refresh:28800
Retry:7200
Expire:604800
TTL:600
num Entries:1


5. Screenshots

No Screenshot listed, because no url-check with https + http status 200-299, 400-599 + not-ACME-check found.

6. Url-Checks


:

:
DomainnameHttp-StatusredirectSec.G
• http://nicolinux.org/
80.67.16.8
302
http://leere.seite
Html is minified: 111.29 %
0.076
D
Server: nginx
Date: Mon, 18 Sep 2023 21:38:13 GMT
Content-Type: text/html
Content-Length: 138
Connection: close
Location: http://leere.seite

• http://nicolinux.org/
2a00:1158:0:100::14
302
http://leere.seite
Html is minified: 111.29 %
0.074
D
Server: nginx
Date: Mon, 18 Sep 2023 21:38:13 GMT
Content-Type: text/html
Content-Length: 138
Connection: close
Location: http://leere.seite

• http://www.nicolinux.org/
80.67.16.8
302
http://leere.seite
Html is minified: 111.29 %
0.040
D
Server: nginx
Date: Mon, 18 Sep 2023 21:38:13 GMT
Content-Type: text/html
Content-Length: 138
Connection: close
Location: http://leere.seite

• http://www.nicolinux.org/
2a00:1158:0:100::14
302
http://leere.seite
Html is minified: 111.29 %
0.047
D
Server: nginx
Date: Mon, 18 Sep 2023 21:38:13 GMT
Content-Type: text/html
Content-Length: 138
Connection: close
Location: http://leere.seite

• http://leere.seite

-1

0.017
R
NameResolutionFailure - The remote name could not be resolved: 'leere.seite'

• https://nicolinux.org/
80.67.16.8
-2

1.073
V
ConnectFailure - Unable to connect to the remote server

• https://nicolinux.org/
2a00:1158:0:100::14
-14

10.034
T
Timeout - The operation has timed out

• https://www.nicolinux.org/
80.67.16.8
-2

1.060
V
ConnectFailure - Unable to connect to the remote server

• https://www.nicolinux.org/
2a00:1158:0:100::14
-14

10.053
T
Timeout - The operation has timed out

• http://nicolinux.org/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
80.67.16.8
Inline-JavaScript (∑/total): 0/0 Inline-CSS (∑/total): 0/0
302
http://leere.seite
Html is minified: 111.29 %
0.053
D
Visible Content: 302 Found nginx
Server: nginx
Date: Mon, 18 Sep 2023 21:38:35 GMT
Content-Type: text/html
Content-Length: 138
Connection: close
Location: http://leere.seite

• http://nicolinux.org/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
2a00:1158:0:100::14
Inline-JavaScript (∑/total): 0/0 Inline-CSS (∑/total): 0/0
302
http://leere.seite
Html is minified: 111.29 %
0.086
D
Visible Content: 302 Found nginx
Server: nginx
Date: Mon, 18 Sep 2023 21:38:36 GMT
Content-Type: text/html
Content-Length: 138
Connection: close
Location: http://leere.seite

• http://www.nicolinux.org/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
80.67.16.8
Inline-JavaScript (∑/total): 0/0 Inline-CSS (∑/total): 0/0
302
http://leere.seite
Html is minified: 111.29 %
0.054
D
Visible Content: 302 Found nginx
Server: nginx
Date: Mon, 18 Sep 2023 21:38:36 GMT
Content-Type: text/html
Content-Length: 138
Connection: close
Location: http://leere.seite

• http://www.nicolinux.org/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
2a00:1158:0:100::14
Inline-JavaScript (∑/total): 0/0 Inline-CSS (∑/total): 0/0
302
http://leere.seite
Html is minified: 111.29 %
0.047
D
Visible Content: 302 Found nginx
Server: nginx
Date: Mon, 18 Sep 2023 21:38:36 GMT
Content-Type: text/html
Content-Length: 138
Connection: close
Location: http://leere.seite

• https://80.67.16.8/
80.67.16.8
-2

1.057
V
ConnectFailure - Unable to connect to the remote server

• https://[2a00:1158:0000:0100:0000:0000:0000:0014]/
2a00:1158:0:100::14
-14

10.033
T
Timeout - The operation has timed out

7. Comments


1. General Results, most used to calculate the result

Aname "nicolinux.org" is domain, public suffix is ".org", top-level-domain is ".org", top-level-domain-type is "generic", tld-manager is "Public Interest Registry (PIR)", num .org-domains preloaded: 7880 (complete: 231048)
AGood: All ip addresses are public addresses
AGood: Minimal 2 ip addresses per domain name found: nicolinux.org has 2 different ip addresses (authoritative).
AGood: Minimal 2 ip addresses per domain name found: www.nicolinux.org has 2 different ip addresses (authoritative).
AGood: Ipv4 and Ipv6 addresses per domain name found: nicolinux.org has 1 ipv4, 1 ipv6 addresses
AGood: Ipv4 and Ipv6 addresses per domain name found: www.nicolinux.org has 1 ipv4, 1 ipv6 addresses
AGood: No asked Authoritative Name Server had a timeout
AGood: 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.
CError - no version with Http-Status 200
Dhttp://nicolinux.org/ 80.67.16.8
302
http://leere.seite
Wrong redirect one domain http to other domain http. First redirect to https without changing the domain, so no new dns query is required. So the server can send the HSTS header. That's fundamental using HSTS (Http Strict Transport Security). First step: Add correct redirects http ⇒ https. 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. Then recheck your domain, should be Grade C. There is the rule to select one https version as preferred version.
Dhttp://nicolinux.org/ 2a00:1158:0:100::14
302
http://leere.seite
Wrong redirect one domain http to other domain http. First redirect to https without changing the domain, so no new dns query is required. So the server can send the HSTS header. That's fundamental using HSTS (Http Strict Transport Security). First step: Add correct redirects http ⇒ https. 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. Then recheck your domain, should be Grade C. There is the rule to select one https version as preferred version.
Dhttp://www.nicolinux.org/ 80.67.16.8
302
http://leere.seite
Wrong redirect one domain http to other domain http. First redirect to https without changing the domain, so no new dns query is required. So the server can send the HSTS header. That's fundamental using HSTS (Http Strict Transport Security). First step: Add correct redirects http ⇒ https. 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. Then recheck your domain, should be Grade C. There is the rule to select one https version as preferred version.
Dhttp://www.nicolinux.org/ 2a00:1158:0:100::14
302
http://leere.seite
Wrong redirect one domain http to other domain http. First redirect to https without changing the domain, so no new dns query is required. So the server can send the HSTS header. That's fundamental using HSTS (Http Strict Transport Security). First step: Add correct redirects http ⇒ https. 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. Then recheck your domain, should be Grade C. There is the rule to select one https version as preferred version.
Dhttp://nicolinux.org/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 80.67.16.8
302
http://leere.seite
Wrong redirect one domain http to other domain http. First redirect to https without changing the domain, so no new dns query is required. So the server can send the HSTS header. That's fundamental using HSTS (Http Strict Transport Security). First step: Add correct redirects http ⇒ https. 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. Then recheck your domain, should be Grade C. There is the rule to select one https version as preferred version.
Dhttp://nicolinux.org/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 2a00:1158:0:100::14
302
http://leere.seite
Wrong redirect one domain http to other domain http. First redirect to https without changing the domain, so no new dns query is required. So the server can send the HSTS header. That's fundamental using HSTS (Http Strict Transport Security). First step: Add correct redirects http ⇒ https. 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. Then recheck your domain, should be Grade C. There is the rule to select one https version as preferred version.
Dhttp://www.nicolinux.org/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 80.67.16.8
302
http://leere.seite
Wrong redirect one domain http to other domain http. First redirect to https without changing the domain, so no new dns query is required. So the server can send the HSTS header. That's fundamental using HSTS (Http Strict Transport Security). First step: Add correct redirects http ⇒ https. 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. Then recheck your domain, should be Grade C. There is the rule to select one https version as preferred version.
Dhttp://www.nicolinux.org/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 2a00:1158:0:100::14
302
http://leere.seite
Wrong redirect one domain http to other domain http. First redirect to https without changing the domain, so no new dns query is required. So the server can send the HSTS header. That's fundamental using HSTS (Http Strict Transport Security). First step: Add correct redirects http ⇒ https. 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. Then recheck your domain, should be Grade C. There is the rule to select one https version as preferred version.
HFatal error: No https - result with http-status 200, no encryption
Khttps://nicolinux.org/ 80.67.16.8, Status -2

https://nicolinux.org/ 2a00:1158:0:100::14, Status -14
Configuration problem - different ip addresses with different status
Khttps://www.nicolinux.org/ 80.67.16.8, Status -2

https://www.nicolinux.org/ 2a00:1158:0:100::14, Status -14
Configuration problem - different ip addresses with different status
Rhttp://nicolinux.org/ 80.67.16.8
302
http://leere.seite
Redirect to not existing domain
Rhttp://nicolinux.org/ 2a00:1158:0:100::14
302
http://leere.seite
Redirect to not existing domain
Rhttp://www.nicolinux.org/ 80.67.16.8
302
http://leere.seite
Redirect to not existing domain
Rhttp://www.nicolinux.org/ 2a00:1158:0:100::14
302
http://leere.seite
Redirect to not existing domain
Rhttp://nicolinux.org/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 80.67.16.8
302
http://leere.seite
Redirect to not existing domain
Rhttp://nicolinux.org/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 2a00:1158:0:100::14
302
http://leere.seite
Redirect to not existing domain
Rhttp://www.nicolinux.org/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 80.67.16.8
302
http://leere.seite
Redirect to not existing domain
Rhttp://www.nicolinux.org/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 2a00:1158:0:100::14
302
http://leere.seite
Redirect to not existing domain
Vhttps://nicolinux.org/ 80.67.16.8
-2

Connect failure - perhaps firewall
Vhttps://www.nicolinux.org/ 80.67.16.8
-2

Connect failure - perhaps firewall
Vhttps://80.67.16.8/ 80.67.16.8
-2

Connect failure - perhaps firewall
AGood: More then one ip address per domain name found, checking all ip addresses the same http status and the same certificate found: Domain nicolinux.org, 2 ip addresses.
AGood: More then one ip address per domain name found, checking all ip addresses the same http status and the same certificate found: Domain www.nicolinux.org, 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 nicolinux.org, 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.nicolinux.org, 2 ip addresses.
AGood: _mta-sts TXT record found (mta-sts: Mail Transfer Agent Strict Transport Security - see RFC 8461). Domainname: _mta-sts.nicolinux.org
BBad: _mta-sts TXT found, but invalid

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

AInfo:: 27 Root-climbing DNS Queries required to find all IPv4- and IPv6-Addresses of 2 Name Servers.
AInfo:: 27 Queries complete, 27 with IPv6, 0 with IPv4.
AGood: All DNS Queries done via IPv6.
Bad (greater 8):: An average of 13.5 queries per domain name server required to find all ip addresses of all name servers.
AInfo:: 2 different Name Servers found: ns71.domaincontrol.com, ns72.domaincontrol.com, 2 Name Servers included in Delegation: ns71.domaincontrol.com, ns72.domaincontrol.com, 2 Name Servers included in 1 Zone definitions: ns71.domaincontrol.com, ns72.domaincontrol.com, 1 Name Servers listed in SOA.Primary: ns71.domaincontrol.com.
AGood: Only one SOA.Primary Name Server found.: ns71.domaincontrol.com.
AGood: SOA.Primary Name Server included in the delegation set.: ns71.domaincontrol.com.
AGood: 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: ns71.domaincontrol.com, ns72.domaincontrol.com
AGood: All Name Server Domain Names have a Public Suffix.
AGood: All Name Server Domain Names ending with a Public Suffix have minimal one IPv4- or IPv6 address.
AGood: All Name Server ip addresses are public.
AGood: Minimal 2 different name servers (public suffix and public ip address) found: 2 different Name Servers found
AGood: All name servers have ipv4- and ipv6-addresses.: 2 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.: 2 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: domaincontrol.com
Warning: All Name Servers from the same Country / IP location.: 2 Name Servers, 1 Countries: US
AInfo: Ipv4-Subnet-list: 2 Name Servers, 2 different subnets (first Byte): 173., 97., 2 different subnets (first two Bytes): 173.201., 97.74., 2 different subnets (first three Bytes): 173.201.73., 97.74.105.
AExcellent: Every Name Server IPv4-address starts with an unique Byte.
AInfo: IPv6-Subnet-list: 2 Name Servers with IPv6, 1 different subnets (first block): 2603:, 1 different subnets (first two blocks): 2603:0005:, 2 different subnets (first three blocks): 2603:0005:2194:, 2603:0005:2294:, 2 different subnets (first four blocks): 2603:0005:2194:0000:, 2603:0005:2294:0000:
AGood: Name Server IPv6 addresses from different subnets found.
AGood: Nameserver supports TCP connections: 4 good Nameserver
AGood: Nameserver supports Echo Capitalization: 4 good Nameserver
AGood: Nameserver supports EDNS with max. 512 Byte Udp payload, message is smaller: 4 good Nameserver
AGood: Nameserver has passed 10 EDNS-Checks (OP100, FLAGS, V1, V1OP100, V1FLAGS, DNSSEC, V1DNSSEC, NSID, COOKIE, CLIENTSUBNET): 4 good Nameserver
AGood: 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

Fatal: All checks of /.well-known/acme-challenge/random-filename have a redirect, destination doesn't have the random filename. Creating a Letsencrypt certificate via http-01 challenge may not work. Trouble creating a certificate? Use https://community.letsencrypt.org/ to ask.
AInfo: No img element found, no alt attribute checked
AGood: 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
ADuration: 119267 milliseconds, 119.267 seconds


8. Connections

No connection informations found. Perhaps only http - connections.


9. Certificates

No certificate informations found. Perhaps only http - connections.


10. Last Certificates - Certificate Transparency Log Check

1. Source CertSpotter - active certificates (one check per day)

Issuerlast 7 daysactivenum Certs
CN=R3, O=Let's Encrypt, C=US
0
0
1
CN=ZeroSSL ECC Domain Secure Site CA, O=ZeroSSL, C=AT
0
0
1

CertSpotter-IdIssuernot beforenot afterDomain namesLE-Duplicatenext LE
5850127851
leaf cert
CN=R3, O=Let's Encrypt, C=US
2023-09-14 16:25:56
2023-12-13 16:25:55
nicolinux.org - 1 entries


5850089307
leaf cert
CN=ZeroSSL ECC Domain Secure Site CA, O=ZeroSSL, C=AT
2023-09-14 00:00:00
2023-12-13 23:59:59
nicolinux.org - 1 entries



2. Source crt.sh - old and new certificates, sometimes very slow - only certificates with "not after" > of the last months are listed

No CRT - CT-Log entries found


11. Html-Content - Entries

No Html-Content entries found. Only checked if https + status 200/401/403/404


12. Nameserver - IP-Adresses

Required Root-climbing DNS-Queries to find ip addresses of all Name Servers: ns71.domaincontrol.com, ns72.domaincontrol.com

QNr.DomainTypeNS used
1
com
NS
d.root-servers.net (2001:500:2d::d)

Answer: a.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net, e.gtld-servers.net, f.gtld-servers.net, g.gtld-servers.net, h.gtld-servers.net, i.gtld-servers.net, j.gtld-servers.net, k.gtld-servers.net, l.gtld-servers.net, m.gtld-servers.net
2
ns71.domaincontrol.com
NS
a.gtld-servers.net (2001:503:a83e::2:30)

Answer: a1-245.akam.net, a11-64.akam.net, a20-65.akam.net, a6-66.akam.net, a8-67.akam.net, a9-67.akam.net, ans01.domaincontrol.com, ans02.domaincontrol.com

Answer: ans01.domaincontrol.com
2603:5:2111::23, 97.74.97.35

Answer: ans02.domaincontrol.com
173.201.65.35, 2603:5:2211::23
3
ns72.domaincontrol.com
NS
a.gtld-servers.net (2001:503:a83e::2:30)

Answer: a1-245.akam.net, a11-64.akam.net, a20-65.akam.net, a6-66.akam.net, a8-67.akam.net, a9-67.akam.net, ans01.domaincontrol.com, ans02.domaincontrol.com

Answer: ans01.domaincontrol.com
2603:5:2111::23, 97.74.97.35

Answer: ans02.domaincontrol.com
173.201.65.35, 2603:5:2211::23
4
net
NS
m.root-servers.net (2001:dc3::35)

Answer: a.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net, e.gtld-servers.net, f.gtld-servers.net, g.gtld-servers.net, h.gtld-servers.net, i.gtld-servers.net, j.gtld-servers.net, k.gtld-servers.net, l.gtld-servers.net, m.gtld-servers.net
5
a1-245.akam.net
NS
l.gtld-servers.net (2001:500:d937::30)

Answer: a1-67.akam.net, a11-67.akam.net, a12-67.akam.net, a13-67.akam.net, a18-67.akam.net, a22-67.akam.net, a28-67.akam.net, a3-67.akam.net, a4-67.akam.net, a5-67.akam.net, a6-67.akam.net, a7-67.akam.net, a9-67.akam.net

Answer: a1-67.akam.net
193.108.91.67, 2600:1401:2::43

Answer: a11-67.akam.net
84.53.139.67

Answer: a12-67.akam.net
184.26.160.67

Answer: a13-67.akam.net
2.22.230.67

Answer: a18-67.akam.net
95.101.36.67

Answer: a22-67.akam.net
23.211.61.67

Answer: a28-67.akam.net
95.100.173.67

Answer: a3-67.akam.net
96.7.49.67

Answer: a5-67.akam.net
95.100.168.67

Answer: a7-67.akam.net
23.61.199.67

Answer: a9-67.akam.net
184.85.248.67
6
a11-64.akam.net
NS
l.gtld-servers.net (2001:500:d937::30)

Answer: a1-67.akam.net, a11-67.akam.net, a12-67.akam.net, a13-67.akam.net, a18-67.akam.net, a22-67.akam.net, a28-67.akam.net, a3-67.akam.net, a4-67.akam.net, a5-67.akam.net, a6-67.akam.net, a7-67.akam.net, a9-67.akam.net

Answer: a1-67.akam.net
193.108.91.67, 2600:1401:2::43

Answer: a11-67.akam.net
84.53.139.67

Answer: a12-67.akam.net
184.26.160.67

Answer: a13-67.akam.net
2.22.230.67

Answer: a18-67.akam.net
95.101.36.67

Answer: a22-67.akam.net
23.211.61.67

Answer: a28-67.akam.net
95.100.173.67

Answer: a3-67.akam.net
96.7.49.67

Answer: a5-67.akam.net
95.100.168.67

Answer: a7-67.akam.net
23.61.199.67

Answer: a9-67.akam.net
184.85.248.67
7
a20-65.akam.net
NS
l.gtld-servers.net (2001:500:d937::30)

Answer: a1-67.akam.net, a11-67.akam.net, a12-67.akam.net, a13-67.akam.net, a18-67.akam.net, a22-67.akam.net, a28-67.akam.net, a3-67.akam.net, a4-67.akam.net, a5-67.akam.net, a6-67.akam.net, a7-67.akam.net, a9-67.akam.net

Answer: a1-67.akam.net
193.108.91.67, 2600:1401:2::43

Answer: a11-67.akam.net
84.53.139.67

Answer: a12-67.akam.net
184.26.160.67

Answer: a13-67.akam.net
2.22.230.67

Answer: a18-67.akam.net
95.101.36.67

Answer: a22-67.akam.net
23.211.61.67

Answer: a28-67.akam.net
95.100.173.67

Answer: a3-67.akam.net
96.7.49.67

Answer: a5-67.akam.net
95.100.168.67

Answer: a7-67.akam.net
23.61.199.67

Answer: a9-67.akam.net
184.85.248.67
8
a6-66.akam.net
NS
l.gtld-servers.net (2001:500:d937::30)

Answer: a1-67.akam.net, a11-67.akam.net, a12-67.akam.net, a13-67.akam.net, a18-67.akam.net, a22-67.akam.net, a28-67.akam.net, a3-67.akam.net, a4-67.akam.net, a5-67.akam.net, a6-67.akam.net, a7-67.akam.net, a9-67.akam.net

Answer: a1-67.akam.net
193.108.91.67, 2600:1401:2::43

Answer: a11-67.akam.net
84.53.139.67

Answer: a12-67.akam.net
184.26.160.67

Answer: a13-67.akam.net
2.22.230.67

Answer: a18-67.akam.net
95.101.36.67

Answer: a22-67.akam.net
23.211.61.67

Answer: a28-67.akam.net
95.100.173.67

Answer: a3-67.akam.net
96.7.49.67

Answer: a5-67.akam.net
95.100.168.67

Answer: a7-67.akam.net
23.61.199.67

Answer: a9-67.akam.net
184.85.248.67
9
a8-67.akam.net
NS
l.gtld-servers.net (2001:500:d937::30)

Answer: a1-67.akam.net, a11-67.akam.net, a12-67.akam.net, a13-67.akam.net, a18-67.akam.net, a22-67.akam.net, a28-67.akam.net, a3-67.akam.net, a4-67.akam.net, a5-67.akam.net, a6-67.akam.net, a7-67.akam.net, a9-67.akam.net

Answer: a1-67.akam.net
193.108.91.67, 2600:1401:2::43

Answer: a11-67.akam.net
84.53.139.67

Answer: a12-67.akam.net
184.26.160.67

Answer: a13-67.akam.net
2.22.230.67

Answer: a18-67.akam.net
95.101.36.67

Answer: a22-67.akam.net
23.211.61.67

Answer: a28-67.akam.net
95.100.173.67

Answer: a3-67.akam.net
96.7.49.67

Answer: a5-67.akam.net
95.100.168.67

Answer: a7-67.akam.net
23.61.199.67

Answer: a9-67.akam.net
184.85.248.67
10
a4-67.akam.net: 72.246.46.67
NS
l.gtld-servers.net (2001:500:d937::30)

Answer: a1-67.akam.net
193.108.91.67, 2600:1401:2::43

Answer: a11-67.akam.net
84.53.139.67

Answer: a12-67.akam.net
184.26.160.67

Answer: a13-67.akam.net
2.22.230.67

Answer: a18-67.akam.net
95.101.36.67

Answer: a22-67.akam.net
23.211.61.67

Answer: a28-67.akam.net
95.100.173.67

Answer: a3-67.akam.net
96.7.49.67

Answer: a5-67.akam.net
95.100.168.67

Answer: a7-67.akam.net
23.61.199.67

Answer: a9-67.akam.net
184.85.248.67
11
a6-67.akam.net
NS
l.gtld-servers.net (2001:500:d937::30)

Answer: a1-67.akam.net, a11-67.akam.net, a12-67.akam.net, a13-67.akam.net, a18-67.akam.net, a22-67.akam.net, a28-67.akam.net, a3-67.akam.net, a4-67.akam.net, a5-67.akam.net, a6-67.akam.net, a7-67.akam.net, a9-67.akam.net

Answer: a1-67.akam.net
193.108.91.67, 2600:1401:2::43

Answer: a11-67.akam.net
84.53.139.67

Answer: a12-67.akam.net
184.26.160.67

Answer: a13-67.akam.net
2.22.230.67

Answer: a18-67.akam.net
95.101.36.67

Answer: a22-67.akam.net
23.211.61.67

Answer: a28-67.akam.net
95.100.173.67

Answer: a3-67.akam.net
96.7.49.67

Answer: a4-67.akam.net
72.246.46.67

Answer: a5-67.akam.net
95.100.168.67

Answer: a7-67.akam.net
23.61.199.67

Answer: a9-67.akam.net
184.85.248.67
12
a1-245.akam.net: 193.108.91.245
A
a1-67.akam.net (2600:1401:2::43)
13
a1-245.akam.net: 2600:1401:2::f5
AAAA
a1-67.akam.net (2600:1401:2::43)
14
a11-64.akam.net: 84.53.139.64
A
a1-67.akam.net (2600:1401:2::43)
15
a11-64.akam.net: 2600:1480:1::40
AAAA
a1-67.akam.net (2600:1401:2::43)
16
a20-65.akam.net: 95.100.175.65
A
a1-67.akam.net (2600:1401:2::43)
17
a20-65.akam.net: 2a02:26f0:67::41
AAAA
a1-67.akam.net (2600:1401:2::43)
18
a6-66.akam.net: 23.211.133.66
A
a1-67.akam.net (2600:1401:2::43)
19
a6-66.akam.net: 2600:1401:1::42
AAAA
a1-67.akam.net (2600:1401:2::43)
20
a8-67.akam.net: 2.16.40.67
A
a1-67.akam.net (2600:1401:2::43)
21
a8-67.akam.net: 2600:1403:a::43
AAAA
a1-67.akam.net (2600:1401:2::43)
22
a6-67.akam.net: 23.211.133.67
A
a1-67.akam.net (2600:1401:2::43)
23
a6-67.akam.net: 2600:1401:1::43
AAAA
a1-67.akam.net (2600:1401:2::43)
24
ns71.domaincontrol.com: 97.74.105.46
A
a1-245.akam.net (2600:1401:2::f5)
25
ns71.domaincontrol.com: 2603:5:2194::2e
AAAA
a1-245.akam.net (2600:1401:2::f5)
26
ns72.domaincontrol.com: 173.201.73.46
A
a1-245.akam.net (2600:1401:2::f5)
27
ns72.domaincontrol.com: 2603:5:2294::2e
AAAA
a1-245.akam.net (2600:1401:2::f5)


13. CAA - Entries

DomainnameflagNameValue∑ Queries∑ Timeout
www.nicolinux.org
0

no CAA entry found
1
0
nicolinux.org
0

no CAA entry found
1
0
org
0

no CAA entry found
1
0


14. TXT - Entries

DomainnameTXT EntryStatus∑ Queries∑ Timeout
nicolinux.org
v=spf1 mx include:ispgateway.de ~all
ok
1
0
www.nicolinux.org

ok
1
0
_acme-challenge.nicolinux.org
v=spf1 mx include:ispgateway.de ~all
missing entry or wrong length
1
0
_acme-challenge.www.nicolinux.org

Name Error - The domain name does not exist
1
0
_acme-challenge.nicolinux.org.nicolinux.org
v=spf1 mx include:ispgateway.de ~all
perhaps wrong
1
0
_acme-challenge.www.nicolinux.org.nicolinux.org
v=spf1 mx include:ispgateway.de ~all
perhaps wrong
1
0
_acme-challenge.www.nicolinux.org.www.nicolinux.org

Name Error - The domain name does not exist
1
0


15. DomainService - Entries

TypeDomainPrefValueDNS-errornum AnswersStatusDescription
MX

nicolinux.org
100
mxlb.ispgateway.de
01ok

A


80.67.18.126
01ok

CNAME


00ok
_mta-sts
TXT
_mta-sts.nicolinux.org

v=spf1 mx include:ispgateway.de ~all
2A MTA-STS TXT Entry (Mail Transfer Agent Strict Transport Security) must start with "'v=STSv1". Do you really want to create a MTA-STS? Or is it the effect of a wildcard * DNS?
_dmarc
TXT
_dmarc.nicolinux.org

v=spf1 mx include:ispgateway.de ~all
013A _dmarc TXT Entry must start with "'v=DMARC1". Do you really want to create a DMARC? Or is it the effect of a wildcard * DNS?



16. Cipher Suites

No results


17. Portchecks

No open Ports <> 80 / 443 found, so no additional Ports checked.



Permalink: https://check-your-website.server-daten.de/?i=a9bbb314-080a-4222-9b4f-5df563056c21


Last Result: https://check-your-website.server-daten.de/?q=nicolinux.org - 2023-09-18 23:37:15


Do you like this page? Support this tool, add a link on your page:

<a href="https://check-your-website.server-daten.de/?q=nicolinux.org" target="_blank">Check this Site: nicolinux.org</a>

Do you really want to support this project? Donate: Check-your-website, IBAN DE98 1001 0010 0575 2211 07, SWIFT/BIC PBNKDEFF, Euro