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

...

skip EDNS-Check

skip Content-Check

check links

Top config

Checked:
18.01.2019 15:55:21

Older results

No older results found

1. IP-Addresses

Host	Type	IP-Address	is auth.	∑ Queries	∑ Timeout
femsamx.iotek.space			yes	4	0
www.femsamx.iotek.space			yes	4	0
femsamx.iotek.space	A	138.197.0.197 No Hostname found	no

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


	1 RRSIG RR to validate DS RR found


	RRSIG-Owner space., Algorithm: 8, 1 Labels, original TTL: 86400 sec, Signature-expiration: 31.01.2019, 05:00:00 +, Signature-Inception: 18.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


	0 DNSKEY RR found





	Fatal error: Parent zone has a signed DS RR (Algorithm 8, KeyTag 44251, DigestType 1, Digest Nqy2i3NN/kZcwREvnawIuLZmJ8w=), but the destination DNSKEY doesn't exist or doesn't validate the DNSKEY RR set. No chain of trust created.


	Fatal error: Parent zone has a signed DS RR (Algorithm 8, KeyTag 44251, DigestType 2, Digest qC2O0rB9ZtbnrzdeDkSyKoL0R5rUX12OGFnfb8Fw5nw=), but the destination DNSKEY doesn't exist or doesn't validate the DNSKEY RR set. No chain of trust created.

Zone: iotek.space
iotek.space	0 DS RR in the parent zone found

Zone: femsamx.iotek.space
femsamx.iotek.space	0 DS RR in the parent zone found

Zone: www.femsamx.iotek.space
www.femsamx.iotek.space	0 DS RR in the parent zone found

3. Name Servers

Domain	Nameserver	NS-IP
space	U a.nic.space
	U b.nic.space
	U c.nic.space
	U d.nic.space

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://femsamx.iotek.space/ 138.197.0.197	301	https://femsamx.iotek.space/	0.210	A
Server: nginx/1.10.3 (Ubuntu)
Date: Fri, 18 Jan 2019 14:55:34 GMT
Content-Type: text/html
Content-Length: 194
Connection: close
Location: https://femsamx.iotek.space/

• https://femsamx.iotek.space/ 138.197.0.197	200		2.430	A
Server: nginx/1.10.3 (Ubuntu)
Date: Fri, 18 Jan 2019 14:55:35 GMT
Content-Type: text/html;charset=UTF-8
Content-Length: 1430
Connection: close
Last-Modified: Fri, 07 Sep 2018 18:10:08 GMT
Accept-Ranges: bytes
X-Content-Type-Options: nosniff
X-XSS-Protection: 1; mode=block
Cache-Control: no-cache, no-store, max-age=0, must-revalidate
Pragma: no-cache
Expires: 0
Strict-Transport-Security: max-age=31536000 ; includeSubDomains
Content-Language: en-US

• http://femsamx.iotek.space/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 138.197.0.197	301	https://femsamx.iotek.space/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de	0.213	A
Visible Content:
Server: nginx/1.10.3 (Ubuntu)
Date: Fri, 18 Jan 2019 14:55:37 GMT
Content-Type: text/html
Content-Length: 194
Connection: close
Location: https://femsamx.iotek.space/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de

• https://femsamx.iotek.space/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de	404		2.003	A
Visible Content:
Server: nginx/1.10.3 (Ubuntu)
Date: Fri, 18 Jan 2019 14:55:37 GMT
Content-Type: application/json;charset=UTF-8
Transfer-Encoding: chunked
Connection: close
X-Content-Type-Options: nosniff
X-XSS-Protection: 1; mode=block
Cache-Control: no-cache, no-store, max-age=0, must-revalidate
Pragma: no-cache
Expires: 0
Strict-Transport-Security: max-age=31536000 ; includeSubDomains

7. Comments

	1. General Results, most used to calculate the result
A	name "femsamx.iotek.space" is subdomain, public suffix is "space", top-level-domain-type is "generic", tld-manager is "DotSpace Inc."
A	Good: All ip addresses are public addresses
A	Good: No asked Authoritative Name Server had a timeout
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 max-age is long enough, 31536000 seconds = 365 days
A	Good: HSTS has includeSubdomains - directive
A	Good: All urls with http status 200/404 have a complete Content-Type header (MediaType / MediaSubType + correct charset)
A	http://femsamx.iotek.space/ 138.197.0.197	301	https://femsamx.iotek.space/	Correct redirect http - https with the same domain name
X	Fatal error: Nameserver doesn't support TCP connection: b.nic.space: Fatal error - no NameServer IP-Address or connection
X	Fatal error: Nameserver doesn't support TCP connection: c.nic.space: Fatal error - no NameServer IP-Address or connection
X	Fatal error: Nameserver doesn't support TCP connection: d.nic.space: Fatal error - no NameServer IP-Address or connection
X	Fatal error: Nameserver doesn't support TCP connection: a.nic.space: Fatal error - no NameServer IP-Address or connection
	2. Header-Checks
	3. DNS- and NameServer - Checks
	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
	https://femsamx.iotek.space/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de	404	2.003 seconds	Warning: 404 needs more then one second
A	Duration: 17970 milliseconds, 17.970 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

femsamx.iotek.space

138.197.0.197

443

Tls12

DiffieHellman

2048

Aes128

128

Sha256

not supported

femsamx.iotek.space

138.197.0.197

443

Tls12

DiffieHellman

2048

Aes128

128

Sha256

not supported

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

9. Certificates

CN=femsamx.iotek.space

04.01.2019

04.04.2019
2079 days expired

femsamx.iotek.space - 1 entry

CN=femsamx.iotek.space

04.01.2019

04.04.2019
2079 days expired

femsamx.iotek.space - 1 entry

Keyalgorithm	RSA encryption (2048 bit)
Signatur:	SHA256 With RSA-Encryption
Serial Number:	03B1DC1D2DB56950C0853D5976446D64E109
Thumbprint:	00B1CC1A0FE1B485D1D5FA0DCC37D68D27EACDEB
SHA256 / Certificate:	xex2ZQDA0/+fqNBEwB46CJ2kP++f/F8E4lNeLgOiuW8=
SHA256 hex / Cert (DANE * 0 1):	c5ec766500c0d3ff9fa8d044c01e3a089da43fef9ffc5f04e2535e2e03a2b96f
SHA256 hex / PublicKey (DANE * 1 1):	ba38aa70d4dda620a9bd78c53b2ce6e0369db27638cf216ae890089e7d44ef09
SHA256 hex / Subject Public Key Information (SPKI):	ba38aa70d4dda620a9bd78c53b2ce6e0369db27638cf216ae890089e7d44ef09
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
1366 days expired

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

17.03.2016

17.03.2021
1366 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
1169 days expired

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

30.09.2000

30.09.2021
1169 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.w3.org/nu/

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	Name	Value	∑ Queries	∑ Timeout
space				4	0

15. TXT - Entries

No TXT entries found

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=30478c06-9a45-4d72-9c76-4dc823d11408

Last Result: https://check-your-website.server-daten.de/?q=femsamx.iotek.space - 2019-01-18 15:55:21

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

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