WEBVTT - This file was automatically generated by VIMEO

0
00:00:12.300 --> 00:00:15.300
Hello everyone. So in this video we are

1
00:00:15.300 --> 00:00:18.800
 going to see how we can use nmap for

2
00:00:18.800 --> 00:00:20.100
 Recon.

3
00:00:21.400 --> 00:00:21.500
So

4
00:00:22.300 --> 00:00:25.800
in this video we are going to see how you can perform trace

5
00:00:25.800 --> 00:00:28.300
 route scan using and map

6
00:00:28.300 --> 00:00:31.300
 which is very useful to identify the

7
00:00:31.300 --> 00:00:31.900
 trace.

8
00:00:32.600 --> 00:00:35.700
Of the root to your target server.

9
00:00:36.400 --> 00:00:39.900
and to identify the Hops that you

10
00:00:39.900 --> 00:00:41.900
 are taking between

11
00:00:42.900 --> 00:00:45.200
Your network to the Target server?

12
00:00:47.200 --> 00:00:50.400
So the syntax of doing this scan is nmap the target

13
00:00:50.400 --> 00:00:53.900
 IP followed by hyphen hyphen trace route.

14
00:00:54.700 --> 00:00:57.200
So you can scan a Target by simply giving an

15
00:00:57.200 --> 00:01:00.800
 IP address and specifying the trace route flag. You can

16
00:01:00.800 --> 00:01:03.100
 always add hyphen V to see the

17
00:01:03.100 --> 00:01:06.200
 output in verbose mode and also you can

18
00:01:06.200 --> 00:01:08.200
 see a example is given over here.

19
00:01:10.500 --> 00:01:13.400
So it is the Practical time and let's see, how can

20
00:01:13.400 --> 00:01:15.200
 you perform the trace routes can

21
00:01:17.200 --> 00:01:20.200
as you can see on the terminal I have typed the

22
00:01:20.200 --> 00:01:23.300
 command which is nmap hyphen hyphen traced out -

23
00:01:23.300 --> 00:01:23.800
 p

24
00:01:24.400 --> 00:01:27.500
Port 80 which means I'm going to scan for Port 80

25
00:01:27.500 --> 00:01:30.800
 and my target which is scan me Dot nmap.org.

26
00:01:31.800 --> 00:01:35.400
As you can see this particular scan requires

27
00:01:34.400 --> 00:01:36.700
 root privileges.

28
00:01:38.400 --> 00:01:38.700
so

29
00:01:39.600 --> 00:01:42.400
you can run this can by typing the pseudo command

30
00:01:42.400 --> 00:01:45.000
 or you can become the root user.

31
00:01:47.100 --> 00:01:49.300
So I will switch quickly to the root user.

32
00:01:50.400 --> 00:01:52.500
And now I'm going to run the same command.

33
00:01:59.100 --> 00:02:02.300
Once I run this command you can see the nmap has

34
00:02:02.300 --> 00:02:05.200
 started. We are not able to see the output onto the

35
00:02:05.200 --> 00:02:05.500
 screen.

36
00:02:06.500 --> 00:02:09.600
Because we did not add hyphen V but you

37
00:02:09.600 --> 00:02:12.500
 can see the scan has completed and the output is

38
00:02:12.500 --> 00:02:14.200
 visible to us on the screen.

39
00:02:15.300 --> 00:02:17.100
Alright, let's see the output.

40
00:02:17.900 --> 00:02:20.300
In the output you can see the trace route which

41
00:02:20.300 --> 00:02:23.700
 has happened and you can identify from my

42
00:02:23.700 --> 00:02:26.800
 computer the first request that went was

43
00:02:26.800 --> 00:02:27.500
 from my router.

44
00:02:28.600 --> 00:02:31.600
That is the first IP address as you can see over here.

45
00:02:32.500 --> 00:02:35.100
Then the request went to this particular IP address.

46
00:02:35.900 --> 00:02:38.300
The next was this the next one was

47
00:02:38.300 --> 00:02:41.400
 this before reaching my target, which

48
00:02:41.400 --> 00:02:43.800
 was can be Dot nmap.org.

49
00:02:44.800 --> 00:02:46.600
finally to this IP address

50
00:02:49.100 --> 00:02:52.300
so we have identified this way that

51
00:02:53.500 --> 00:02:56.800
the trace route output gives us the

52
00:02:56.800 --> 00:02:59.500
 Hops that our request takes between

53
00:02:59.500 --> 00:03:01.800
 different different servers.

54
00:03:02.500 --> 00:03:03.200
in between

55
00:03:04.900 --> 00:03:07.800
alright, so let's try to scan another

56
00:03:07.800 --> 00:03:10.200
 server this time. So let's say

57
00:03:10.200 --> 00:03:13.500
 I will scan hectify this time. So let

58
00:03:13.500 --> 00:03:15.900
 me just type actify dot in my website.

59
00:03:16.800 --> 00:03:18.900
And you can see the scan has started again.

60
00:03:20.100 --> 00:03:23.500
This time, let's see. What is the trace

61
00:03:23.500 --> 00:03:24.200
 route output?

62
00:03:25.200 --> 00:03:28.600
As you can see the servers has changed this time

63
00:03:28.600 --> 00:03:31.600
 and the final request is been

64
00:03:31.600 --> 00:03:34.900
 going to the web hosting server, which I have purchased

65
00:03:34.900 --> 00:03:37.200
 which is server 2 Double 3

66
00:03:37.400 --> 00:03:40.500
 - 2 dot web hosting.com and this

67
00:03:40.500 --> 00:03:42.900
 is the IP address of my server.

68
00:03:44.300 --> 00:03:47.200
This way you can identify where the server

69
00:03:47.200 --> 00:03:50.700
 has hosted which is the hosting service and how

70
00:03:50.700 --> 00:03:52.700
 are the Hops taking place in between?

71
00:03:53.500 --> 00:03:56.600
So I hope you guys understood how you can perform

72
00:03:56.600 --> 00:04:00.400
 a trace route scan and identify the

73
00:03:59.400 --> 00:04:02.100
 Hops in between as well as

74
00:04:02.100 --> 00:04:05.400
 there is the target server located on.

75
00:04:06.900 --> 00:04:07.300
Thank you.
