PYTHON LAB ### Assignment Description This week, you will be will be completing a script that gathers information about
Posted: Sat Nov 27, 2021 2:30 pm
PYTHON LAB
### Assignment Description
This week, you will be will be completing a script that gathers
information about an email address using an API and JSON. This is
another example of footprinting, or OSINT, in the cybersecurity
field.
Part 1 - Parse the command line, grab email address from
argument:
# python emailInfo.py m..c@g m a i l.com and saving to a
variable
# sys.argv[0] is emailInfo.py, sys.argv[1] is m..c@g m a i
l.com
#
# Extra Credit (3 points) - Display help for no arguments or --help
flag
# (must work completely)
# Part 2 - Request page
https://api.trumail.io/v2/lookups/json?email=
# appending the email passed into sys.argv[1]
# and call raise_for_status on the request object
# Part 3 - Parse the request text JSON and save the new Python
dictionary
# into a variable (hint: use json.loads)
# Part 4 - MAKE SURE THIS IS FORMATTED NICELY
# Display the following information to the user:
# Email address (address key)
# Username (username key)
# Domain (domain key)
# Valid format (validFormat key)
# Deliverable (deliverable key)
# Full Inbox (fullInbox key)
# Host Exists (hostExists key)
# Catch All (catchAll key)
# Disposable (disposable key)
# Free (free key)
print("\nEmail Analyzer 1.0\n\nInformation for email: " +
sys.argv[1])
print("=====================================================")
print("Username: ")
1. Correct work on Part 1 - Up to 1 pts under Functional
Expectations
2. Correct work on Part 2 - Up to 1 pts under Functional
Expectations
3. Correct work on Part 3 - Up to 2 pts under Functional
Expectations
4. Correct work on Part 4 - Up to 2 pts under Functional
Expectations
5. Sufficient comments and docstrings where required - Up to 1 pts
under Functional Expectations
6. Output is readable to the end-user and looks professional - Up
to 1 pts under Functional Expectations
7. Code runs without error - Up to 1 pts under Functional
Expectations
8. OPTIONAL - 3 Points Extra Credit - Displays help on --help or no
argument (must work completely without error)
### Assignment Description
This week, you will be will be completing a script that gathers
information about an email address using an API and JSON. This is
another example of footprinting, or OSINT, in the cybersecurity
field.
Part 1 - Parse the command line, grab email address from
argument:
# python emailInfo.py m..c@g m a i l.com and saving to a
variable
# sys.argv[0] is emailInfo.py, sys.argv[1] is m..c@g m a i
l.com
#
# Extra Credit (3 points) - Display help for no arguments or --help
flag
# (must work completely)
# Part 2 - Request page
https://api.trumail.io/v2/lookups/json?email=
# appending the email passed into sys.argv[1]
# and call raise_for_status on the request object
# Part 3 - Parse the request text JSON and save the new Python
dictionary
# into a variable (hint: use json.loads)
# Part 4 - MAKE SURE THIS IS FORMATTED NICELY
# Display the following information to the user:
# Email address (address key)
# Username (username key)
# Domain (domain key)
# Valid format (validFormat key)
# Deliverable (deliverable key)
# Full Inbox (fullInbox key)
# Host Exists (hostExists key)
# Catch All (catchAll key)
# Disposable (disposable key)
# Free (free key)
print("\nEmail Analyzer 1.0\n\nInformation for email: " +
sys.argv[1])
print("=====================================================")
print("Username: ")
1. Correct work on Part 1 - Up to 1 pts under Functional
Expectations
2. Correct work on Part 2 - Up to 1 pts under Functional
Expectations
3. Correct work on Part 3 - Up to 2 pts under Functional
Expectations
4. Correct work on Part 4 - Up to 2 pts under Functional
Expectations
5. Sufficient comments and docstrings where required - Up to 1 pts
under Functional Expectations
6. Output is readable to the end-user and looks professional - Up
to 1 pts under Functional Expectations
7. Code runs without error - Up to 1 pts under Functional
Expectations
8. OPTIONAL - 3 Points Extra Credit - Displays help on --help or no
argument (must work completely without error)