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

...

skip EDNS-Check

skip Content-Check

check links

Tls-Protocol error

Checked:
06.07.2025 09:24:14

Older results

No older results found

1. IP-Addresses

Host	Type	IP-Address	is auth.	∑ Queries	∑ Timeout
kimsserver.dk	A	87.57.145.116 Risskov/Central Jutland/Denmark (DK) - TDC Holding A/S Hostname: 87-57-145-116-cable.dk.customer.tdc.net	yes	1	0
	AAAA		yes
www.kimsserver.dk	A	87.57.145.116 Risskov/Central Jutland/Denmark (DK) - TDC Holding A/S Hostname: 87-57-145-116-cable.dk.customer.tdc.net	yes	1	0
	AAAA		yes
*.kimsserver.dk	A	87.57.145.116	yes
	AAAA		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


	4 DNSKEY RR found


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


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


	Public Key with Algorithm 8, KeyTag 46441, Flags 256


	Public Key with Algorithm 8, KeyTag 53148, Flags 256


	1 RRSIG RR to validate DNSKEY RR found


	RRSIG-Owner (root), Algorithm: 8, 0 Labels, original TTL: 172800 sec, Signature-expiration: 22.07.2025, 00:00:00 +, Signature-Inception: 01.07.2025, 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: dk
dk	1 DS RR in the parent zone found


	DS with Algorithm 13, KeyTag 20109, DigestType 2 and Digest XIamiuLDq3QYKzrQdJtG5V+JK4NflXjPoS+Qk/slK9A=


	1 RRSIG RR to validate DS RR found


	RRSIG-Owner dk., Algorithm: 8, 1 Labels, original TTL: 86400 sec, Signature-expiration: 19.07.2025, 05:00:00 +, Signature-Inception: 06.07.2025, 04:00:00 +, KeyTag 46441, Signer-Name: (root)


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


	2 DNSKEY RR found


	Public Key with Algorithm 13, KeyTag 300, Flags 256


	Public Key with Algorithm 13, KeyTag 20109, Flags 257 (SEP = Secure Entry Point)


	1 RRSIG RR to validate DNSKEY RR found


	RRSIG-Owner dk., Algorithm: 13, 1 Labels, original TTL: 86400 sec, Signature-expiration: 30.07.2025, 08:27:01 +, Signature-Inception: 02.07.2025, 06:57:01 +, KeyTag 20109, Signer-Name: dk


	• Status: Good - Algorithmus 13 and DNSKEY with KeyTag 20109 used to validate the DNSKEY RRSet


	• Status: Valid Chain of trust. Parent-DS with Algorithm 13, KeyTag 20109, DigestType 2 and Digest "XIamiuLDq3QYKzrQdJtG5V+JK4NflXjPoS+Qk/slK9A=" validates local Key with the same values, Key ist Secure Entry Point (SEP) of the zone

Zone: kimsserver.dk
kimsserver.dk	1 DS RR in the parent zone found


	DS with Algorithm 13, KeyTag 60349, DigestType 2 and Digest Dsilern8HivUx6YZ9iOOUbAbcZyy7tV4Nbo50EpTRig=


	1 RRSIG RR to validate DS RR found


	RRSIG-Owner kimsserver.dk., Algorithm: 13, 2 Labels, original TTL: 7200 sec, Signature-expiration: 28.07.2025, 11:54:01 +, Signature-Inception: 30.06.2025, 10:24:01 +, KeyTag 300, Signer-Name: dk


	• Status: Good - Algorithmus 13 and DNSKEY with KeyTag 300 used to validate the DS RRSet in the parent zone


	2 DNSKEY RR found


	Public Key with Algorithm 13, KeyTag 58901, Flags 256


	Public Key with Algorithm 13, KeyTag 60349, Flags 257 (SEP = Secure Entry Point)


	1 RRSIG RR to validate DNSKEY RR found


	RRSIG-Owner kimsserver.dk., Algorithm: 13, 2 Labels, original TTL: 600 sec, Signature-expiration: 17.07.2025, 00:00:00 +, Signature-Inception: 26.06.2025, 00:00:00 +, KeyTag 60349, Signer-Name: kimsserver.dk


	• Status: Good - Algorithmus 13 and DNSKEY with KeyTag 60349 used to validate the DNSKEY RRSet


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


	RRSIG Type 1 validates the A - Result: 87.57.145.116 Validated: RRSIG-Owner kimsserver.dk., Algorithm: 13, 2 Labels, original TTL: 43200 sec, Signature-expiration: 17.07.2025, 00:00:00 +, Signature-Inception: 26.06.2025, 00:00:00 +, KeyTag 58901, Signer-Name: kimsserver.dk


	CNAME-Query sends a valid NSEC3 RR as result with the hashed query name "itu7k6tan7e8tr0cvvj83ccoahce3936" equal the hashed NSEC3-owner "itu7k6tan7e8tr0cvvj83ccoahce3936" and the hashed NextOwner "itu7k6tan7e8tr0cvvj83ccoahce3937". So the zone confirmes the not-existence of that CNAME RR, but the existence of that query name (minimal one RR with that name exists). Bitmap: A, NS, SOA, MX, RRSIG, DNSKEY, NSEC3PARAM Validated: RRSIG-Owner itu7k6tan7e8tr0cvvj83ccoahce3936.kimsserver.dk., Algorithm: 13, 3 Labels, original TTL: 600 sec, Signature-expiration: 17.07.2025, 00:00:00 +, Signature-Inception: 26.06.2025, 00:00:00 +, KeyTag 58901, Signer-Name: kimsserver.dk


	Status: Good. NoData-Proof required and found.


	TXT-Query sends a valid NSEC3 RR as result with the hashed query name "itu7k6tan7e8tr0cvvj83ccoahce3936" equal the hashed NSEC3-owner "itu7k6tan7e8tr0cvvj83ccoahce3936" and the hashed NextOwner "itu7k6tan7e8tr0cvvj83ccoahce3937". So the zone confirmes the not-existence of that TXT RR, but the existence of that query name (minimal one RR with that name exists). Bitmap: A, NS, SOA, MX, RRSIG, DNSKEY, NSEC3PARAM Validated: RRSIG-Owner itu7k6tan7e8tr0cvvj83ccoahce3936.kimsserver.dk., Algorithm: 13, 3 Labels, original TTL: 600 sec, Signature-expiration: 17.07.2025, 00:00:00 +, Signature-Inception: 26.06.2025, 00:00:00 +, KeyTag 58901, Signer-Name: kimsserver.dk


	Status: Good. NoData-Proof required and found.


	AAAA-Query sends a valid NSEC3 RR as result with the hashed query name "itu7k6tan7e8tr0cvvj83ccoahce3936" equal the hashed NSEC3-owner "itu7k6tan7e8tr0cvvj83ccoahce3936" and the hashed NextOwner "itu7k6tan7e8tr0cvvj83ccoahce3937". So the zone confirmes the not-existence of that AAAA RR, but the existence of that query name (minimal one RR with that name exists). Bitmap: A, NS, SOA, MX, RRSIG, DNSKEY, NSEC3PARAM Validated: RRSIG-Owner itu7k6tan7e8tr0cvvj83ccoahce3936.kimsserver.dk., Algorithm: 13, 3 Labels, original TTL: 600 sec, Signature-expiration: 17.07.2025, 00:00:00 +, Signature-Inception: 26.06.2025, 00:00:00 +, KeyTag 58901, Signer-Name: kimsserver.dk


	Status: Good. NoData-Proof required and found.


	TLSA-Query (_443._tcp.kimsserver.dk) sends a valid NSEC3 RR as result with the hashed query name "qc1ska8hhvik4s0ikg6h9s3alrfv0pel" equal the hashed NSEC3-owner "qc1ska8hhvik4s0ikg6h9s3alrfv0pel" and the hashed NextOwner "qc1ska8hhvik4s0ikg6h9s3alrfv0pem". So the zone confirmes the not-existence of that TLSA RR, but the existence of that query name (minimal one RR with that name exists). Bitmap: A, RRSIG Validated: RRSIG-Owner qc1ska8hhvik4s0ikg6h9s3alrfv0pel.kimsserver.dk., Algorithm: 13, 3 Labels, original TTL: 600 sec, Signature-expiration: 17.07.2025, 00:00:00 +, Signature-Inception: 26.06.2025, 00:00:00 +, KeyTag 58901, Signer-Name: kimsserver.dk


	Status: Good. NoData-Proof required and found.


	CAA-Query sends a valid NSEC3 RR as result with the hashed query name "itu7k6tan7e8tr0cvvj83ccoahce3936" equal the hashed NSEC3-owner "itu7k6tan7e8tr0cvvj83ccoahce3936" and the hashed NextOwner "itu7k6tan7e8tr0cvvj83ccoahce3937". So the zone confirmes the not-existence of that CAA RR, but the existence of that query name (minimal one RR with that name exists). Bitmap: A, NS, SOA, MX, RRSIG, DNSKEY, NSEC3PARAM Validated: RRSIG-Owner itu7k6tan7e8tr0cvvj83ccoahce3936.kimsserver.dk., Algorithm: 13, 3 Labels, original TTL: 600 sec, Signature-expiration: 17.07.2025, 00:00:00 +, Signature-Inception: 26.06.2025, 00:00:00 +, KeyTag 58901, Signer-Name: kimsserver.dk


	Status: Good. NoData-Proof required and found.

Zone: www.kimsserver.dk
www.kimsserver.dk	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 "tucg98o7mn44u3p8fss7b918kkr826l9" between the hashed NSEC3-owner "tucg98o7mn44u3p8fss7b918kkr826l9" and the hashed NextOwner "tucg98o7mn44u3p8fss7b918kkr826la". So the parent zone confirmes the not-existence of a DS RR. Bitmap: A, RRSIG Validated: RRSIG-Owner tucg98o7mn44u3p8fss7b918kkr826l9.kimsserver.dk., Algorithm: 13, 3 Labels, original TTL: 600 sec, Signature-expiration: 17.07.2025, 00:00:00 +, Signature-Inception: 26.06.2025, 00:00:00 +, KeyTag 58901, Signer-Name: kimsserver.dk


	RRSIG Type 1 validates the A - Result: 87.57.145.116 Validated: RRSIG-Owner www.kimsserver.dk., Algorithm: 13, 3 Labels, original TTL: 43200 sec, Signature-expiration: 17.07.2025, 00:00:00 +, Signature-Inception: 26.06.2025, 00:00:00 +, KeyTag 58901, Signer-Name: kimsserver.dk


	CNAME-Query sends a valid NSEC3 RR as result with the hashed query name "tucg98o7mn44u3p8fss7b918kkr826l9" equal the hashed NSEC3-owner "tucg98o7mn44u3p8fss7b918kkr826l9" and the hashed NextOwner "tucg98o7mn44u3p8fss7b918kkr826la". So the zone confirmes the not-existence of that CNAME RR, but the existence of that query name (minimal one RR with that name exists). Bitmap: A, RRSIG Validated: RRSIG-Owner tucg98o7mn44u3p8fss7b918kkr826l9.kimsserver.dk., Algorithm: 13, 3 Labels, original TTL: 600 sec, Signature-expiration: 17.07.2025, 00:00:00 +, Signature-Inception: 26.06.2025, 00:00:00 +, KeyTag 58901, Signer-Name: kimsserver.dk


	Status: Good. NoData-Proof required and found.


	TXT-Query sends a valid NSEC3 RR as result with the hashed query name "tucg98o7mn44u3p8fss7b918kkr826l9" equal the hashed NSEC3-owner "tucg98o7mn44u3p8fss7b918kkr826l9" and the hashed NextOwner "tucg98o7mn44u3p8fss7b918kkr826la". So the zone confirmes the not-existence of that TXT RR, but the existence of that query name (minimal one RR with that name exists). Bitmap: A, RRSIG Validated: RRSIG-Owner tucg98o7mn44u3p8fss7b918kkr826l9.kimsserver.dk., Algorithm: 13, 3 Labels, original TTL: 600 sec, Signature-expiration: 17.07.2025, 00:00:00 +, Signature-Inception: 26.06.2025, 00:00:00 +, KeyTag 58901, Signer-Name: kimsserver.dk


	Status: Good. NoData-Proof required and found.


	AAAA-Query sends a valid NSEC3 RR as result with the hashed query name "tucg98o7mn44u3p8fss7b918kkr826l9" equal the hashed NSEC3-owner "tucg98o7mn44u3p8fss7b918kkr826l9" and the hashed NextOwner "tucg98o7mn44u3p8fss7b918kkr826la". So the zone confirmes the not-existence of that AAAA RR, but the existence of that query name (minimal one RR with that name exists). Bitmap: A, RRSIG Validated: RRSIG-Owner tucg98o7mn44u3p8fss7b918kkr826l9.kimsserver.dk., Algorithm: 13, 3 Labels, original TTL: 600 sec, Signature-expiration: 17.07.2025, 00:00:00 +, Signature-Inception: 26.06.2025, 00:00:00 +, KeyTag 58901, Signer-Name: kimsserver.dk


	Status: Good. NoData-Proof required and found.


	TLSA-Query (_443._tcp.www.kimsserver.dk) sends a valid NSEC3 RR as result with the hashed query name "sop3r4udnis5itr19c1ulmcbmacqis73" equal the hashed NSEC3-owner "sop3r4udnis5itr19c1ulmcbmacqis73" and the hashed NextOwner "sop3r4udnis5itr19c1ulmcbmacqis74". So the zone confirmes the not-existence of that TLSA RR, but the existence of that query name (minimal one RR with that name exists). Bitmap: A, RRSIG Validated: RRSIG-Owner sop3r4udnis5itr19c1ulmcbmacqis73.kimsserver.dk., Algorithm: 13, 3 Labels, original TTL: 600 sec, Signature-expiration: 17.07.2025, 00:00:00 +, Signature-Inception: 26.06.2025, 00:00:00 +, KeyTag 58901, Signer-Name: kimsserver.dk


	Status: Good. NoData-Proof required and found.


	CAA-Query sends a valid NSEC3 RR as result with the hashed query name "tucg98o7mn44u3p8fss7b918kkr826l9" equal the hashed NSEC3-owner "tucg98o7mn44u3p8fss7b918kkr826l9" and the hashed NextOwner "tucg98o7mn44u3p8fss7b918kkr826la". So the zone confirmes the not-existence of that CAA RR, but the existence of that query name (minimal one RR with that name exists). Bitmap: A, RRSIG Validated: RRSIG-Owner tucg98o7mn44u3p8fss7b918kkr826l9.kimsserver.dk., Algorithm: 13, 3 Labels, original TTL: 600 sec, Signature-expiration: 17.07.2025, 00:00:00 +, Signature-Inception: 26.06.2025, 00:00:00 +, KeyTag 58901, Signer-Name: kimsserver.dk


	Status: Good. NoData-Proof required and found.

3. Name Servers

Domain	Nameserver	NS-IP
www.kimsserver.dk	• ns01.one.com / ns3.cst.dnspod1-fra1.g1i.one		•
kimsserver.dk	• ns01.one.com / ns2.cst.dnspod1-fra1.g1i.one	195.206.121.10 Copenhagen/Capital Region/Denmark (DK) - One.com A/S	•
	•	2001:67c:28cc::10 Copenhagen/Capital Region/Denmark (DK) - One.com A/S	•
	• ns02.one.com	185.10.11.10 Copenhagen/Capital Region/Denmark (DK) - One.com A/S	•
	•	2001:67c:3c0::10 Copenhagen/Capital Region/Denmark (DK) - One.com A/S	•
dk	• b.nic.dk		•
	• c.nic.dk / FRA1		•
	• h.nic.dk		•
	• l.nic.dk / nic-l2.prod.dkhm.dk		•
	• s.nic.dk / eqx-fr-ns02-65225		•
	• t.nic.dk / dns-sgix-01.nic.cz		•

4. SOA-Entries

Domain:	dk
Zone-Name:	dk
Primary:	b.nic.dk
Mail:	tech.dk-hostmaster.dk
Serial:	1751786461
Refresh:	600
Retry:	300
Expire:	1814400
TTL:	300
num Entries:	6

Domain:	kimsserver.dk
Zone-Name:	kimsserver.dk
Primary:	ns01.one.com
Mail:	hostmaster.one.com
Serial:	2025051601
Refresh:	14400
Retry:	3600
Expire:	1209600
TTL:	600
num Entries:	4

Domain:	www.kimsserver.dk
Zone-Name:	kimsserver.dk
Primary:	ns01.one.com
Mail:	hostmaster.one.com
Serial:	2025051601
Refresh:	14400
Retry:	3600
Expire:	1209600
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

show header:

Domainname	Http-Status	redirect	Sec.	G
• http://kimsserver.dk:8443/ 87.57.145.116	302	http://kimsserver.dk/dashboard/	0.087	D
Date: Sun, 06 Jul 2025 07:25:01 GMT
Server: Apache/2.4.56,(Unix),OpenSSL/1.1.1t,PHP/8.2.4,mod_perl/2.0.12,Perl/v5.34.1
X-Powered-By: PHP/8.2.4
Location: http://kimsserver.dk/dashboard/
Content-Length: 0
Content-Type: text/html; charset=UTF-8

• http://www.kimsserver.dk:8443/ 87.57.145.116	302	http://www.kimsserver.dk/dashboard/	0.054	D
Date: Sun, 06 Jul 2025 07:25:01 GMT
Server: Apache/2.4.56,(Unix),OpenSSL/1.1.1t,PHP/8.2.4,mod_perl/2.0.12,Perl/v5.34.1
X-Powered-By: PHP/8.2.4
Location: http://www.kimsserver.dk/dashboard/
Content-Length: 0
Content-Type: text/html; charset=UTF-8

• http://kimsserver.dk/dashboard/	404	Html is minified: 103.70 %	0.083	M
Not Found
Date: Sun, 06 Jul 2025 07:25:03 GMT
Server: Apache/2.4.54,(Unix),OpenSSL/1.0.2u,PHP/8.1.13,mod_wsgi/3.5,Python/2.7.18,mod_fastcgi/mod_fastcgi-SNAP-0910052141,mod_perl/2.0.11,Perl/v5.30.1
Content-Length: 196
Content-Type: text/html; charset=iso-8859-1

• http://www.kimsserver.dk/dashboard/	404	Html is minified: 103.70 %	0.083	M
Not Found
Date: Sun, 06 Jul 2025 07:25:03 GMT
Server: Apache/2.4.54,(Unix),OpenSSL/1.0.2u,PHP/8.1.13,mod_wsgi/3.5,Python/2.7.18,mod_fastcgi/mod_fastcgi-SNAP-0910052141,mod_perl/2.0.11,Perl/v5.30.1
Content-Length: 196
Content-Type: text/html; charset=iso-8859-1

• https://kimsserver.dk:8443/ 87.57.145.116	-103		0.100	P
SecureConnectionError (3, 0x80131501). The SSL connection could not be established, see inner exception. Cannot determine the frame size or a corrupted frame was received

• https://www.kimsserver.dk:8443/ 87.57.145.116	-103		0.100	P
SecureConnectionError (3, 0x80131501). The SSL connection could not be established, see inner exception. Cannot determine the frame size or a corrupted frame was received

• http://kimsserver.dk:8443/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 87.57.145.116 Inline-JavaScript (∑/total): 0/0 Inline-CSS (∑/total): 0/0	404	Html is minified: 136.75 % Other inline scripts (∑/total): 0/0	0.053	A
Not Found
Visible Content:
Date: Sun, 06 Jul 2025 07:25:01 GMT
Server: Apache/2.4.56,(Unix),OpenSSL/1.1.1t,PHP/8.2.4,mod_perl/2.0.12,Perl/v5.34.1
Vary: accept-language,accept-charset
Accept-Ranges: bytes
Transfer-Encoding: chunked
Content-Type: text/html; charset=utf-8
Content-Language: en
Content-Length: 1027

• http://www.kimsserver.dk:8443/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 87.57.145.116 Inline-JavaScript (∑/total): 0/0 Inline-CSS (∑/total): 0/0	404	Html is minified: 136.56 % Other inline scripts (∑/total): 0/0	0.040	A
Not Found
Visible Content:
Date: Sun, 06 Jul 2025 07:25:02 GMT
Server: Apache/2.4.56,(Unix),OpenSSL/1.1.1t,PHP/8.2.4,mod_perl/2.0.12,Perl/v5.34.1
Vary: accept-language,accept-charset
Accept-Ranges: bytes
Transfer-Encoding: chunked
Content-Type: text/html; charset=utf-8
Content-Language: en
Content-Length: 1031

• https://87.57.145.116:8443/ 87.57.145.116	-103		0.100	P
SecureConnectionError (3, 0x80131501). The SSL connection could not be established, see inner exception. Cannot determine the frame size or a corrupted frame was received

7. Comments

	1. General Results, most used to calculate the result
A	name "kimsserver.dk" is domain, public suffix is ".dk", top-level-domain is ".dk", top-level-domain-type is "country-code", Country is Denmark, tld-manager is "Dansk Internet Forum", num .dk-domains preloaded: 981 (complete: 271405)
A	Good: All ip addresses are public addresses
	Warning: Only one ip address found: kimsserver.dk has only one ip address.
	Warning: Only one ip address found: www.kimsserver.dk 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: kimsserver.dk has no ipv6 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.kimsserver.dk has no ipv6 address.
A	Good: No asked Authoritative Name Server had a timeout
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: All urls with http status 200/404 have a complete Content-Type header (MediaType / MediaSubType + correct charset)
C	Error - no version with Http-Status 200
D	http://kimsserver.dk:8443/ 87.57.145.116	302	http://kimsserver.dk/dashboard/	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.
D	http://www.kimsserver.dk:8443/ 87.57.145.116	302	http://www.kimsserver.dk/dashboard/	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.
H	Fatal error: No https - result with http-status 200, no encryption
M	http://kimsserver.dk/dashboard/	404		Misconfiguration - main pages should never send http status 400 - 499
M	http://www.kimsserver.dk/dashboard/	404		Misconfiguration - main pages should never send http status 400 - 499
	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 kimsserver.dk, 1 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.kimsserver.dk, 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.kimsserver.dk
	2. Header-Checks
U				No https result with http status 2 or 4 (standard-check) found, no header checked.
	3. DNS- and NameServer - Checks
A	Info:: 9 Root-climbing DNS Queries required to find all IPv4- and IPv6-Addresses of 2 Name Servers.
A	Info:: 9 Queries complete, 9 with IPv6, 0 with IPv4.
A	Good: All DNS Queries done via IPv6.
	Ok (4 - 8):: An average of 4.5 queries per domain name server required to find all ip addresses of all name servers.
A	Info:: 2 different Name Servers found: ns01.one.com, ns02.one.com, 2 Name Servers included in Delegation: ns01.one.com, ns02.one.com, 2 Name Servers included in 1 Zone definitions: ns01.one.com, ns02.one.com, 1 Name Servers listed in SOA.Primary: ns01.one.com.
A	Good: Only one SOA.Primary Name Server found.: ns01.one.com.
A	Good: SOA.Primary Name Server included in the delegation set.: ns01.one.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: ns01.one.com, ns02.one.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: 2 different Name Servers found
A	Good: 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: one.com
	Warning: All Name Servers from the same Country / IP location.: 2 Name Servers, 1 Countries: DK
A	Info: Ipv4-Subnet-list: 2 Name Servers, 2 different subnets (first Byte): 185., 195., 2 different subnets (first two Bytes): 185.10., 195.206., 2 different subnets (first three Bytes): 185.10.11., 195.206.121.
A	Excellent: Every Name Server IPv4-address starts with an unique Byte.
A	Info: IPv6-Subnet-list: 2 Name Servers with IPv6, 1 different subnets (first block): 2001:, 1 different subnets (first two blocks): 2001:067c:, 2 different subnets (first three blocks): 2001:067c:03c0:, 2001:067c:28cc:, 2 different subnets (first four blocks): 2001:067c:03c0:0000:, 2001:067c:28cc:0000:
A	Good: Name Server IPv6 addresses from different subnets 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
	Nameserver doesn't pass all EDNS-Checks: ns01.one.com: OP100: ok. FLAGS: ok. V1: ok. V1OP100: ok. V1FLAGS: ok. DNSSEC: ok. V1DNSSEC: ok. NSID: ok (ns3.cst.dnspod1-fra1.g1i.one). COOKIE: ok. CLIENTSUBNET: fatal timeout.
	Nameserver doesn't pass all EDNS-Checks: ns01.one.com / 195.206.121.10: OP100: ok. FLAGS: ok. V1: ok. V1OP100: ok. V1FLAGS: ok. DNSSEC: fatal timeout. V1DNSSEC: ok. NSID: ok (ns2.cst.dnspod1-fra1.g1i.one). COOKIE: ok. CLIENTSUBNET: ok.
	Nameserver doesn't pass all EDNS-Checks: ns01.one.com / 2001:67c:28cc::10: OP100: ok. FLAGS: ok. V1: ok. V1OP100: ok. V1FLAGS: ok. DNSSEC: ok. V1DNSSEC: ok. NSID: ok (ns2.cst.dnspod1-fra1.g1i.one). COOKIE: fatal timeout. CLIENTSUBNET: ok.
	Nameserver doesn't pass all EDNS-Checks: ns02.one.com / 185.10.11.10: OP100: ok. FLAGS: ok. V1: ok. V1OP100: ok. V1FLAGS: ok. DNSSEC: ok. V1DNSSEC: ok. NSID: fatal timeout. COOKIE: ok. CLIENTSUBNET: ok.
	Nameserver doesn't pass all EDNS-Checks: ns02.one.com / 2001:67c:3c0::10: OP100: ok. FLAGS: ok. V1: ok. V1OP100: ok. V1FLAGS: ok. DNSSEC: ok. V1DNSSEC: ok. NSID: ok (ns3.cst.dnspod1-fra1.g1i.one). COOKIE: fatal timeout. CLIENTSUBNET: ok.
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
A	Good: All checks /.well-known/acme-challenge/random-filename without redirects answer with the expected http status 404 - Not Found. Creating a Letsencrypt certificate via http-01 challenge should work. If it doesn't work: Check your vHost configuration (apachectl -S, httpd -S, nginx -T). Every combination of port and ServerName / ServerAlias (Apache) or Server (Nginx) must be unique. Merge duplicated entries in one vHost. If you use an IIS, extensionless files must be allowed in the /.well-known/acme-challenge subdirectory. Create a web.config in that directory. Content: <configuration><system.webServer><staticContent><mimeMap fileExtension="." mimeType="text/plain" /></staticContent></system.webServer></configuration>. If you have a redirect http ⇒ https, that's ok, Letsencrypt follows such redirects to port 80 / 443 (same or other server). There must be a certificate. But the certificate may be expired, self signed or with a not matching domain name. Checking the validation file Letsencrypt ignores such certificate errors. Trouble creating a certificate? Use https://community.letsencrypt.org/ to ask.
A	Good: All checked attribute values are enclosed in quotation marks (" or ').
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	Info: Different Server-Headers found
A	Duration: 58516 milliseconds, 58.516 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)

Issuer				last 7 days	active	num Certs
CN=E6, O=Let's Encrypt, C=US				0	1	1
CN=E5, O=Let's Encrypt, C=US				0	1	1

CertSpotter-Id	Issuer	not before	not after	Domain names	LE-Duplicate	next LE
10917174534 leaf cert	CN=E6, O=Let's Encrypt, C=US	2025-06-28 07:37:59	2025-09-26 07:37:58	kimsserver.dk, www.kimsserver.dk - 2 entries
10669322511 leaf cert	CN=E5, O=Let's Encrypt, C=US	2025-06-06 22:04:10	2025-09-04 22:04:09	kimsserver.dk, www.kimsserver.dk - 2 entries

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

Issuer				last 7 days	active	num Certs
CN=E5, O=Let's Encrypt, C=US				0	1	2
CN=E6, O=Let's Encrypt, C=US				0	1	1

CRT-Id	Issuer	not before	not after	Domain names	LE-Duplicate	next LE
19306125385 leaf cert	CN=E6, O=Let's Encrypt, C=US	2025-06-28 05:37:59	2025-09-26 05:37:58	kimsserver.dk, www.kimsserver.dk 2 entries
18858659748 precert	CN=E5, O=Let's Encrypt, C=US	2025-06-06 20:04:10	2025-09-04 20:04:09	kimsserver.dk, www.kimsserver.dk 2 entries
17403698529 precert	CN=E5, O=Let's Encrypt, C=US	2025-03-25 20:29:34	2025-06-23 19:29:33	kimsserver.dk, www.kimsserver.dk 2 entries

11. Html-Content - Entries

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

12. Html-Parsing via https://validator.w3.org/nu/

No https result http status 200 and Content-Type text/html or text/xml found, no Html-Parsing - Check

13. Nameserver - IP-Adresses

Required Root-climbing DNS-Queries to find ip addresses of all Name Servers: ns01.one.com, ns02.one.com

QNr.	Domain	Type	NS used
1	com	NS	a.root-servers.net (2001:503:ba3e::2:30)
	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	ns01.one.com	NS	a.gtld-servers.net (2001:503:a83e::2:30)
	Answer: auth.g1-dns.com, auth.g1-dns.one
	Answer: auth.g1-dns.com 195.206.121.11, 2001:67c:28cc::11
3	ns02.one.com	NS	a.gtld-servers.net (2001:503:a83e::2:30)
	Answer: auth.g1-dns.com, auth.g1-dns.one
	Answer: auth.g1-dns.com 195.206.121.11, 2001:67c:28cc::11
4	one	NS	b.root-servers.net (2001:500:200::b)
	Answer: a.nic.one, b.nic.one, c.nic.one, x.nic.one, y.nic.one, z.nic.one
5	auth.g1-dns.one: 185.10.11.11, 2001:67c:3c0::11	NS	a.nic.one (2001:dcd:1::9)
6	ns01.one.com: 195.206.121.10	A	auth.g1-dns.com (2001:67c:28cc::11)
7	ns01.one.com: 2001:67c:28cc::10	AAAA	auth.g1-dns.com (2001:67c:28cc::11)
8	ns02.one.com: 185.10.11.10	A	auth.g1-dns.com (2001:67c:28cc::11)
9	ns02.one.com: 2001:67c:3c0::10	AAAA	auth.g1-dns.com (2001:67c:28cc::11)

14. CAA - Entries

Domainname	Value	∑ Queries
www.kimsserver.dk	no CAA entry found	1
kimsserver.dk	no CAA entry found	1
dk	no CAA entry found	1

15. TXT - Entries

Domainname	Status	∑ Queries
kimsserver.dk	ok	1
www.kimsserver.dk	ok	1
_acme-challenge.kimsserver.dk	missing entry or wrong length	1
_acme-challenge.www.kimsserver.dk	missing entry or wrong length	1
_acme-challenge.kimsserver.dk.kimsserver.dk	perhaps wrong	1
_acme-challenge.www.kimsserver.dk.kimsserver.dk	perhaps wrong	1
_acme-challenge.www.kimsserver.dk.www.kimsserver.dk	perhaps wrong	1

16. DomainService - Entries

Type		Domain	Pref	Value	num Answers	Status
MX		kimsserver.dk	10	mx3.pub.mailpod11-cph3.one.com	4	ok
	A			104.37.34.232	1	ok
	CNAME				0	ok
MX		kimsserver.dk	10	mx4.pub.mailpod11-cph3.one.com	4	ok
	A			104.37.34.233	1	ok
	CNAME				0	ok
MX		kimsserver.dk	10	mx1.pub.mailpod11-cph3.one.com	4	ok
	A			104.37.34.230	1	ok
	CNAME				0	ok
MX		kimsserver.dk	10	mx2.pub.mailpod11-cph3.one.com	4	ok
	A			104.37.34.231	1	ok
	CNAME				0	ok

17. Cipher Suites

No results

18. Portchecks

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

Permalink: https://check-your-website.server-daten.de/?i=5819d031-a583-4627-8016-948e6b1068dd

Last Result: https://check-your-website.server-daten.de/?q=kimsserver.dk%3A8443 - 2025-07-06 09:24:14

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

<a href="https://check-your-website.server-daten.de/?q=kimsserver.dk%3A8443" target="_blank">Check this Site: kimsserver.dk%3A8443</a>

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

QR-Code of this page - https://check-your-website.server-daten.de/?d=kimsserver.dk:8443