Here, we have selected some of best Ad Networks for Bloggers which are secure, trustworthy, and give you the best opportunity to monetize your blog or website. They serve millions of Ad impressions daily, have a large network of advertisers and publishers, and provide decent money to publishers.

10 Top Ad Networks for Publishers / Bloggers

1. Google Adsense

2. Propeller Ads

3. Adsterra Network

4. Revcontent

5. Infolinks

• Easy sign-up process.
• It allows you to generate more revenue from your blog
• You can easily integrate code to your blog
• Minimum payout is $50
• Multiple sources for getting payments such as PayPal
• New technology for getting more clicks
• It uses In3 Technology for increasing revenue of a blog or websites
• A large number of advertisers and publishers
• Mobile Ads Optimization for mobile traffic
• Superb Customer Support from their team

6. Media.net

7. RevenueHits

8. Clicksor

9. PopAds

• Advertiser’s Panel
• Publisher’s Panel
• Account Manager

10. Chitika

Contents

1. Introduction
2. Where to Begin? Internet Addresses
3. Protocol Stacks and Packets
4. Networking Infrastructure
5. Internet Infrastructure
6. The Internet Routing Hierarchy
7. Domain Names and Address Resolution
8. Internet Protocols Revisited
9. Application Protocols: HTTP and the World Wide Web
10. Application Protocols: SMTP and Electronic Mail
11. Transmission Control Protocol
12. Internet Protocol
13. Wrap Up
14. Resources
15. Bibliography

Introduction

Where to Begin? Internet Addresses

Diagram 1

Protocol Stacks and Packets

Diagram 2

1. The message would start at the top of the protocol stack on your computer and work it’s way downward.
2. If the message to be sent is long, each stack layer that the message passes through may break the message up into smaller chunks of data. This is because data sent over the Internet (and most computer networks) are sent in manageable chunks. On the Internet, these chunks of data are known as packets.
3. The packets would go through the Application Layer and continue to the TCP layer. Each packet is assigned a port number. Ports will be explained later, but suffice to say that many programs may be using the TCP/IP stack and sending messages. We need to know which program on the destination computer needs to receive the message because it will be listening on a specific port.
4. After going through the TCP layer, the packets proceed to the IP layer. This is where each packet receives it’s destination address, 5.6.7.8.
5. Now that our message packets have a port number and an IP address, they are ready to be sent over the Internet. The hardware layer takes care of turning our packets containing the alphabetic text of our message into electronic signals and transmitting them over the phone line.
6. On the other end of the phone line your ISP has a direct connection to the Internet. The ISPs routerexamines the destination address in each packet and determines where to send it. Often, the packet’s next stop is another router. More on routers and Internet infrastructure later.
7. Eventually, the packets reach computer 5.6.7.8. Here, the packets start at the bottom of the destination computer’s TCP/IP stack and work upwards.
8. As the packets go upwards through the stack, all routing data that the sending computer’s stack added (such as IP address and port number) is stripped from the packets.
9. When the data reaches the top of the stack, the packets have been re-assembled into their original form, “Hello computer 5.6.7.8!”

Networking Infrastructure

Diagram 3

Internet Infrastructure

Diagram 4

The Internet Routing Hierarchy

Diagram 5

Domain Names and Address Resolution

Diagram 6

Internet Protocols Revisited

Application Protocols: HTTP and the World Wide Web

1. If the URL contains a domain name, the browser first connects to a domain name server and retrieves the corresponding IP address for the web server.
2. The web browser connects to the web server and sends an HTTP request (via the protocol stack) for the desired web page.
3. The web server receives the request and checks for the desired page. If the page exists, the web server sends it. If the server cannot find the requested page, it will send an HTTP 404 error message. (404 means ‘Page Not Found’ as anyone who has surfed the web probably knows.)
4. The web browser receives the page back and the connection is closed.
5. The browser then parses through the page and looks for other page elements it needs to complete the web page. These usually include images, applets, etc.
6. For each element needed, the browser makes additional connections and HTTP requests to the server for each element.
7. When the browser has finished loading all images, applets, etc. the page will be completely loaded in the browser window.

Application Protocols: SMTP and Electronic Mail

1. The mail client (Netscape Mail, Lotus Notes, Microsoft Outlook, etc.) opens a connection to it’s default mail server. The mail server’s IP address or domain name is typically setup when the mail client is installed.
2. The mail server will always transmit the first message to identify itself.
3. The client will send an SMTP HELO command to which the server will respond with a 250 OK message.
4. Depending on whether the client is checking mail, sending mail, etc. the appropriate SMTP commands will be sent to the server, which will respond accordingly.
5. This request/response transaction will continue until the client sends an SMTP QUIT command. The server will then say goodbye and the connection will be closed.

      This SMTP example shows mail sent by Smith at host USC-ISIF, to
      Jones, Green, and Brown at host BBN-UNIX.  Here we assume that
      host USC-ISIF contacts host BBN-UNIX directly.  The mail is
      accepted for Jones and Brown.  Green does not have a mailbox at
      host BBN-UNIX.

      -------------------------------------------------------------

         R: 220 BBN-UNIX.ARPA Simple Mail Transfer Service Ready
         S: HELO USC-ISIF.ARPA
         R: 250 BBN-UNIX.ARPA

         S: MAIL FROM:<Smith@USC-ISIF.ARPA>
         R: 250 OK

         S: RCPT TO:<Jones@BBN-UNIX.ARPA>
         R: 250 OK

         S: RCPT TO:<Green@BBN-UNIX.ARPA>
         R: 550 No such user here

         S: RCPT TO:<Brown@BBN-UNIX.ARPA>
         R: 250 OK

         S: DATA
         R: 354 Start mail input; end with <CRLF>.<CRLF>
         S: Blah blah blah...
         S: ...etc. etc. etc.
         S: .
         R: 250 OK

         S: QUIT
         R: 221 BBN-UNIX.ARPA Service closing transmission channel

Transmission Control Protocol

• When the TCP layer receives the application layer protocol data from above, it segments it into manageable ‘chunks’ and then adds a TCP header with specific TCP information to each ‘chunk’. The information contained in the TCP header includes the port number of the application the data needs to be sent to.
• When the TCP layer receives a packet from the IP layer below it, the TCP layer strips the TCP header data from the packet, does some data reconstruction if necessary, and then sends the data to the correct application using the port number taken from the TCP header.

Diagram 7

Internet Protocol

Diagram 8

Diagram 9