With millions of websites in search engines we can never be sure that the sites we are visiting are not harmful.  Some search engines like Google helps us detect websites that can cause harm to out computer.  Some search engines do not have this feature which makes us vulnerable to to exploit attacks especially for those that are webmasters.  We must always make sure that we have computer protection such as anti spyware or even the basic antivirus software which can be downloaded for free on the internet such as avast and avira.

Just like the website virus I found on some of our sites a new one existed and was not even noticed by the webmaster of the site I recently modified.  There was a script injected along the php files, as seen on the images.  I never knew how the virus got into the site, what I saw when I opened the site’s files via FTP is that there are encrypted codes along the normal pages.  I had the pages scanned and found out that the encrypted codes is a virus.  I removed the lines on the php files and in a short while it was back again.  There I found out that there are 3 files that generates the virus, 1 is the index.php which has the iframe tag as seen on the image, 2nd was the file ncoyrl.htm which has the encrypted javascript codes and lastly a gif image named zcv.gif which also plays a role.

After I deleted the files the website no longer throws a threat warning coming from an antivirus.  We must always make sure that in an online business, security is an issue.  Let a programmer or anybody that is techie enough to check free scripts downloaded online.

The line break and the paragraph and tags are easy to omit, both in writing regular HTML and in PHP and ASP code to produce HTML. The browsers generally ignore what is referred to as white space. Therefore, if you want the text to go to a new line, you must include explicitly a tag to force that to happen. Similarly, white space along a line, such as this will be ignored. A special character, written as will force a space. The table tags often are used to lay out text and images on the screen, not just for things like tables of numbers. Later, you will work on examples in which each record from a database will generate a row of a table, including images, buttons, and hyperlinks. HTML has other tags! You can learn about them by using the View Source option in the browsers and by looking at references. You also can investigate Cascading Style Sheets (CSS), an addition to HTML for more elaborate formatting. The tags described here are the basics that you will use in your PHP and ASP scripting. Another description of the process is the following: You, the person using the client computer, invoke a browser such as the latest version of Netscape. You enter in a location on the Web in the form of a URL. The browser sends a request for that particular file to the server computer, the computer described by the URL. As part of the process of interpreting the file, the browser might request other files, such as all the image files mentioned in the src attribute of img tags. If the document had any hyperlinks, coded using tags, then if and when you click on one, the process repeats. However, this time, the browser sends a request for the particular file indicated by the href attribute of the tag. An important feature of how browsers work is, to put it in anthropomorphic terms, they do not complain. That is, if your HTML file has errors, such as incorrectly formatted tags, missing ending tags, improper nesting or mis-spelling of filenames, the browser will display something and give no indication of the existence or the location of errors. You will need to check out the display to see if it is what you intended. This is different from working in programming languages such as C++ or Java when minor syntactic errors in notation prevent you from proceeding beyond compilation, many errors are detected during runtime, and special functions are provided for debugging, getting the errors out of your application. If you have had such experiences, you will come to miss them when working with HTML. Read on for suggestions on how to debug HTML.

Declare a DOCTYPE. The DOCTYPE goes before the opening html tag at the top of the page and tells the browser whether the page contains HTML, XHTML, or a mix of both, so that it can correctly interpret the markup. There are three main DOCTYPEs that let the browser know what kind of markup it is dealing with:

Strict:

All markup is XHTML-compliant.

“http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd”>

Transitional:

This states that the markup is a mix of XHTML and deprecated HTML. Many well-established sites are currently using this one, so their old HTML code can exist happily in the document alongside the XHTML they are now adding.

Transitional//EN” “http://www.w3.org/TR/html4/loose.dtd”>

Frameset:

This is the same as transitional but in this case frames, which are deprecated under XHTML, are OK, too.

<!DOCTYPE HTML PUBLIC “-//W3C//DTD HTML 4.01 Frameset//EN” “http://www.w3.org/TR/html4/frameset.dtd”>

It is important to specify a DOCTYPE. Browsers that don’t see a DOCTYPE in the markup assume that the site page was coded for browsers developed long before Web standards. My recommendation is that if you are building a site from scratch, and can therefore avoid deprecated or abandoned tag attributes, such as FONT and COLOR, use the XHTML Strict DOCTYPE listed previously.
When encountering a page without a DOCTYPE, many browsers go into what is known as Quirks mode, a backwards-compatibility feature supported by Mozilla, Internet Explorer 6 for Windows, and Internet Explorer 5 for Macintosh.
In Quirks mode, the browser functions as if it has no knowledge of the modern DOM (document object model) and pretends it has never heard of Web standards. This ability to switch modes depending on the DOCTYPE, or lack thereof, enables browsers to do the best possible job of interpreting the code of both standards- compliant and noncompliant sites.
Note that for some weird reason, the DOCTYPE tag does not need to be closed with a slash and DOCTYPE is always in caps.