This document provides an overview of hazard identification and detection in URLs. It discusses how phishing is a common attack where fraudulent websites try to steal personal information. Machine learning is presented as a powerful tool for detecting phishing attacks by analyzing website URLs and their contents. The document then summarizes various unified modeling language (UML) diagrams that can be used for modeling software, including use case diagrams, class diagrams, sequence diagrams, activity diagrams, component diagrams, deployment diagrams, and data flow diagrams.

1. HAZARD IDENTIFICATION AND DETECTION IN URL’s
PRESENTED BY- UNDER THE GUIDANCE OF-
A.EKSHITHA(20691F00D5) DR.S.V.S GANGA DEVI
PROFESSOR

2. ABSTRACT
 Phishing is a common attack on credulous people by making them to disclose their unique
information using counterfeit websites. The objective of phishing website URLs is to purloin the
personal information like user name, passwords and online banking transactions. Phishers use
the websites which are visually and semantically similar to those real websites. As technology
continues to grow, phishing techniques started to progress rapidly and this needs to be
prevented by using anti-phishing mechanisms to detect phishing. Machine learning is a
powerful tool used to strive against phishing attacks. This project surveys the features used for
detection and detection techniques using machine learning.

3. INTRODUCTION
 Phishing is the most unsafe criminal exercises in cyber space. Since most of the users go online
to access the services provided by government and financial institutions, there has been a
significant increase in phishing attacks for the past few years. Phishers started to earn money and
they are doing this as a successful business. It is very easy to create counterfeit websites, which
looks like a genuine website in terms of layout and content. Even, the content of these websites
would be identical to their legitimate websites. The reason for creating these websites is to get
private data from users like account numbers, login id, passwords of debit and credit card, etc.
 Moreover, attackers ask security questions to answer to posing as a high level security measure
providing to users. When users respond to those questions, they get easily trapped into phishing
attacks. Many researches have been going on to prevent phishing attacks by different
communities around the world. Phishing attacks can be prevented by detecting the websites and
creating awareness to users to identify the phishing websites. Machine learning algorithms have
been one of the powerful techniques in detecting phishing websites. In this study, various methods
of detecting phishing websites have been discussed.

4. UML DIAGRAMS
 UML stands for Unified Modeling Language. UML is a standardized general-purpose
modeling language in the field of object-oriented software engineering. The standard is
managed, and was created by, the Object Management Group. The goal is for UML to
become a common language for creating models of object oriented computer software. The
Unified Modeling Language is a standard language for specifying,Visualization, Constructing
and documenting the artifacts of software system,as well as for business modeling and
other non-software systems.
 The UML represents a collection of best engineering practices that have proven successful
in the modeling of large and complex systems.The UML is a very important part of
developing objects oriented software and the software development process. The UML
uses mostlygraphical notations to express the design of software projects.

5. UML DIAGRAMS
GOALS :
The Primary goals in the design of the UML are as follows:
1.Provide users a ready-to-use, expressive visual modeling Language so that they can develop
and exchange meaningful models.
2. Provide extendibility and specialization mechanisms to extend the core concepts.
3. Be independent of particular programming languages and developmentprocess.
4. Provide a formal basis for understanding the modeling language.
5. Encourage the growth of OO tools market.
6.Support higher level development concepts such as collaborations,frameworks, patterns and
components.
7. Integrate best practices.

6. USE CASE DIAGRAM
 A use case diagram in the Unified Modeling Language (UML) is a type of behavioral diagram
defined by and created from a Use-case analysis. Its purpose is to present a graphical overview of
the functionality provided by a system in terms of actors, their goals (represented as use cases),
and anydependencies between those use cases. The main purpose of a use case diagramis to
show what system functions are performed for which actor. Roles of theactors in the system can
be depicted.

9. CLASS DIAGRAM
 In software engineering,a class diagram in the unified modeling language(UML) is a type of ststic
structure diagram that describes the structure of a system by showing the system’s classes ,their
attributes,operations(or methods),and the relationships among the classes.It explains which class
contain information

11. SEQUENCE DIAGRAM
 A sequence diagram in Unified Modeling Language (UML) is a kind of interaction diagram
that shows how processes operate with one another and in what order. It is a construct of a
Message Sequence Chart. Sequence diagrams are sometimes called event diagrams, event
scenarios, and timing diagrams.

13. ACTVITY DIAGRAM
 Activity diagrams are graphical representations of workflows of stepwise activities and actions
with support for choice, iteration and concurrency. In the Unified Modeling Language, activity
diagrams can be used to describe the business and operational step-by-step workflows of
components in a system. An activity diagram shows the overall flow of control.

15. COMPONENT DIAGRAM
 Component diagrams are used to describe the physical artifacts of a system.This artifact includes files,
executables, libraries etc. So the purpose of this diagram is different, Component diagrams are used
during the implementation phase of an application. But it is prepared well in advance to visualize the
implementation details. Initially the system is designed using different UML diagrams and then when the
artifacts are ready component diagrams are used to get an idea of the implementation.

17. DEPLOYMENT DIAGRAM
 Deployment diagram represents the deployment view of a system. It is related to the component
diagram. Because the components are deployed using the deployment diagrams. A deployment
diagram consists of nodes. Nodes are nothing but physical hardwares used to deploy the
application.

19. DFD DIAGRAM
 A picture is worth a thousand words. A Data Flow Diagram (DFD) is a traditional way to visualize the
information flows within a system. A neat andclear DFD can depict a good amount of the system
requirements graphically. It can be manual, automated, or a combination of both. It shows how
information enters and leaves the system, what changes the information and where information is
stored. The purpose of a DFD is to show the scope and boundaries of a system as a whole. It may be
used as a communications tool between a systems analyst and any person who plays a part in the
system that acts as the starting point for redesigning a system.
 It is usually begin with a context diagram as level 0 of the DFD diagram, a simple representation of
the whole system. To elaborate further from that, we drill down to a level 1 diagram with lower-level
functions decomposed from the major functions of the system. This could continue to evolve to
become a level2 diagram when further analysis is required. Progression to levels 3, 4 and so on is
possible but anything beyond level 3 is not very common. Please bear in mind that the level of detail
for decomposing a particular function depending on the complexity that function.

22. THANK YOU