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




X

DNS-problem - authoritative Nameserver refused, not defined or timeout

Checked:
11.07.2019 09:55:54


Older results

No older results found


1. IP-Addresses

HostTIP-Addressis auth.∑ Queries∑ Timeout
tumer.poweredbyclear.com
A
213.74.25.66
Kartal/Istanbul/Turkey (TR) - Tellcom Iletisim Hizmetleri A.S.
Hostname: host-213-74-25-66.superonline.net
yes
1
0

AAAA

yes


www.tumer.poweredbyclear.com
A
213.74.25.66
Kartal/Istanbul/Turkey (TR) - Tellcom Iletisim Hizmetleri A.S.
Hostname: host-213-74-25-66.superonline.net
yes
1
0

AAAA

yes



2. DNSSEC

Zone (*)DNSSEC - Informations (beta)

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



Status: Valid because published



3 DNSKEY RR found



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



Public Key with Algorithm 8, KeyTag 25266, Flags 256



Public Key with Algorithm 8, KeyTag 59944, Flags 256



1 RRSIG RR to validate DNSKEY RR found



Algorithm: 8, 0 Labels, original TTL: 172800 sec, Signature-expiration: 22.07.2019, 00:00:00, Signature-Inception: 01.07.2019, 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: com
com
1 DS RR in the parent zone found



1 RRSIG RR to validate DS RR found



Algorithm: 8, 1 Labels, original TTL: 86400 sec, Signature-expiration: 23.07.2019, 21:00:00, Signature-Inception: 10.07.2019, 20:00:00, KeyTag 59944, Signer-Name: (root)



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



3 DNSKEY RR found



Public Key with Algorithm 8, KeyTag 3800, Flags 256



Public Key with Algorithm 8, KeyTag 17708, Flags 256



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



1 RRSIG RR to validate DNSKEY RR found



Algorithm: 8, 1 Labels, original TTL: 86400 sec, Signature-expiration: 16.07.2019, 18:25:33, Signature-Inception: 01.07.2019, 18:20:33, KeyTag 30909, Signer-Name: com



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



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

Zone: poweredbyclear.com
poweredbyclear.com
0 DS RR in the parent zone found



DS-Query in the parent zone has a valid NSEC3 RR as result with the hashed domain name between the hashed NSEC3-owner and the hashed NextOwner. So the parent zone confirmes the non-existence of a DS RR.



0 DNSKEY RR found





Zone: tumer.poweredbyclear.com
tumer.poweredbyclear.com
0 DS RR in the parent zone found



0 DNSKEY RR found





Zone: www.tumer.poweredbyclear.com
www.tumer.poweredbyclear.com
0 DS RR in the parent zone found


3. Name Servers

DomainNameserverNS-IP
www.tumer.poweredbyclear.com
U  ns1.clearsdn.com

tumer.poweredbyclear.com
U  ns1.clearsdn.com
35.159.5.1
Frankfurt am Main/Hesse/Germany (DE) - Amazon Technologies Inc.

poweredbyclear.com
U  ns1.clearsdn.com


U  ns2.clearsdn.com


U  ns3.clearsdn.com


  ns4.clearsdn.com

com
  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


4. SOA-Entries


Domain:com
Primary:a.gtld-servers.net
Mail:nstld.verisign-grs.com
Serial:1562831728
Refresh:1800
Retry:900
Expire:604800
TTL:86400
num Entries:3


Domain:com
Primary:a.gtld-servers.net
Mail:nstld.verisign-grs.com
Serial:1562831743
Refresh:1800
Retry:900
Expire:604800
TTL:86400
num Entries:10


Domain:poweredbyclear.com
Primary:ns1.clearsdn.com
Mail:hostmaster.clearsdn.com
Serial:2019071103
Refresh:10000
Retry:3600
Expire:1048576
TTL:2560
num Entries:4


Domain:tumer.poweredbyclear.com
Primary:ns1.clearsdn.com
Mail:hostmaster.clearsdn.com
Serial:2019071103
Refresh:10000
Retry:3600
Expire:1048576
TTL:2560
num Entries:1


Domain:www.tumer.poweredbyclear.com
Primary:ns1.clearsdn.com
Mail:hostmaster.clearsdn.com
Serial:2019071103
Refresh:10000
Retry:3600
Expire:1048576
TTL:2560
num Entries:1


5. Url-Checks


:

:
Domainname Http-StatusredirectSec.G
• http://tumer.poweredbyclear.com/
213.74.25.66
302
http://tumer.poweredbyclear.com/login.aspx?default=pl&ht=Id&cont=http://tumer.poweredbyclear.com/default.aspx
0.217
D
Cache-Control: private
Content-Type: text/html; charset=iso-8859-9
Location: login.aspx?default=pl&ht=Id&cont=http://tumer.poweredbyclear.com/default.aspx
Set-Cookie: ASP.NET_SessionId=ygha11k1b4n1quqcmwm3xcjt; Path=/; Domain=tumer.poweredbyclear.com; HttpOnly
p3p: CP="IDC DSP COR ADM DEVi TAIi PSA PSD IVAi IVDi CONi HIS OUR IND CNT"
Strict-Transport-Security: max-age=16070400; includeSubDomains
X-Frame-Options: SAMEORIGIN
X-XSS-Protection: 1; mode=block
X-Content-Type-Options: nosniff
Referrer-Policy: no-referrer
X-Permitted-Cross-Domain-Policies: none
X-Powered-By: ASP.NET
Date: Thu, 11 Jul 2019 07:58:35 GMT
Connection: close
Content-Length: 8457

• http://www.tumer.poweredbyclear.com/
213.74.25.66
302
http://www.tumer.poweredbyclear.com/login.aspx?default=pl&ht=Id&cont=http://www.tumer.poweredbyclear.com/default.aspx
0.234
D
Cache-Control: private
Content-Type: text/html; charset=iso-8859-9
Location: login.aspx?default=pl&ht=Id&cont=http://www.tumer.poweredbyclear.com/default.aspx
Set-Cookie: ASP.NET_SessionId=igoaiclbbpynutjmuh2pmttv; Path=/; Domain=www.tumer.poweredbyclear.com; HttpOnly
p3p: CP="IDC DSP COR ADM DEVi TAIi PSA PSD IVAi IVDi CONi HIS OUR IND CNT"
Strict-Transport-Security: max-age=16070400; includeSubDomains
X-Frame-Options: SAMEORIGIN
X-XSS-Protection: 1; mode=block
X-Content-Type-Options: nosniff
Referrer-Policy: no-referrer
X-Permitted-Cross-Domain-Policies: none
X-Powered-By: ASP.NET
Date: Thu, 11 Jul 2019 07:58:35 GMT
Connection: close
Content-Length: 8461

• http://tumer.poweredbyclear.com/login.aspx?default=pl&ht=Id&cont=http://tumer.poweredbyclear.com/default.aspx

200

0.264
H
Cache-Control: private
Content-Type: text/html; charset=iso-8859-9
Set-Cookie: ASP.NET_SessionId=s2plqqwtalflce31x333jdlx; Path=/; Domain=tumer.poweredbyclear.com; HttpOnly,adaSessionId=aa263418999246a5a75e277688f6685a; Path=/; Domain=tumer.poweredbyclear.com; HttpOnly
p3p: CP="IDC DSP COR ADM DEVi TAIi PSA PSD IVAi IVDi CONi HIS OUR IND CNT"
Strict-Transport-Security: max-age=16070400; includeSubDomains
X-Frame-Options: SAMEORIGIN
X-XSS-Protection: 1; mode=block
X-Content-Type-Options: nosniff
Referrer-Policy: no-referrer
X-Permitted-Cross-Domain-Policies: none
X-Powered-By: ASP.NET
Date: Thu, 11 Jul 2019 07:58:37 GMT
Connection: close
Content-Length: 6872

• http://www.tumer.poweredbyclear.com/login.aspx?default=pl&ht=Id&cont=http://www.tumer.poweredbyclear.com/default.aspx

200

0.234
H
Cache-Control: private
Content-Type: text/html; charset=iso-8859-9
Set-Cookie: ASP.NET_SessionId=ikse32aocrjwa0g3cwx1ob5y; Path=/; Domain=www.tumer.poweredbyclear.com; HttpOnly,adaSessionId=4f25da9e2c344213a893d2b14f6ea099; Path=/; Domain=www.tumer.poweredbyclear.com; HttpOnly
p3p: CP="IDC DSP COR ADM DEVi TAIi PSA PSD IVAi IVDi CONi HIS OUR IND CNT"
Strict-Transport-Security: max-age=16070400; includeSubDomains
X-Frame-Options: SAMEORIGIN
X-XSS-Protection: 1; mode=block
X-Content-Type-Options: nosniff
Referrer-Policy: no-referrer
X-Permitted-Cross-Domain-Policies: none
X-Powered-By: ASP.NET
Date: Thu, 11 Jul 2019 07:58:37 GMT
Connection: close
Content-Length: 6940

• https://tumer.poweredbyclear.com/
213.74.25.66
200

0.783
N
Certificate error: RemoteCertificateNameMismatch, RemoteCertificateChainErrors
Date: Thu, 11 Jul 2019 07:58:00 GMT
Server: Apache/2.4.6 (CentOS) OpenSSL/1.0.2k-fips
Last-Modified: Mon, 29 Apr 2019 20:09:41 GMT
ETag: "2634-587b0dd56cb40"
Accept-Ranges: bytes
Content-Length: 9780
Connection: close
Content-Type: text/html; charset=UTF-8

• https://www.tumer.poweredbyclear.com/
213.74.25.66
200

0.797
N
Certificate error: RemoteCertificateNameMismatch, RemoteCertificateChainErrors
Date: Thu, 11 Jul 2019 07:58:01 GMT
Server: Apache/2.4.6 (CentOS) OpenSSL/1.0.2k-fips
Last-Modified: Mon, 29 Apr 2019 20:09:41 GMT
ETag: "2634-587b0dd56cb40"
Accept-Ranges: bytes
Content-Length: 9780
Connection: close
Content-Type: text/html; charset=UTF-8

• http://tumer.poweredbyclear.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
213.74.25.66
404

0.157
A
Not Found
Visible Content:
Cache-Control: no-cache, no-store, must-revalidate
Content-Type: text/html
Strict-Transport-Security: max-age=16070400; includeSubDomains
X-Frame-Options: SAMEORIGIN
X-XSS-Protection: 1; mode=block
X-Content-Type-Options: nosniff
Referrer-Policy: no-referrer
X-Permitted-Cross-Domain-Policies: none
X-Powered-By: ASP.NET
Date: Thu, 11 Jul 2019 07:58:37 GMT
Connection: close
Content-Length: 1221

• http://www.tumer.poweredbyclear.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
213.74.25.66
404

0.144
A
Not Found
Visible Content:
Cache-Control: no-cache, no-store, must-revalidate
Content-Type: text/html
Strict-Transport-Security: max-age=16070400; includeSubDomains
X-Frame-Options: SAMEORIGIN
X-XSS-Protection: 1; mode=block
X-Content-Type-Options: nosniff
Referrer-Policy: no-referrer
X-Permitted-Cross-Domain-Policies: none
X-Powered-By: ASP.NET
Date: Thu, 11 Jul 2019 07:58:37 GMT
Connection: close
Content-Length: 1221

6. Comments (GZip / Html minfied / Cache-Control is beta)

Aname "tumer.poweredbyclear.com" is subdomain, public suffix is "com", top-level-domain-type is "generic", tld-manager is "VeriSign Global Registry Services"
Agood: All ip addresses are public addresses
AGood: Some urls with http status 200/404 have a complete Content-Type header (MediaType / MediaSubType + correct charset):4 complete Content-Type - header (6 urls)
http://tumer.poweredbyclear.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 213.74.25.66


Url with incomplete Content-Type - header - missing charset
http://www.tumer.poweredbyclear.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 213.74.25.66


Url with incomplete Content-Type - header - missing charset
Bhttps://tumer.poweredbyclear.com/ 213.74.25.66
200

Missing HSTS-Header
Bhttps://www.tumer.poweredbyclear.com/ 213.74.25.66
200

Missing HSTS-Header
CError - more then one version with Http-Status 200. After all redirects, all users (and search engines) should see the same https url: Non-www or www, but not both with http status 200.
CError - no preferred version www or non-www. Select one version as preferred version, then add a redirect https + not-preferred version to https + preferred version. Perhaps in your port 443 vHost something like "RewriteEngine on" + "RewriteCond %{SERVER_NAME} = example.com" + "ReWriteRule ^ https://www.example.com%{REQUEST_URI} [END,QSA,R=permanent]" (three rows, without the "). That should create a redirect https + example.com ⇒ https + www.example.com. Or switch both values to use the non-www version as your preferred version.
Dhttp://tumer.poweredbyclear.com/ 213.74.25.66
302
http://tumer.poweredbyclear.com/login.aspx?default=pl&ht=Id&cont=http://tumer.poweredbyclear.com/default.aspx
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.tumer.poweredbyclear.com/ 213.74.25.66
302
http://www.tumer.poweredbyclear.com/login.aspx?default=pl&ht=Id&cont=http://www.tumer.poweredbyclear.com/default.aspx
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: http result with http-status 200, no encryption. Add a redirect http ⇒ https, so every connection is secure. 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.
Nhttps://tumer.poweredbyclear.com/ 213.74.25.66
200

Error - Certificate isn't trusted, RemoteCertificateNameMismatch, RemoteCertificateChainErrors
Nhttps://www.tumer.poweredbyclear.com/ 213.74.25.66
200

Error - Certificate isn't trusted, RemoteCertificateNameMismatch, RemoteCertificateChainErrors
OOld connection: SHA1 as Hash Algorithm is deprecated. Switch to SHA256 or SHA384. If your certificate has SHA256, first check your domain via ssllabs.com and update weak Cipher Suites. Forward Secrecy support is required. The part "Cipher Suites" should have a preference. First Cipher Suite with SHA instead of SHA256 or higher - that's the problem, change that. If that doesn't help, check if there is an old Firewall / router or something else, that supports only SHA1. Update that component.
XFatal error: Nameserver isn't defined or has timeout
XFatal error: Nameserver doesn't support TCP connection: ns1.clearsdn.com: Fatal error - no NameServer IP-Address or connection. Details: One or more errors occurred. - No connection could be made because the target machine actively refused it 35.159.5.1:53
XFatal error: Nameserver doesn't support TCP connection: ns1.clearsdn.com / 35.159.5.1: Fatal error - no NameServer IP-Address or connection. Details: One or more errors occurred. - No connection could be made because the target machine actively refused it 35.159.5.1:53
XFatal error: Nameserver doesn't support TCP connection: ns2.clearsdn.com: Fatal error - no NameServer IP-Address or connection. Details: One or more errors occurred. - No connection could be made because the target machine actively refused it 23.21.90.219:53
XFatal error: Nameserver doesn't support TCP connection: ns3.clearsdn.com: Fatal error - no NameServer IP-Address or connection. Details: One or more errors occurred. - No connection could be made because the target machine actively refused it 34.217.162.48:53
AGood: Nameserver supports Echo Capitalization: 1 good Nameserver
XFatal error: Nameserver doesn't support EDNS with max. 512 Byte Udp payload or sends more then 512 Bytes: ns1.clearsdn.com
XFatal error: Nameserver doesn't support EDNS with max. 512 Byte Udp payload or sends more then 512 Bytes: ns2.clearsdn.com
XFatal error: Nameserver doesn't support EDNS with max. 512 Byte Udp payload or sends more then 512 Bytes: ns3.clearsdn.com
XFatal error: Nameserver doesn't support EDNS with max. 512 Byte Udp payload or sends more then 512 Bytes: ns4.clearsdn.com
Nameserver doesn't pass all EDNS-Checks: ns1.clearsdn.com: OP100: no result. FLAGS: no result. V1: no result. V1OP100: no result. V1FLAGS: no result. DNSSEC: no result. V1DNSSEC: no result. NSID: no result. COOKIE: no result. CLIENTSUBNET: no result.
Nameserver doesn't pass all EDNS-Checks: ns1.clearsdn.com: OP100: no result. FLAGS: no result. V1: no result. V1OP100: no result. V1FLAGS: no result. DNSSEC: no result. V1DNSSEC: no result. NSID: no result. COOKIE: no result. CLIENTSUBNET: no result.
Nameserver doesn't pass all EDNS-Checks: ns1.clearsdn.com / 35.159.5.1: OP100: no result. FLAGS: no result. V1: no result. V1OP100: no result. V1FLAGS: no result. DNSSEC: no result. V1DNSSEC: no result. NSID: no result. COOKIE: no result. CLIENTSUBNET: no result.
Nameserver doesn't pass all EDNS-Checks: ns2.clearsdn.com: OP100: no result. FLAGS: no result. V1: no result. V1OP100: no result. V1FLAGS: no result. DNSSEC: no result. V1DNSSEC: no result. NSID: no result. COOKIE: no result. CLIENTSUBNET: no result.
Nameserver doesn't pass all EDNS-Checks: ns3.clearsdn.com: OP100: no result. FLAGS: no result. V1: no result. V1OP100: no result. V1FLAGS: no result. DNSSEC: no result. V1DNSSEC: no result. NSID: no result. COOKIE: no result. CLIENTSUBNET: no result.
Nameserver doesn't pass all EDNS-Checks: ns4.clearsdn.com: OP100: no result. FLAGS: no result. V1: no result. V1OP100: no result. V1FLAGS: no result. DNSSEC: no result. V1DNSSEC: no result. NSID: no result. COOKIE: no result. CLIENTSUBNET: no result.
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.
AGood: 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.
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
http://tumer.poweredbyclear.com/ 213.74.25.66
302

Warning: HSTS header sent via http has no effect
http://tumer.poweredbyclear.com/login.aspx?default=pl&ht=Id&cont=http://tumer.poweredbyclear.com/default.aspx
200

Warning: HSTS header sent via http has no effect
http://www.tumer.poweredbyclear.com/ 213.74.25.66
302

Warning: HSTS header sent via http has no effect
http://www.tumer.poweredbyclear.com/login.aspx?default=pl&ht=Id&cont=http://www.tumer.poweredbyclear.com/default.aspx
200

Warning: HSTS header sent via http has no effect
ADuration: 137643 milliseconds, 137.643 seconds


7. Connections (http/2 - check is BETA)

DomainIPPortCert.ProtocolKeyExchangeStrengthCipherStrengthHashAlgorithmOCSP stapling
Domain/KeyExchangeIP/StrengthPort/CipherCert./StrengthProtocol/HashAlgorithmOCSP stapling
tumer.poweredbyclear.com
213.74.25.66
443
Certificate/chain invalid and wrong name
Tls12
ECDH Ephermal
384
Aes256
256
Sha1
error checking OCSP stapling
weak
tumer.poweredbyclear.com
213.74.25.66
443
Certificate/chain invalid and wrong name
Tls12

ECDH Ephermal
384
Aes256
256
Sha1
error checking OCSP stapling
weak
Self signed certificate
1CN=localhost.localdomain, OU=SomeOrganizationalUnit, O=SomeOrganization, L=SomeCity, C=--, emailAddress=root@localhost.localdomain
www.tumer.poweredbyclear.com
213.74.25.66
443
Certificate/chain invalid and wrong name
Tls12
ECDH Ephermal
384
Aes256
256
Sha1
error checking OCSP stapling
weak
www.tumer.poweredbyclear.com
213.74.25.66
443
Certificate/chain invalid and wrong name
Tls12

ECDH Ephermal
384
Aes256
256
Sha1
error checking OCSP stapling
weak
Self signed certificate
1CN=localhost.localdomain, OU=SomeOrganizationalUnit, O=SomeOrganization, L=SomeCity, C=--, emailAddress=root@localhost.localdomain


8. Certificates

1.
1.
E=root@localhost.localdomain, CN=localhost.localdomain, OU=SomeOrganizationalUnit, O=SomeOrganization, L=SomeCity, S=SomeState, C=--
04.07.2019
03.07.2020
expires in 231 days

1.
1.
E=root@localhost.localdomain, CN=localhost.localdomain, OU=SomeOrganizationalUnit, O=SomeOrganization, L=SomeCity, S=SomeState, C=--
04.07.2019

03.07.2020
expires in 231 days


KeyalgorithmRSA encryption ( bit)
Signatur:SHA256 With RSA-Encryption
Serial Number:643A
Thumbprint:665BC40365A1E54CF52B5198C57A988BE8373537
SHA256 / Certificate:B4ZD3pGvo+26b31UTIFYMaaKfC+MwfoxmWEctbuqjJQ=
SHA256 hex / Cert (DANE * 0 1):e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855
SHA256 hex / PublicKey (DANE * 1 1):43c6ca9bbe0ea322e1740726825a76582356edc85fd4f9ed4037bd2948d1aaf5
OCSP - Url:
OCSP - must staple:no
Certificate Transparency:no

UntrustedRoot: A certificate chain processed, but terminated in a root certificate which is not trusted by the trust provider.


9. Last Certificates - Certificate Transparency Log Check

1. Source CertSpotter - active certificates

Issuerlast 7 daysactivenum Certs
CN=Let's Encrypt Authority X3, O=Let's Encrypt, C=US
0
0
1

CertSpotter-IdIssuernot beforenot afterDomain namesLE-Duplicatenext LE
1008497267
leaf cert
CN=Let's Encrypt Authority X3, O=Let's Encrypt, C=US
2019-07-09 17:13:30
2019-10-07 17:13:30
tumer.poweredbyclear.com - 1 entries



2. Source crt.sh - old and new certificates, sometimes very slow.

Issuerlast 7 daysactivenum Certs
CN=Let's Encrypt Authority X3, O=Let's Encrypt, C=US
0 /0 new
0
1

CRT-IdIssuernot beforenot afterDomain namesLE-Duplicatenext LE
1654902367
precert
CN=Let's Encrypt Authority X3, O=Let's Encrypt, C=US
2019-07-09 15:13:30
2019-10-07 15:13:30
tumer.poweredbyclear.com
1 entries



10. Html-Content - Entries

Summary

Subresource Integrity (SRI)
DomainnameHtmlElementrel/property∑ size∑ problems∑ int.∑ ext.∑ Origin poss.∑ SRI ParseErrors∑ SRI valid∑ SRI missing
https://tumer.poweredbyclear.com/
213.74.25.66
a

3

0







img

1
20,008 Bytes
0
1
0




https://www.tumer.poweredbyclear.com/
213.74.25.66
a

3

0







img

1
20,008 Bytes
0
1
0




Details (GZip part is BETA, may be wrong / incomplete)

DomainnameHtml-Elementname/equiv/ property/relhref/src/contentHttpStatusmsgStatus
https://tumer.poweredbyclear.com/
213.74.25.66
a

http://www.clearos.com/


1
ok








a

https://www.clearos.com/products/clearos-editions/clearos-7-business


1
ok








a

https://www.clearos.com/resources/documentation/clearos/content:en_us:7_ug_web_server


1
ok








img
src
logo.png
200
image/png

1
ok

No Cache-Control header






https://www.tumer.poweredbyclear.com/
213.74.25.66
a

http://www.clearos.com/


1
ok








a

https://www.clearos.com/products/clearos-editions/clearos-7-business


1
ok








a

https://www.clearos.com/resources/documentation/clearos/content:en_us:7_ug_web_server


1
ok








img
src
logo.png
200
image/png

1
ok

No Cache-Control header







11. CAA - Entries

DomainnameflagNameValue∑ Queries∑ Timeout
www.tumer.poweredbyclear.com
0

no CAA entry found
1
0
tumer.poweredbyclear.com
0

no CAA entry found
1
0
poweredbyclear.com
0

no CAA entry found
1
0
com
0

no CAA entry found
1
0


12. TXT - Entries

DomainnameTXT EntryStatus∑ Queries∑ Timeout
poweredbyclear.com

ok
1
0
tumer.poweredbyclear.com

ok
1
0
www.tumer.poweredbyclear.com

ok
1
0
_acme-challenge.tumer.poweredbyclear.com

missing entry or wrong length
1
0
_acme-challenge.www.tumer.poweredbyclear.com

missing entry or wrong length
1
0
_acme-challenge.tumer.poweredbyclear.com.poweredbyclear.com

perhaps wrong
1
0
_acme-challenge.tumer.poweredbyclear.com.tumer.poweredbyclear.com

perhaps wrong
1
0
_acme-challenge.www.tumer.poweredbyclear.com.tumer.poweredbyclear.com

perhaps wrong
1
0
_acme-challenge.www.tumer.poweredbyclear.com.www.tumer.poweredbyclear.com

perhaps wrong
1
0


13. Portchecks (BETA)

Domain or IPPortDescriptionResultAnswer
tumer.poweredbyclear.com
21




tumer.poweredbyclear.com
21




tumer.poweredbyclear.com
22

open


tumer.poweredbyclear.com
22

open


tumer.poweredbyclear.com
25




tumer.poweredbyclear.com
25




tumer.poweredbyclear.com
53




tumer.poweredbyclear.com
53




tumer.poweredbyclear.com
110




tumer.poweredbyclear.com
110




tumer.poweredbyclear.com
143




tumer.poweredbyclear.com
143




tumer.poweredbyclear.com
465




tumer.poweredbyclear.com
465




tumer.poweredbyclear.com
587




tumer.poweredbyclear.com
587




tumer.poweredbyclear.com
993




tumer.poweredbyclear.com
993




tumer.poweredbyclear.com
995




tumer.poweredbyclear.com
995




tumer.poweredbyclear.com
1433




tumer.poweredbyclear.com
1433




tumer.poweredbyclear.com
2082




tumer.poweredbyclear.com
2082




tumer.poweredbyclear.com
2083




tumer.poweredbyclear.com
2083




tumer.poweredbyclear.com
2086




tumer.poweredbyclear.com
2086




tumer.poweredbyclear.com
2087




tumer.poweredbyclear.com
2087




tumer.poweredbyclear.com
2089




tumer.poweredbyclear.com
2089




tumer.poweredbyclear.com
3306




tumer.poweredbyclear.com
3306




tumer.poweredbyclear.com
5224




tumer.poweredbyclear.com
5224




tumer.poweredbyclear.com
5432




tumer.poweredbyclear.com
5432




tumer.poweredbyclear.com
8443




tumer.poweredbyclear.com
8443




tumer.poweredbyclear.com
8447




tumer.poweredbyclear.com
8447




tumer.poweredbyclear.com
8880




tumer.poweredbyclear.com
8880




www.tumer.poweredbyclear.com
21




www.tumer.poweredbyclear.com
21




www.tumer.poweredbyclear.com
22

open


www.tumer.poweredbyclear.com
22

open


www.tumer.poweredbyclear.com
25




www.tumer.poweredbyclear.com
25




www.tumer.poweredbyclear.com
53




www.tumer.poweredbyclear.com
53




www.tumer.poweredbyclear.com
110




www.tumer.poweredbyclear.com
110




www.tumer.poweredbyclear.com
143




www.tumer.poweredbyclear.com
143




www.tumer.poweredbyclear.com
465




www.tumer.poweredbyclear.com
465




www.tumer.poweredbyclear.com
587




www.tumer.poweredbyclear.com
587




www.tumer.poweredbyclear.com
993




www.tumer.poweredbyclear.com
993




www.tumer.poweredbyclear.com
995




www.tumer.poweredbyclear.com
995




www.tumer.poweredbyclear.com
1433




www.tumer.poweredbyclear.com
1433




www.tumer.poweredbyclear.com
2082




www.tumer.poweredbyclear.com
2082




www.tumer.poweredbyclear.com
2083




www.tumer.poweredbyclear.com
2083




www.tumer.poweredbyclear.com
2086




www.tumer.poweredbyclear.com
2086




www.tumer.poweredbyclear.com
2087




www.tumer.poweredbyclear.com
2087




www.tumer.poweredbyclear.com
2089




www.tumer.poweredbyclear.com
2089




www.tumer.poweredbyclear.com
3306




www.tumer.poweredbyclear.com
3306




www.tumer.poweredbyclear.com
5224




www.tumer.poweredbyclear.com
5224




www.tumer.poweredbyclear.com
5432




www.tumer.poweredbyclear.com
5432




www.tumer.poweredbyclear.com
8443




www.tumer.poweredbyclear.com
8443




www.tumer.poweredbyclear.com
8447




www.tumer.poweredbyclear.com
8447




www.tumer.poweredbyclear.com
8880




www.tumer.poweredbyclear.com
8880




213.74.25.66
21




213.74.25.66
21




213.74.25.66
22

open


213.74.25.66
22

open


213.74.25.66
25




213.74.25.66
25




213.74.25.66
53




213.74.25.66
53




213.74.25.66
110




213.74.25.66
110




213.74.25.66
143




213.74.25.66
143




213.74.25.66
465




213.74.25.66
465




213.74.25.66
587




213.74.25.66
587




213.74.25.66
993




213.74.25.66
993




213.74.25.66
995




213.74.25.66
995




213.74.25.66
1433




213.74.25.66
1433




213.74.25.66
2082




213.74.25.66
2082




213.74.25.66
2083




213.74.25.66
2083




213.74.25.66
2086




213.74.25.66
2086




213.74.25.66
2087




213.74.25.66
2087




213.74.25.66
2089




213.74.25.66
2089




213.74.25.66
3306




213.74.25.66
3306




213.74.25.66
5224




213.74.25.66
5224




213.74.25.66
5432




213.74.25.66
5432




213.74.25.66
8443




213.74.25.66
8443




213.74.25.66
8447




213.74.25.66
8447




213.74.25.66
8880




213.74.25.66
8880






Permalink: https://check-your-website.server-daten.de/?i=19a639da-adea-4d9d-9329-7f375a95d22f


Last Result: https://check-your-website.server-daten.de/?q=tumer.poweredbyclear.com - 2019-07-11 09:55:54


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

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