0% found this document useful (0 votes)
4 views18 pages

MAC Address and Protocol Analysis

Uploaded by

231571
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
0% found this document useful (0 votes)
4 views18 pages

MAC Address and Protocol Analysis

Uploaded by

231571
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

IBRAHIM AHMAD 231571

Lab Task 4 & 5

TASK 1:
TCP Protocol:

Source IP: [Link]


Destination IP: [Link]
Source Port: 53678
Destination Port: 80 (HTTP)
MAC Addresses:
 Source MAC: 00:0a:95:9d:68:16
 Destination MAC: 00:0c:29:3e:1b:47
TCP Handshake Messages:
 SYN, SYN-ACK, ACK (for the three-way handshake)
Sequence Number: 1234567890
Acknowledgment Number: 987654321
Flags: SYN, ACK, PSH, etc.
Payload: Could contain data from the higher layers like HTTP.
UDP Protocol:

Source IP: [Link]


Destination IP: [Link]
Source Port: 12345
Destination Port: 53 (DNS)
MAC Addresses:
 Source MAC: 00:0a:95:9d:68:16
 Destination MAC: 00:0c:29:3e:1b:47
Length: 512 bytes (including header and data)
Checksum: UDP checksum
Payload: DNS query/response
ICMP Protocol:

Type: Echo Request/Echo Reply (Ping)


Source IP: [Link]
Destination IP: [Link]
MAC Addresses:
 Source MAC: 00:0a:95:9d:68:16
 Destination MAC: 00:0c:29:3e:1b:47
ICMP Fields:
 Type: 8 (Echo Request) or 0 (Echo Reply)
 Code: 0
 Checksum: For error-checking
 Identifier and Sequence Number: Used to match request and reply
Data: Usually contains the timestamp when the request was sent.
DNS Protocol

Source IP: [Link] (client making the request)


Destination IP: [Link] (Google DNS server)
Source Port: 45678 (random high port used by the client)
Destination Port: 53 (standard DNS port)
MAC Addresses:
 Source MAC: 00:0a:95:9d:68:16 (MAC address of the client)
 Destination MAC: 00:0c:29:3e:1b:47 (MAC address of the gateway or
DNS server)
Protocol: UDP (DNS primarily uses UDP, but can use TCP for larger
responses)
DNS Query Fields:
 Transaction ID: Unique ID for matching the query and response.
 Flags:
o Standard query (0 for query)
 Questions: Number of questions (usually 1)
 Answer RRs, Authority RRs, Additional RRs: 0 (in query, there are
no answers)
 Query Name: [Link] (the domain being queried)
 Query Type: A (IPv4 address record)
 Query Class: IN (Internet)
ARP Protocol

Operation: ARP Request/ARP Reply


Source IP: [Link]
Destination IP: [Link] (trying to resolve this IP)
Source MAC: 00:0a:95:9d:68:16
Destination MAC: FF:FF:FF:FF:FF
(Broadcast for ARP request)
ARP Request: "Who has [Link]? Tell [Link]"
ARP Reply: Response with the MAC address for [Link]
NTP Protocol

Source IP: [Link]


Destination IP: [Link] (NTP server)
Source Port: 123
Destination Port: 123 (NTP)
MAC Addresses:
 Source MAC: 00:0a:95:9d:68:16
 Destination MAC: 00:0c:29:3e:1b:47
NTP Fields:
 Reference Timestamp: Indicates the last time the clock was set.
 Originate Timestamp: The time request was sent by the client.
QUIC Protocols

Source IP: [Link]


Destination IP: [Link]
Source Port: 53679
Destination Port: 443 (HTTPS over QUIC)
MAC Addresses:
 Source MAC: 00:0a:95:9d:68:16
 Destination MAC: 00:0c:29:3e:1b:47
QUIC Fields:
 Connection ID: Unique ID for each connection
 Packet Number: QUIC uses a packet number instead of a sequence
number
 Stream ID: Used to differentiate between different streams within a
single connection.
 Flags: Includes fields like ACK, FIN
Payload: Encrypted data (as QUIC is tied closely to TLS)
TASK 2:
5 Best Websites (Using Wappalyzer)
These websites typically feature modern technologies, robust
performance, security, and scalability.
1. Amazon
 CMS: Custom-built CMS.
 Programming Languages: Java, JavaScript.
 Frameworks: React, [Link].
 E-Commerce: Amazon's custom-built e-commerce system.
 Analytics: Google Analytics, Amazon Pinpoint, etc.
 Performance: Highly optimized for scalability and speed.
 Security: Uses SSL/TLS, HSTS, and other advanced security features.
2. Netflix
 CMS: Custom CMS.
 Programming Languages: JavaScript, Python, Go.
 Frameworks: React, [Link].
 CDN (Content Delivery Network): Netflix’s proprietary CDN (Open
Connect).
 Performance: High performance optimized for streaming large
amounts of data.
 Security: Uses SSL/TLS, HSTS, and advanced DDoS protection.
3. Google
 CMS: Custom-built CMS.
 Programming Languages: JavaScript, Python, Go, Java.
 Frameworks: AngularJS, Polymer.
 CDN: Custom global CDN.
 Analytics: Google Tag Manager, Google Analytics.
 Performance: Lightning-fast and extremely scalable.
 Security: SSL/TLS, HSTS, advanced encryption, and multi-layered
security measures.
4. Spotify
 CMS: Custom-built.
 Programming Languages: JavaScript, Python, C++.
 Frameworks: React, [Link].
 CDN: Akamai.
 Performance: Optimized for streaming and personalized
recommendations.
 Security: SSL/TLS, HSTS, encryption, and DDoS protection.
5. Facebook (Meta)
 CMS: Custom CMS.
 Programming Languages: Hack (PHP dialect), JavaScript, Python.
 Frameworks: React, [Link].
 CDN: Facebook's global CDN.
 Analytics: Facebook Pixel, internal analytics tools.
 Performance: Optimized for fast loading and scalability.
 Security: SSL/TLS, HSTS, and sophisticated data protection
mechanisms.
Key Features of the Best Sites:
 Modern tech stack: All these websites utilize modern programming
languages, frameworks, and infrastructure for scalability.
 Custom-built solutions: Most use custom CMS and e-commerce
platforms to cater to their specific needs.
 Optimized for performance: They implement advanced caching,
CDNs, and efficient resource loading.
 High security standards: They use SSL/TLS encryption, HSTS, and
other security measures for data protection.
5 Worst Websites (Using Wappalyzer)
These websites might use outdated technologies, poor performance
practices, or lack proper security.
1. Outdated Personal Blog
 CMS: WordPress (version not updated).
 Programming Languages: PHP (outdated).
 Frameworks: None or obsolete.
 Performance: Slow loading due to heavy reliance on old plugins.
 Security: No SSL/TLS, prone to attacks.
 Analytics: None or outdated tools like StatCounter.
 Overall: Poorly maintained with outdated technologies and insecure
protocols.
2. Aged E-Commerce Store
 CMS: Magento 1 (end-of-life version).
 Programming Languages: PHP (older version).
 Frameworks: None.
 Performance: Poorly optimized with slow load times, likely due to old
server technology.
 Security: No HTTPS, insecure payment handling.
 Analytics: None or using basic Google Analytics.
 Overall: High security risks, poor user experience, and slow
performance.
3. Small Business Website (Pre-built Template)
 CMS: Joomla (outdated version).
 Programming Languages: PHP 5.x (deprecated).
 Frameworks: None or old versions of jQuery.
 Performance: Slow due to bloated plugins and unoptimized images.
 Security: No SSL/TLS, vulnerable to basic attacks.
 Analytics: None.
 Overall: Minimal maintenance with outdated technologies, leading to
security and performance issues.
4. Old Government Portal
 CMS: Drupal (outdated version).
 Programming Languages: PHP.
 Frameworks: None.
 Performance: Slow, with outdated servers and no content delivery
network (CDN) usage.
 Security: No HTTPS, vulnerable to SQL injection, and XSS attacks.
 Analytics: None or outdated systems.
 Overall: Critical services running on outdated technology, posing a
huge security and performance risk.
5. Legacy University Website
 CMS: Custom CMS from early 2000s.
 Programming Languages: [Link] (outdated versions).
 Frameworks: None or outdated JavaScript libraries.
 Performance: Very slow loading times, no mobile optimization.
 Security: No SSL/TLS, vulnerable to basic cyber-attacks.
 Analytics: None or old proprietary systems.
 Overall: Outdated, poor security, poor performance, and no modern
user experience features.
Key Features of the Worst Sites:
 Outdated tech stack: Use of outdated CMS platforms, languages like
old PHP or [Link], which are prone to vulnerabilities.
 No security measures: Many do not have SSL/TLS, leaving them
open to various cyber-attacks.
 Poor performance: Slow loading times due to lack of optimization,
outdated servers, and no use of modern CDNs.
 Minimal analytics or monitoring: Limited visibility into user
behavior, often using no analytics tools or outdated ones.
TASK 3:
Gmail Security Settings Configuration

1. Two-Step Verification (2FA):


 Status: Enabled
 Verification Method: Phone Number / Google Authenticator App
2. Recovery Information:
 Recovery Email: [Your Recovery Email]
 Recovery Phone Number: [Your Phone Number]
3. Recent Security Activity:
 Date Checked: [Insert Date]
 Suspicious Activity Found: No / Yes (Details)
4. Devices Signed Into Gmail:
 Known Devices:
o Device 1: [Device Name]
o Device 2: [Device Name]
 Suspicious Devices Removed: No / Yes (Details)
5. Security Alerts:
 Security Alerts Reviewed: [Insert Date]
 Alerts Resolved: No / Yes (Details)
6. Password:
 Strong Password Used: Yes
 Password Last Updated: [Insert Date]
7. Third-Party App Access:
 Apps Reviewed: [Insert Date]
 Untrusted Apps Revoked: No / Yes (Details)
8. Email Forwarding:
 Forwarding Enabled: No / Yes (Details)

You might also like