Scribd
Upload
2 views8 pages

Analyzing HTTP and DNS Protocols

The document is a lab sheet focused on analyzing application layer protocols, specifically HTTP and DNS. It includes questions regarding HTTP versions, IP addresses, status codes, DNS queries, and connection establishment methods. The responses require practical observations from browser interactions with a server and DNS functionalities.

Uploaded by

abhinavdileep461
Copyright
© All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
2 views8 pages

Analyzing HTTP and DNS Protocols

The document is a lab sheet focused on analyzing application layer protocols, specifically HTTP and DNS. It includes questions regarding HTTP versions, IP addresses, status codes, DNS queries, and connection establishment methods. The responses require practical observations from browser interactions with a server and DNS functionalities.

Uploaded by

abhinavdileep461
Copyright
© All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd

LABSHEET 3 [Link].

u4cse23202
Analysing Application layer protocols –
HTTP, DNS

1. Is your browser running HTTP version 1.0, 1.1, or 2? What version of HTTP is
the server running?
Ans:

2. What languages (if any) does your browser indicate that it can accept to the
server?

Ans:
3. What is the IP address of your computer? What is the IP address of the
[Link] server?
Ans:

Ip address of host: [Link]


The ip address of the server: [Link]

[Link] is the status code returned from the server to your browser?
Ans:

5. When was the HTML file that you are retrieving last modified at the server?
Ans:
6. How many bytes of content are being returned to your browser in the first
HTTP Response for first GET to [Link] server?
Ans:

7. Inspect the contents of the first HTTP GET request from your browser to the
server. Do you see an “IF-MODIFIED-SINCE” line in the HTTP GET?

8. Inspect the contents of the server response. Did the server explicitly return the
contents of the file? How can you tell?
Ans:

->Yes. The status code is 200 OK, and the response includes the full
HTML content. You can see the payload in the packet details.

9. Now inspect the contents of the second HTTP GET request from your browser
to the server. Do you see an “IF-MODIFIED-SINCE:” line in the HTTP GET1? If so,
what information follows the “IF-MODIFIED-SINCE:” header?
Ans:
This tells the server: “Only send the file if it has changed since
this date.”

10. What is the HTTP status code and phrase returned from the server in response
to this second HTTP GET? Did the server explicitly return the contents of the file?
Explain.
Ans:

This means the file hasn’t changed, so the server did not
resend the content.

11 Locate the DNS query and response messages. Are they


sent over UDP or TCP?
Ans:

Typically, DNS queries and responses are sent over UDP.

12. What is the destination port for the DNS query? What is
the source port of the DNS response?
Ans:

DESTINATION PORT: 62052


SOURCE PORT: 53

14. Examine the DNS response message. How many


“answers” are provided? What do each of these answers
contain?
Ans:

15. . What is the destination port for the DNS query message?
What is the source port of DNS response message?
Ans:
16. To what IP address is the DNS query message sent? Is this
the IP address of your default local DNS server?
Ans:

NO ,it is not.

17. Before retrieving each image/object in your web page,


does your host issue new DNS queries?

Ans:

No they all comes from the same domain

18. Before the HTTP how the connection is established?


Ans:
TCP 3 way Handshake

You might also like