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

...

skip EDNS-Check

skip Content-Check

check links

Top config

Checked:
19.01.2019 11:53:19

Older results

No older results found

1. IP-Addresses

Host	Type	IP-Address	is auth.	∑ Queries	∑ Timeout
home.hardlands.de	CNAME	hardlands.dscloud.me	yes	1	0
	A	79.206.216.101 Hostname: p4fced865.dip0.t-ipconnect.de	yes
hardlands.dscloud.me	AAAA		yes
www.home.hardlands.de		Name Error	yes	1	0

2. DNSSEC

Zone (*)	DNSSEC - Informations

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


	• Status: Valid because published


	3 DNSKEY RR found


	Public Key with Algorithm 8, KeyTag 16749, Flags 256


	Public Key with Algorithm 8, KeyTag 19164, Flags 385


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


	2 RRSIG RR to validate DNSKEY RR found


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


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


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


	• 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: de
de	1 DS RR in the parent zone found


	1 RRSIG RR to validate DS RR found


	RRSIG-Owner de., Algorithm: 8, 1 Labels, original TTL: 86400 sec, Signature-expiration: 01.02.2019, 05:00:00 +, Signature-Inception: 19.01.2019, 04:00:00 +, KeyTag 16749, Signer-Name: (root)


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


	2 DNSKEY RR found


	Public Key with Algorithm 8, KeyTag 9253, Flags 256


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


	1 RRSIG RR to validate DNSKEY RR found


	RRSIG-Owner de., Algorithm: 8, 1 Labels, original TTL: 7200 sec, Signature-expiration: 07.02.2019, 12:00:00 +, Signature-Inception: 17.01.2019, 12:00:00 +, KeyTag 39227, Signer-Name: de


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


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

Zone: hardlands.de
hardlands.de	0 DS RR in the parent zone found


	0 DNSKEY RR found




Zone: home.hardlands.de
home.hardlands.de	0 DS RR in the parent zone found

Zone: www.home.hardlands.de
www.home.hardlands.de	0 DS RR in the parent zone found

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


	• Status: Valid because published


	3 DNSKEY RR found


	Public Key with Algorithm 8, KeyTag 16749, Flags 256


	Public Key with Algorithm 8, KeyTag 19164, Flags 385


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


	2 RRSIG RR to validate DNSKEY RR found


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


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


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


	• 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: me
me	2 DS RR in the parent zone found


	1 RRSIG RR to validate DS RR found


	RRSIG-Owner me., Algorithm: 8, 1 Labels, original TTL: 86400 sec, Signature-expiration: 01.02.2019, 05:00:00 +, Signature-Inception: 19.01.2019, 04:00:00 +, KeyTag 16749, Signer-Name: (root)


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


	4 DNSKEY RR found


	Public Key with Algorithm 7, KeyTag 2569, Flags 257 (SEP = Secure Entry Point)


	Public Key with Algorithm 7, KeyTag 31700, Flags 256


	Public Key with Algorithm 7, KeyTag 53233, Flags 257 (SEP = Secure Entry Point)


	Public Key with Algorithm 7, KeyTag 59048, Flags 256


	3 RRSIG RR to validate DNSKEY RR found


	RRSIG-Owner me., Algorithm: 7, 1 Labels, original TTL: 900 sec, Signature-expiration: 07.02.2019, 15:19:38 +, Signature-Inception: 17.01.2019, 14:19:38 +, KeyTag 2569, Signer-Name: me


	RRSIG-Owner me., Algorithm: 7, 1 Labels, original TTL: 900 sec, Signature-expiration: 07.02.2019, 15:19:38 +, Signature-Inception: 17.01.2019, 14:19:38 +, KeyTag 53233, Signer-Name: me


	RRSIG-Owner me., Algorithm: 7, 1 Labels, original TTL: 900 sec, Signature-expiration: 07.02.2019, 15:19:38 +, Signature-Inception: 17.01.2019, 14:19:38 +, KeyTag 59048, Signer-Name: me


	• Status: Good - Algorithmus 7 and DNSKEY with KeyTag 2569 used to validate the DNSKEY RRSet


	• Status: Good - Algorithmus 7 and DNSKEY with KeyTag 53233 used to validate the DNSKEY RRSet


	• Status: Good - Algorithmus 7 and DNSKEY with KeyTag 59048 used to validate the DNSKEY RRSet


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


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

Zone: dscloud.me
dscloud.me	0 DS RR in the parent zone found


	0 DNSKEY RR found




Zone: hardlands.dscloud.me
hardlands.dscloud.me	0 DS RR in the parent zone found


	0 DNSKEY RR found

3. Name Servers

Domain	Nameserver	NS-IP
www.home.hardlands.de	• ns.namespace4you.de
hardlands.de	• ns.namespace4you.de
	• ns2.namespace4you.de
de	• a.nic.de
	• f.nic.de
	• l.de.net
	• n.de.net
	• s.de.net
	• z.nic.de

hardlands.dscloud.me	• ddns-ns1.quickconnect.to
dscloud.me	• ddns-ns1.quickconnect.to
	• ddns-ns2.quickconnect.to
me	• a0.nic.me
	• a2.nic.me
	• b0.nic.me
	• b2.nic.me
	• c0.nic.me

4. SOA-Entries

No SOA informations found. The feature is new (startet 2019-02-05), so recheck this domain.

5. Screenshots

No Screenshot listed, because no screenshot found. Perhaps the check is too old, the feature startet 2019-12-23.

6. Url-Checks

show header:

Domainname	Http-Status	redirect	Sec.	G
• http://home.hardlands.de/ 79.206.216.101	301	https://home.hardlands.de/	0.064	A
Server: nginx
Date: Sat, 19 Jan 2019 10:53:31 GMT
Content-Type: text/html
Content-Length: 178
Connection: close
Location: https://home.hardlands.de/

• https://home.hardlands.de/ 79.206.216.101	200		2.787	A
Server: nginx
Date: Sat, 19 Jan 2019 10:53:33 GMT
Content-Type: text/html; charset="UTF-8"
Transfer-Encoding: chunked
Connection: close
Cache-control: no-store
X-Content-Type-Options: nosniff
X-XSS-Protection: 1; mode=block
X-Frame-Options: SAMEORIGIN
P3P: CP="IDC DSP COR ADM DEVi TAIi PSA PSD IVAi IVDi CONi HIS OUR IND CNT"
Content-Security-Policy: base-uri 'self'; connect-src ws: wss: ; default-src 'self' 'unsafe-eval' data: blob: https://.synology.com https://www.synology.cn/; font-src 'self' data: https://.googleapis.com https://.gstatic.com https://fonts.gstatic.com https://.gstatic.com; form-action 'self'; frame-ancestors 'self' https://gofile.me http://gofile.me; frame-src 'self' data: blob: https://.synology.com https://www.synology.cn/ https://www.youtube.com http://www.youtube.com http://.synology.com http://.synology.cn; img-src 'self' data: blob: https://.google.com https://.googleapis.com http://.googlecode.com https://.gstatic.com https://.gstatic.com https://.googleapis.com https://.google.com https://.gstatic.com https://.googleapis.com https://.google.com http://.baidu.com https://.bdstatic.com; media-src 'self' data: about:; report-uri webman/csp_report.cgi; script-src 'self' 'unsafe-eval' data: blob: https://.synology.com https://www.synology.cn/ https://.google.com https://.googleapis.com https://.google.com https://.googleapis.com https://.google.com https://.googleapis.com https://.baidu.com https://.bdstatic.com; style-src 'self' 'unsafe-inline' https://.googleapis.com https://.googleapis.com https://.googleapis.com https://api.map.baidu.com;
Strict-Transport-Security: max-age=15768000; includeSubdomains; preload

• http://home.hardlands.de/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 79.206.216.101	404		0.086	A
Not Found
Visible Content:
Server: nginx
Date: Sat, 19 Jan 2019 10:53:34 GMT
Content-Type: text/html
Content-Length: 162
Connection: close

7. Comments

	1. General Results, most used to calculate the result
A	name "home.hardlands.de" is subdomain, public suffix is "de", top-level-domain-type is "country-code", Country is Germany, tld-manager is "DENIC eG"
A	Good: All ip addresses are public addresses
A	Good: No asked Authoritative Name Server had a timeout
A	DNS: "Name Error" means: No www-dns-entry defined. This isn't a problem
A	Good: destination is https
A	Good - only one version with Http-Status 200
A	Good: one preferred version: non-www is preferred
A	Good: every https has a Strict Transport Security Header
A	Good: HSTS has includeSubdomains - directive
A	Good: HSTS has preload directive
	Warning: HSTS preload sent, but not in Preload-List. Never send a preload directive if you don't know what preload means. Check https://hstspreload.org/ to learn the basics about the Google-Preload list. If you send a preload directive, you should immediately add your domain to the HSTS preload list via https://hstspreload.org/ . If Google accepts the domain, so the status is "pending": Note that new entries are hardcoded into the Chrome source code and can take several months before they reach the stable version. So you will see this message some months. If you don't want that or if you don't understand "preload", but if you send a preload directive and if you have correct A-redirects, everybody can add your domain to that list. Then you may have problems, it's not easy to undo that. So if you don't want your domain preloaded, remove the preload directive.
A	Good: Some urls with http status 200/404 have a complete Content-Type header (MediaType / MediaSubType + correct charset):1 complete Content-Type - header (2 urls)
	http://home.hardlands.de/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 79.206.216.101			Url with incomplete Content-Type - header - missing charset
A	http://home.hardlands.de/ 79.206.216.101	301	https://home.hardlands.de/	Correct redirect http - https with the same domain name
B	Warning: HSTS max-age is too short - minimum 31536000 = 365 days required, 15768000 seconds = 182 days found
	2. Header-Checks (Cross-Origin-* headers are alpha - started 2024-06-05)
	3. DNS- and NameServer - Checks
A	Good: Nameserver supports TCP connections: 2 good Nameserver
A	Good: Nameserver supports Echo Capitalization: 2 good Nameserver
A	Good: Nameserver supports EDNS with max. 512 Byte Udp payload, message is smaller: 2 good Nameserver
	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: 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: 14903 milliseconds, 14.903 seconds

8. Connections

Domain

Port

Cert.

Protocol

KeyExchange

Strength

Cipher

Strength

HashAlgorithm

OCSP stapling

Domain/KeyExchange

IP/Strength

Port/Cipher

Cert./Strength

Protocol/HashAlgorithm

OCSP stapling

home.hardlands.de

79.206.216.101

443

Tls12

DiffieHellman

2048

Aes128

128

Sha256

not supported

home.hardlands.de

79.206.216.101

443

Tls12

DiffieHellman

2048

Aes128

128

Sha256

not supported

no Tls.1.2
no Tls.1.1
no Tls.1.0

9. Certificates

CN=home.hardlands.de

28.12.2018

28.03.2019
2078 days expired

home.hardlands.de - 1 entry

CN=home.hardlands.de

28.12.2018

28.03.2019
2078 days expired

home.hardlands.de - 1 entry

Keyalgorithm	RSA encryption (2048 bit)
Signatur:	SHA256 With RSA-Encryption
Serial Number:	04269BD2E8AE0E18147FEA46DBDC5D610EF6
Thumbprint:	E5C891A7F7A15E72D1F2C7782D7165B9415F192B
SHA256 / Certificate:	Xl9zPbcJ9JWgQtq37V/OEhhEADKxwVWmswZJz6mHBSA=
SHA256 hex / Cert (DANE * 0 1):	5e5f733db709f495a042dab7ed5fce1218440032b1c155a6b30649cfa9870520
SHA256 hex / PublicKey (DANE * 1 1):	e7ea94cecb1affc5e9e2e2488f4ad6e3809fce2b979585fa6ca181a094114a20
SHA256 hex / Subject Public Key Information (SPKI):	e7ea94cecb1affc5e9e2e2488f4ad6e3809fce2b979585fa6ca181a094114a20
SPKI checked via https://v1.pwnedkeys.com/spki-hash:	Good: Key isn't compromised
OCSP - Url:	http://ocsp.int-x3.letsencrypt.org
OCSP - must staple:	no
Certificate Transparency:	yes
Enhanced Key Usage:	Server Authentication (1.3.6.1.5.5.7.3.1), Client Authentication (1.3.6.1.5.5.7.3.2)

CN=Let's Encrypt Authority X3, O=Let's Encrypt, C=US

17.03.2016

17.03.2021
1358 days expired

CN=Let's Encrypt Authority X3, O=Let's Encrypt, C=US

17.03.2016

17.03.2021
1358 days expired

Keyalgorithm	RSA encryption (2048 bit)
Signatur:	SHA256 With RSA-Encryption
Serial Number:	0A0141420000015385736A0B85ECA708
Thumbprint:	E6A3B45B062D509B3382282D196EFE97D5956CCB
SHA256 / Certificate:	JYR9Zo608E/dQLErawdAxWfafQJDCOtsLJb+QdneIY0=
SHA256 hex / Cert (DANE * 0 1):	25847d668eb4f04fdd40b12b6b0740c567da7d024308eb6c2c96fe41d9de218d
SHA256 hex / PublicKey (DANE * 1 1):	60b87575447dcba2a36b7d11ac09fb24a9db406fee12d2cc90180517616e8a18
SHA256 hex / Subject Public Key Information (SPKI):	60b87575447dcba2a36b7d11ac09fb24a9db406fee12d2cc90180517616e8a18
SPKI checked via https://v1.pwnedkeys.com/spki-hash:	Good: Key isn't compromised
OCSP - Url:	http://isrg.trustid.ocsp.identrust.com
OCSP - must staple:	no
Certificate Transparency:	no
Enhanced Key Usage:

CN=DST Root CA X3, O=Digital Signature Trust Co.

30.09.2000

30.09.2021
1161 days expired

CN=DST Root CA X3, O=Digital Signature Trust Co.

30.09.2000

30.09.2021
1161 days expired

Keyalgorithm	RSA encryption (2048 bit)
Signatur:	SHA-1 with RSA Encryption
Serial Number:	44AFB080D6A327BA893039862EF8406B
Thumbprint:	DAC9024F54D8F6DF94935FB1732638CA6AD77C13
SHA256 / Certificate:	BocmAzGnJAPZCfEF5pvPDTLhvSST/8bZIG0RvNZ3Bzk=
SHA256 hex / Cert (DANE * 0 1):	0687260331a72403d909f105e69bcf0d32e1bd2493ffc6d9206d11bcd6770739
SHA256 hex / PublicKey (DANE * 1 1):	563b3caf8cfef34c2335caf560a7a95906e8488462eb75ac59784830df9e5b2b
SHA256 hex / Subject Public Key Information (SPKI):	563b3caf8cfef34c2335caf560a7a95906e8488462eb75ac59784830df9e5b2b
SPKI checked via https://v1.pwnedkeys.com/spki-hash:	Good: Key isn't compromised
OCSP - Url:
OCSP - must staple:	no
Certificate Transparency:	no
Enhanced Key Usage:

10. Last Certificates - Certificate Transparency Log Check

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

No CertSpotter - Certificate-Transparency-Log informations found. The feature is new (startet 2019-05-07), so recheck this domain.

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

No Certificate-Transparency-Log informations found. The feature is new (startet 2019-03-21), so recheck this domain.

11. Html-Content - Entries

No Html-Content informations found. The feature is new (startet 2019-01-22), so recheck this domain.

12. Html-Parsing via https://validator.nu/ / https://validator.w3.org/nu/ (started 2024-09-28, 09:00, alpha)

Unfortunately, there are differences between the first used validator.nu and validator.w3.org/nu/ - switched to validator.w3.org/nu/. Looks like some error messages (link - fetchpriority attribute) of validator.nu are obsolete, not seen in the w3.org-version and not found in the current specification: link may have a fetchpriority attribute.

Small Code update, wait one minute

13. Nameserver - IP-Adresses

Required Root-climbing DNS-Queries to find ip addresses of all Name Servers:

No NameServer - IP address informations found. The feature is new (2020-05-07), so recheck this domain.

14. CAA - Entries

Domainname	flag	Value	∑ Queries
hardlands.dscloud.me	0	no CAA entry found	1
home.hardlands.de			1
hardlands.de	0	no CAA entry found	1
dscloud.me	0	no CAA entry found	1
de	0	no CAA entry found	1
me	0	no CAA entry found	1

15. TXT - Entries

Domainname	Status	∑ Queries
home.hardlands.de		1
hardlands.dscloud.me	ok	1
_acme-challenge.home.hardlands.de	Name Error - The domain name does not exist	1
_acme-challenge.hardlands.dscloud.me	missing entry or wrong length	1
_acme-challenge.home.hardlands.de.home.hardlands.de	Name Error - The domain name does not exist	1
_acme-challenge.hardlands.dscloud.me.hardlands.dscloud.me	perhaps wrong	1

16. DomainService - Entries

No DomainServiceEntries entries found

17. Cipher Suites

No Ciphers found

18. Portchecks

No Port informations found. The feature is new (startet 2019-07-09), so recheck this domain.

Permalink: https://check-your-website.server-daten.de/?i=459c41c9-ba3e-4e5b-8176-c0fc8aa6f430

Last Result: https://check-your-website.server-daten.de/?q=home.hardlands.de - 2019-01-19 11:53:19

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

<a href="https://check-your-website.server-daten.de/?q=home.hardlands.de" target="_blank">Check this Site: home.hardlands.de</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=home.hardlands.de