WEBVTT Kind: captions Language: en 00:00:00.000 --> 00:00:02.090 align:start position:0% thanks<00:00:00.539> for<00:00:00.780> stopping<00:00:01.260> by<00:00:01.380> my<00:00:01.620> channel<00:00:01.800> in 00:00:02.090 --> 00:00:02.100 align:start position:0% thanks for stopping by my channel in 00:00:02.100 --> 00:00:03.169 align:start position:0% thanks for stopping by my channel in this<00:00:02.220> course<00:00:02.399> we're<00:00:02.639> going<00:00:02.760> to<00:00:02.820> be<00:00:02.879> covering 00:00:03.169 --> 00:00:03.179 align:start position:0% this course we're going to be covering 00:00:03.179 --> 00:00:05.570 align:start position:0% this course we're going to be covering Recon<00:00:03.780> for<00:00:04.080> web<00:00:04.319> applications<00:00:04.860> and<00:00:05.279> Bug 00:00:05.570 --> 00:00:05.580 align:start position:0% Recon for web applications and Bug 00:00:05.580 --> 00:00:08.390 align:start position:0% Recon for web applications and Bug bounty<00:00:06.060> hunting<00:00:06.420> my<00:00:07.080> goal<00:00:07.440> in<00:00:07.680> creating<00:00:08.160> this 00:00:08.390 --> 00:00:08.400 align:start position:0% bounty hunting my goal in creating this 00:00:08.400 --> 00:00:10.790 align:start position:0% bounty hunting my goal in creating this course<00:00:08.519> is<00:00:08.880> to<00:00:09.000> give<00:00:09.120> you<00:00:09.300> the<00:00:09.840> best<00:00:10.139> shot<00:00:10.440> at 00:00:10.790 --> 00:00:10.800 align:start position:0% course is to give you the best shot at 00:00:10.800 --> 00:00:12.290 align:start position:0% course is to give you the best shot at finding<00:00:11.160> a<00:00:11.340> really<00:00:11.460> good<00:00:11.639> Target<00:00:11.820> that<00:00:12.120> you're 00:00:12.290 --> 00:00:12.300 align:start position:0% finding a really good Target that you're 00:00:12.300 --> 00:00:14.330 align:start position:0% finding a really good Target that you're going<00:00:12.420> to<00:00:12.540> find<00:00:12.660> vulnerabilities<00:00:13.380> on<00:00:13.799> a<00:00:14.280> lot 00:00:14.330 --> 00:00:14.340 align:start position:0% going to find vulnerabilities on a lot 00:00:14.340 --> 00:00:16.070 align:start position:0% going to find vulnerabilities on a lot of<00:00:14.460> bug<00:00:14.580> bounty<00:00:15.059> hunters<00:00:15.299> who<00:00:15.480> do<00:00:15.660> this<00:00:15.839> every 00:00:16.070 --> 00:00:16.080 align:start position:0% of bug bounty hunters who do this every 00:00:16.080 --> 00:00:18.769 align:start position:0% of bug bounty hunters who do this every single<00:00:16.320> day<00:00:16.440> usually<00:00:17.279> just<00:00:17.460> run<00:00:17.699> some<00:00:18.119> kind<00:00:18.359> of 00:00:18.769 --> 00:00:18.779 align:start position:0% single day usually just run some kind of 00:00:18.779 --> 00:00:20.810 align:start position:0% single day usually just run some kind of subdomain<00:00:19.440> enumeration<00:00:19.980> and<00:00:20.279> then<00:00:20.400> they<00:00:20.580> go 00:00:20.810 --> 00:00:20.820 align:start position:0% subdomain enumeration and then they go 00:00:20.820 --> 00:00:22.189 align:start position:0% subdomain enumeration and then they go out<00:00:20.939> and<00:00:21.180> see<00:00:21.480> what's<00:00:21.660> there<00:00:21.900> and<00:00:22.080> start 00:00:22.189 --> 00:00:22.199 align:start position:0% out and see what's there and start 00:00:22.199 --> 00:00:24.109 align:start position:0% out and see what's there and start attacking<00:00:22.680> those<00:00:22.920> specific<00:00:23.220> subdomains<00:00:23.880> and 00:00:24.109 --> 00:00:24.119 align:start position:0% attacking those specific subdomains and 00:00:24.119 --> 00:00:25.730 align:start position:0% attacking those specific subdomains and for<00:00:24.300> the<00:00:24.420> rest<00:00:24.539> of<00:00:24.660> us<00:00:24.720> we<00:00:24.960> may<00:00:25.140> want<00:00:25.320> to<00:00:25.439> find 00:00:25.730 --> 00:00:25.740 align:start position:0% for the rest of us we may want to find 00:00:25.740 --> 00:00:28.130 align:start position:0% for the rest of us we may want to find easier<00:00:26.160> targets<00:00:26.699> that<00:00:26.760> have<00:00:26.939> not<00:00:27.180> had<00:00:27.480> as<00:00:27.960> many 00:00:28.130 --> 00:00:28.140 align:start position:0% easier targets that have not had as many 00:00:28.140 --> 00:00:30.529 align:start position:0% easier targets that have not had as many people<00:00:28.380> attack<00:00:28.740> them<00:00:29.099> I<00:00:29.580> want<00:00:29.699> to<00:00:29.939> help<00:00:30.359> you 00:00:30.529 --> 00:00:30.539 align:start position:0% people attack them I want to help you 00:00:30.539 --> 00:00:33.110 align:start position:0% people attack them I want to help you find<00:00:31.080> the<00:00:31.500> really<00:00:31.740> old<00:00:32.099> subdomain<00:00:32.820> that<00:00:33.000> maybe 00:00:33.110 --> 00:00:33.120 align:start position:0% find the really old subdomain that maybe 00:00:33.120 --> 00:00:34.670 align:start position:0% find the really old subdomain that maybe has<00:00:33.360> been<00:00:33.480> forgotten<00:00:33.840> about<00:00:33.960> it's<00:00:34.320> out<00:00:34.559> of 00:00:34.670 --> 00:00:34.680 align:start position:0% has been forgotten about it's out of 00:00:34.680 --> 00:00:36.229 align:start position:0% has been forgotten about it's out of date<00:00:34.860> and<00:00:35.399> is<00:00:35.579> going<00:00:35.760> to<00:00:35.880> have<00:00:35.940> a<00:00:36.059> lot<00:00:36.180> of 00:00:36.229 --> 00:00:36.239 align:start position:0% date and is going to have a lot of 00:00:36.239 --> 00:00:37.790 align:start position:0% date and is going to have a lot of vulnerabilities<00:00:36.780> or<00:00:37.260> possible 00:00:37.790 --> 00:00:37.800 align:start position:0% vulnerabilities or possible 00:00:37.800 --> 00:00:40.250 align:start position:0% vulnerabilities or possible vulnerabilities<00:00:38.520> for<00:00:38.880> you<00:00:39.120> to<00:00:39.360> find<00:00:39.780> this 00:00:40.250 --> 00:00:40.260 align:start position:0% vulnerabilities for you to find this 00:00:40.260 --> 00:00:42.229 align:start position:0% vulnerabilities for you to find this course<00:00:40.440> is<00:00:40.620> going<00:00:40.800> to<00:00:40.860> focus<00:00:41.100> purely<00:00:41.520> on<00:00:41.760> recon 00:00:42.229 --> 00:00:42.239 align:start position:0% course is going to focus purely on recon 00:00:42.239 --> 00:00:43.610 align:start position:0% course is going to focus purely on recon sometimes<00:00:42.899> you're<00:00:43.079> going<00:00:43.200> to<00:00:43.260> come<00:00:43.379> across 00:00:43.610 --> 00:00:43.620 align:start position:0% sometimes you're going to come across 00:00:43.620 --> 00:00:45.290 align:start position:0% sometimes you're going to come across videos<00:00:43.860> that<00:00:44.100> say<00:00:44.280> we're<00:00:44.460> here<00:00:44.640> to<00:00:44.820> focus<00:00:45.180> on 00:00:45.290 --> 00:00:45.300 align:start position:0% videos that say we're here to focus on 00:00:45.300 --> 00:00:46.369 align:start position:0% videos that say we're here to focus on recon<00:00:45.660> and<00:00:45.899> then<00:00:45.960> they're<00:00:46.079> going<00:00:46.200> to<00:00:46.260> start 00:00:46.369 --> 00:00:46.379 align:start position:0% recon and then they're going to start 00:00:46.379 --> 00:00:47.810 align:start position:0% recon and then they're going to start showing<00:00:46.680> you<00:00:46.739> how<00:00:46.860> to<00:00:46.980> look<00:00:47.100> for<00:00:47.280> sensitive 00:00:47.810 --> 00:00:47.820 align:start position:0% showing you how to look for sensitive 00:00:47.820 --> 00:00:49.670 align:start position:0% showing you how to look for sensitive information<00:00:48.000> disclosure<00:00:48.840> and<00:00:49.260> that's<00:00:49.440> not 00:00:49.670 --> 00:00:49.680 align:start position:0% information disclosure and that's not 00:00:49.680 --> 00:00:51.410 align:start position:0% information disclosure and that's not really<00:00:49.860> going<00:00:50.100> to<00:00:50.280> be<00:00:50.399> our<00:00:50.640> purpose<00:00:50.940> this<00:00:51.300> is 00:00:51.410 --> 00:00:51.420 align:start position:0% really going to be our purpose this is 00:00:51.420 --> 00:00:53.569 align:start position:0% really going to be our purpose this is purely<00:00:51.899> about<00:00:52.079> finding<00:00:52.559> really<00:00:52.800> good<00:00:53.039> targets 00:00:53.569 --> 00:00:53.579 align:start position:0% purely about finding really good targets 00:00:53.579 --> 00:00:56.510 align:start position:0% purely about finding really good targets for<00:00:54.180> you<00:00:54.420> to<00:00:54.780> attack<00:00:55.079> and<00:00:55.620> I<00:00:55.860> decided<00:00:56.160> to<00:00:56.280> go 00:00:56.510 --> 00:00:56.520 align:start position:0% for you to attack and I decided to go 00:00:56.520 --> 00:00:59.090 align:start position:0% for you to attack and I decided to go ahead<00:00:56.640> and<00:00:56.820> show<00:00:57.059> you<00:00:57.239> one<00:00:57.719> or<00:00:57.960> two<00:00:58.260> tools<00:00:58.800> that 00:00:59.090 --> 00:00:59.100 align:start position:0% ahead and show you one or two tools that 00:00:59.100 --> 00:01:00.830 align:start position:0% ahead and show you one or two tools that is<00:00:59.219> going<00:00:59.340> to<00:00:59.399> help<00:00:59.520> you<00:00:59.640> in<00:00:59.760> this<00:00:59.940> process<00:01:00.539> in 00:01:00.830 --> 00:01:00.840 align:start position:0% is going to help you in this process in 00:01:00.840 --> 00:01:03.770 align:start position:0% is going to help you in this process in each<00:01:01.079> specific<00:01:01.500> area<00:01:01.800> of<00:01:02.340> your<00:01:02.879> recon<00:01:03.359> and<00:01:03.660> the 00:01:03.770 --> 00:01:03.780 align:start position:0% each specific area of your recon and the 00:01:03.780 --> 00:01:05.690 align:start position:0% each specific area of your recon and the reason<00:01:03.899> I<00:01:04.199> decided<00:01:04.619> to<00:01:04.860> do<00:01:05.220> this<00:01:05.339> is<00:01:05.580> because 00:01:05.690 --> 00:01:05.700 align:start position:0% reason I decided to do this is because 00:01:05.700 --> 00:01:07.429 align:start position:0% reason I decided to do this is because when<00:01:06.000> I<00:01:06.119> was<00:01:06.240> new<00:01:06.420> I<00:01:06.840> remember<00:01:06.960> reading 00:01:07.429 --> 00:01:07.439 align:start position:0% when I was new I remember reading 00:01:07.439 --> 00:01:09.109 align:start position:0% when I was new I remember reading through<00:01:07.560> books<00:01:07.979> and<00:01:08.220> listening<00:01:08.640> to<00:01:08.820> other 00:01:09.109 --> 00:01:09.119 align:start position:0% through books and listening to other 00:01:09.119 --> 00:01:11.210 align:start position:0% through books and listening to other people<00:01:09.360> talk<00:01:09.659> and<00:01:09.960> podcasts<00:01:10.560> and<00:01:10.920> they<00:01:11.040> would 00:01:11.210 --> 00:01:11.220 align:start position:0% people talk and podcasts and they would 00:01:11.220 --> 00:01:12.890 align:start position:0% people talk and podcasts and they would cover<00:01:11.400> five<00:01:11.820> six<00:01:12.060> seven<00:01:12.299> eight<00:01:12.659> different 00:01:12.890 --> 00:01:12.900 align:start position:0% cover five six seven eight different 00:01:12.900 --> 00:01:14.870 align:start position:0% cover five six seven eight different tools<00:01:13.380> and<00:01:13.799> I<00:01:13.920> remember<00:01:14.040> thinking<00:01:14.460> there's<00:01:14.640> no 00:01:14.870 --> 00:01:14.880 align:start position:0% tools and I remember thinking there's no 00:01:14.880 --> 00:01:16.490 align:start position:0% tools and I remember thinking there's no way<00:01:15.060> I'm<00:01:15.299> going<00:01:15.479> to<00:01:15.540> remember<00:01:15.659> which<00:01:16.080> one<00:01:16.260> to 00:01:16.490 --> 00:01:16.500 align:start position:0% way I'm going to remember which one to 00:01:16.500 --> 00:01:19.250 align:start position:0% way I'm going to remember which one to use<00:01:17.220> and<00:01:17.820> in<00:01:18.000> what<00:01:18.180> specific<00:01:18.420> case<00:01:18.720> and<00:01:19.020> then<00:01:19.080> a 00:01:19.250 --> 00:01:19.260 align:start position:0% use and in what specific case and then a 00:01:19.260 --> 00:01:21.170 align:start position:0% use and in what specific case and then a lot<00:01:19.320> of<00:01:19.439> times<00:01:19.560> these<00:01:20.220> videos<00:01:20.400> or<00:01:20.820> books 00:01:21.170 --> 00:01:21.180 align:start position:0% lot of times these videos or books 00:01:21.180 --> 00:01:22.789 align:start position:0% lot of times these videos or books didn't<00:01:21.360> even<00:01:21.479> tell<00:01:21.659> me<00:01:21.780> which<00:01:21.960> tool<00:01:22.320> was<00:01:22.500> the 00:01:22.789 --> 00:01:22.799 align:start position:0% didn't even tell me which tool was the 00:01:22.799 --> 00:01:25.370 align:start position:0% didn't even tell me which tool was the best<00:01:22.979> so<00:01:23.520> I've<00:01:23.640> narrowed<00:01:24.119> it<00:01:24.240> down<00:01:24.420> to<00:01:24.720> one<00:01:25.140> and 00:01:25.370 --> 00:01:25.380 align:start position:0% best so I've narrowed it down to one and 00:01:25.380 --> 00:01:27.530 align:start position:0% best so I've narrowed it down to one and most<00:01:25.619> of<00:01:25.740> the<00:01:25.860> time<00:01:25.979> two<00:01:26.400> tools<00:01:26.820> that<00:01:27.299> is<00:01:27.420> going 00:01:27.530 --> 00:01:27.540 align:start position:0% most of the time two tools that is going 00:01:27.540 --> 00:01:30.109 align:start position:0% most of the time two tools that is going to<00:01:27.659> help<00:01:27.840> you<00:01:28.080> in<00:01:28.560> your<00:01:28.740> recon<00:01:29.220> phase<00:01:29.580> and<00:01:30.060> I 00:01:30.109 --> 00:01:30.119 align:start position:0% to help you in your recon phase and I 00:01:30.119 --> 00:01:32.030 align:start position:0% to help you in your recon phase and I decided<00:01:30.420> to<00:01:30.479> show<00:01:30.659> you<00:01:30.780> two<00:01:31.080> tools<00:01:31.619> most<00:01:31.860> of 00:01:32.030 --> 00:01:32.040 align:start position:0% decided to show you two tools most of 00:01:32.040 --> 00:01:33.649 align:start position:0% decided to show you two tools most of the<00:01:32.159> time<00:01:32.280> because<00:01:32.580> sometimes<00:01:33.060> one<00:01:33.360> tool 00:01:33.649 --> 00:01:33.659 align:start position:0% the time because sometimes one tool 00:01:33.659 --> 00:01:35.330 align:start position:0% the time because sometimes one tool won't<00:01:33.900> be<00:01:34.080> working<00:01:34.259> and<00:01:34.740> you<00:01:34.979> need<00:01:35.100> to<00:01:35.280> know 00:01:35.330 --> 00:01:35.340 align:start position:0% won't be working and you need to know 00:01:35.340 --> 00:01:37.429 align:start position:0% won't be working and you need to know the<00:01:35.579> second<00:01:35.820> that<00:01:36.360> is<00:01:36.479> going<00:01:36.659> to<00:01:36.780> work<00:01:36.960> so<00:01:37.200> I've 00:01:37.429 --> 00:01:37.439 align:start position:0% the second that is going to work so I've 00:01:37.439 --> 00:01:39.469 align:start position:0% the second that is going to work so I've decided<00:01:37.799> to<00:01:37.920> narrow<00:01:38.220> down<00:01:38.400> to<00:01:38.640> the<00:01:38.820> best<00:01:39.060> tools 00:01:39.469 --> 00:01:39.479 align:start position:0% decided to narrow down to the best tools 00:01:39.479 --> 00:01:41.569 align:start position:0% decided to narrow down to the best tools that<00:01:39.780> I<00:01:39.960> think<00:01:40.200> are<00:01:40.680> going<00:01:40.799> to<00:01:40.920> help<00:01:41.100> give<00:01:41.460> you 00:01:41.569 --> 00:01:41.579 align:start position:0% that I think are going to help give you 00:01:41.579 --> 00:01:44.030 align:start position:0% that I think are going to help give you the<00:01:41.880> best<00:01:42.180> chance<00:01:42.479> and<00:01:42.900> the<00:01:43.020> most<00:01:43.200> success<00:01:43.799> in 00:01:44.030 --> 00:01:44.040 align:start position:0% the best chance and the most success in 00:01:44.040 --> 00:01:45.890 align:start position:0% the best chance and the most success in finding<00:01:44.520> bugs<00:01:45.000> so<00:01:45.299> I've<00:01:45.360> gone<00:01:45.600> ahead<00:01:45.780> and 00:01:45.890 --> 00:01:45.900 align:start position:0% finding bugs so I've gone ahead and 00:01:45.900 --> 00:01:47.810 align:start position:0% finding bugs so I've gone ahead and streamlined<00:01:46.619> this<00:01:46.860> course<00:01:47.040> for<00:01:47.340> you<00:01:47.460> and<00:01:47.640> I 00:01:47.810 --> 00:01:47.820 align:start position:0% streamlined this course for you and I 00:01:47.820 --> 00:01:48.890 align:start position:0% streamlined this course for you and I believe<00:01:47.939> it's<00:01:48.119> going<00:01:48.299> to<00:01:48.360> give<00:01:48.479> you<00:01:48.540> the<00:01:48.780> best 00:01:48.890 --> 00:01:48.900 align:start position:0% believe it's going to give you the best 00:01:48.900 --> 00:01:51.170 align:start position:0% believe it's going to give you the best attack<00:01:49.140> surface<00:01:49.680> and<00:01:50.040> the<00:01:50.399> best<00:01:50.520> chance<00:01:50.759> at 00:01:51.170 --> 00:01:51.180 align:start position:0% attack surface and the best chance at 00:01:51.180 --> 00:01:53.270 align:start position:0% attack surface and the best chance at success<00:01:51.600> let's<00:01:51.899> go<00:01:52.079> ahead<00:01:52.259> and<00:01:52.500> jump<00:01:52.860> into<00:01:53.100> it 00:01:53.270 --> 00:01:53.280 align:start position:0% success let's go ahead and jump into it 00:01:53.280 --> 00:01:54.649 align:start position:0% success let's go ahead and jump into it in<00:01:53.700> this<00:01:53.820> video<00:01:53.939> we're<00:01:54.180> going<00:01:54.360> to<00:01:54.420> talk<00:01:54.540> about 00:01:54.649 --> 00:01:54.659 align:start position:0% in this video we're going to talk about 00:01:54.659 --> 00:01:57.289 align:start position:0% in this video we're going to talk about how<00:01:55.079> to<00:01:55.200> scan<00:01:55.920> specific<00:01:56.579> Targets<00:01:57.000> in<00:01:57.119> bug 00:01:57.289 --> 00:01:57.299 align:start position:0% how to scan specific Targets in bug 00:01:57.299 --> 00:01:59.030 align:start position:0% how to scan specific Targets in bug Bounty<00:01:57.720> programs<00:01:58.020> as<00:01:58.200> well<00:01:58.320> as<00:01:58.380> fuzzing<00:01:58.799> our 00:01:59.030 --> 00:01:59.040 align:start position:0% Bounty programs as well as fuzzing our 00:01:59.040 --> 00:02:01.190 align:start position:0% Bounty programs as well as fuzzing our targets<00:01:59.520> without<00:01:59.880> getting<00:02:00.299> ourselves<00:02:00.840> into 00:02:01.190 --> 00:02:01.200 align:start position:0% targets without getting ourselves into 00:02:01.200 --> 00:02:02.569 align:start position:0% targets without getting ourselves into any<00:02:01.500> trouble<00:02:01.799> I<00:02:02.100> know<00:02:02.220> there's<00:02:02.340> a<00:02:02.460> lot<00:02:02.520> of 00:02:02.569 --> 00:02:02.579 align:start position:0% any trouble I know there's a lot of 00:02:02.579 --> 00:02:03.950 align:start position:0% any trouble I know there's a lot of interest<00:02:02.700> in<00:02:02.939> learning<00:02:03.180> how<00:02:03.299> to<00:02:03.479> scan<00:02:03.720> and 00:02:03.950 --> 00:02:03.960 align:start position:0% interest in learning how to scan and 00:02:03.960 --> 00:02:05.330 align:start position:0% interest in learning how to scan and fuzz<00:02:04.259> bug<00:02:04.439> Bounty<00:02:04.860> targets<00:02:05.219> because 00:02:05.330 --> 00:02:05.340 align:start position:0% fuzz bug Bounty targets because 00:02:05.340 --> 00:02:06.830 align:start position:0% fuzz bug Bounty targets because sometimes<00:02:05.700> you'll<00:02:05.939> be<00:02:06.060> reading<00:02:06.299> through<00:02:06.479> a 00:02:06.830 --> 00:02:06.840 align:start position:0% sometimes you'll be reading through a 00:02:06.840 --> 00:02:08.630 align:start position:0% sometimes you'll be reading through a program's<00:02:07.439> rules<00:02:07.740> and<00:02:08.039> it'll<00:02:08.220> specifically 00:02:08.630 --> 00:02:08.640 align:start position:0% program's rules and it'll specifically 00:02:08.640 --> 00:02:10.969 align:start position:0% program's rules and it'll specifically say<00:02:08.880> that<00:02:09.239> there<00:02:09.479> is<00:02:09.660> no<00:02:09.959> scanning<00:02:10.440> allowed 00:02:10.969 --> 00:02:10.979 align:start position:0% say that there is no scanning allowed 00:02:10.979 --> 00:02:12.650 align:start position:0% say that there is no scanning allowed now<00:02:11.459> there's<00:02:11.760> a<00:02:11.940> couple<00:02:12.000> ways<00:02:12.360> to<00:02:12.420> get<00:02:12.540> around 00:02:12.650 --> 00:02:12.660 align:start position:0% now there's a couple ways to get around 00:02:12.660 --> 00:02:14.690 align:start position:0% now there's a couple ways to get around this<00:02:12.900> and<00:02:13.080> if<00:02:13.260> you<00:02:13.440> watch<00:02:13.560> my<00:02:13.920> Showdown<00:02:14.459> video 00:02:14.690 --> 00:02:14.700 align:start position:0% this and if you watch my Showdown video 00:02:14.700 --> 00:02:17.089 align:start position:0% this and if you watch my Showdown video you<00:02:15.000> can<00:02:15.120> actually<00:02:15.239> use<00:02:15.540> Showdown<00:02:16.260> to<00:02:16.500> scan 00:02:17.089 --> 00:02:17.099 align:start position:0% you can actually use Showdown to scan 00:02:17.099 --> 00:02:19.010 align:start position:0% you can actually use Showdown to scan your<00:02:17.400> bug<00:02:17.700> Bounty<00:02:18.120> targets<00:02:18.480> and<00:02:18.780> then<00:02:18.840> you 00:02:19.010 --> 00:02:19.020 align:start position:0% your bug Bounty targets and then you 00:02:19.020 --> 00:02:19.850 align:start position:0% your bug Bounty targets and then you don't<00:02:19.080> have<00:02:19.260> to<00:02:19.319> worry<00:02:19.440> about<00:02:19.560> anything 00:02:19.850 --> 00:02:19.860 align:start position:0% don't have to worry about anything 00:02:19.860 --> 00:02:21.710 align:start position:0% don't have to worry about anything because<00:02:20.220> you're<00:02:20.520> using<00:02:20.819> Showdown<00:02:21.239> and<00:02:21.599> that 00:02:21.710 --> 00:02:21.720 align:start position:0% because you're using Showdown and that 00:02:21.720 --> 00:02:24.050 align:start position:0% because you're using Showdown and that is<00:02:21.900> one<00:02:22.200> way<00:02:22.440> to<00:02:22.739> get<00:02:23.099> around<00:02:23.280> scanning<00:02:23.940> a 00:02:24.050 --> 00:02:24.060 align:start position:0% is one way to get around scanning a 00:02:24.060 --> 00:02:26.030 align:start position:0% is one way to get around scanning a Target<00:02:24.180> and<00:02:24.720> staying<00:02:25.140> in<00:02:25.260> the<00:02:25.379> clear<00:02:25.500> now<00:02:25.860> you 00:02:26.030 --> 00:02:26.040 align:start position:0% Target and staying in the clear now you 00:02:26.040 --> 00:02:28.430 align:start position:0% Target and staying in the clear now you can<00:02:26.099> use<00:02:26.220> nmap<00:02:26.879> and<00:02:27.060> fuzzing<00:02:27.540> tools<00:02:27.900> to<00:02:28.140> do 00:02:28.430 --> 00:02:28.440 align:start position:0% can use nmap and fuzzing tools to do 00:02:28.440 --> 00:02:30.229 align:start position:0% can use nmap and fuzzing tools to do this<00:02:28.620> as<00:02:28.800> well<00:02:28.980> and<00:02:29.580> that's<00:02:29.700> the<00:02:29.879> purpose<00:02:30.120> of 00:02:30.229 --> 00:02:30.239 align:start position:0% this as well and that's the purpose of 00:02:30.239 --> 00:02:31.190 align:start position:0% this as well and that's the purpose of this<00:02:30.360> video<00:02:30.480> so<00:02:30.780> we're<00:02:30.900> going<00:02:30.959> to<00:02:31.020> go<00:02:31.140> ahead 00:02:31.190 --> 00:02:31.200 align:start position:0% this video so we're going to go ahead 00:02:31.200 --> 00:02:32.150 align:start position:0% this video so we're going to go ahead and<00:02:31.319> look<00:02:31.440> at<00:02:31.560> this<00:02:31.680> and<00:02:31.800> I'm<00:02:31.920> going<00:02:32.040> to<00:02:32.099> show 00:02:32.150 --> 00:02:32.160 align:start position:0% and look at this and I'm going to show 00:02:32.160 --> 00:02:33.170 align:start position:0% and look at this and I'm going to show you<00:02:32.220> how<00:02:32.340> to<00:02:32.459> do<00:02:32.520> this<00:02:32.640> without<00:02:32.819> getting 00:02:33.170 --> 00:02:33.180 align:start position:0% you how to do this without getting 00:02:33.180 --> 00:02:35.030 align:start position:0% you how to do this without getting yourself<00:02:33.360> into<00:02:33.720> any<00:02:33.959> hot<00:02:34.200> water<00:02:34.319> and<00:02:34.680> to<00:02:34.920> be 00:02:35.030 --> 00:02:35.040 align:start position:0% yourself into any hot water and to be 00:02:35.040 --> 00:02:36.470 align:start position:0% yourself into any hot water and to be able<00:02:35.099> to<00:02:35.220> scan<00:02:35.400> these<00:02:35.700> targets<00:02:35.940> without<00:02:36.120> any 00:02:36.470 --> 00:02:36.480 align:start position:0% able to scan these targets without any 00:02:36.480 --> 00:02:38.630 align:start position:0% able to scan these targets without any issue<00:02:36.840> before<00:02:37.140> we<00:02:37.379> get<00:02:37.500> going<00:02:37.680> too<00:02:38.040> far<00:02:38.220> I<00:02:38.520> want 00:02:38.630 --> 00:02:38.640 align:start position:0% issue before we get going too far I want 00:02:38.640 --> 00:02:40.130 align:start position:0% issue before we get going too far I want to<00:02:38.700> explain<00:02:38.819> to<00:02:39.060> you<00:02:39.180> why<00:02:39.599> you're<00:02:39.720> not<00:02:39.900> allowed 00:02:40.130 --> 00:02:40.140 align:start position:0% to explain to you why you're not allowed 00:02:40.140 --> 00:02:42.530 align:start position:0% to explain to you why you're not allowed to<00:02:40.319> scan<00:02:40.860> these<00:02:41.340> specific<00:02:41.640> targets<00:02:42.120> and 00:02:42.530 --> 00:02:42.540 align:start position:0% to scan these specific targets and 00:02:42.540 --> 00:02:44.930 align:start position:0% to scan these specific targets and there's<00:02:42.840> really<00:02:43.080> two<00:02:43.379> main<00:02:43.680> reasons<00:02:44.099> one<00:02:44.519> the 00:02:44.930 --> 00:02:44.940 align:start position:0% there's really two main reasons one the 00:02:44.940 --> 00:02:46.729 align:start position:0% there's really two main reasons one the company<00:02:45.180> doesn't<00:02:45.599> want<00:02:45.840> a<00:02:46.140> bunch<00:02:46.319> of<00:02:46.560> bug 00:02:46.729 --> 00:02:46.739 align:start position:0% company doesn't want a bunch of bug 00:02:46.739 --> 00:02:48.589 align:start position:0% company doesn't want a bunch of bug bounty<00:02:47.220> hunters<00:02:47.459> using<00:02:47.760> fuff<00:02:48.120> which<00:02:48.360> is<00:02:48.480> going 00:02:48.589 --> 00:02:48.599 align:start position:0% bounty hunters using fuff which is going 00:02:48.599 --> 00:02:50.330 align:start position:0% bounty hunters using fuff which is going to<00:02:48.660> send<00:02:48.780> several<00:02:49.140> hundred<00:02:49.379> requests<00:02:49.800> per 00:02:50.330 --> 00:02:50.340 align:start position:0% to send several hundred requests per 00:02:50.340 --> 00:02:52.610 align:start position:0% to send several hundred requests per second<00:02:50.580> to<00:02:51.000> their<00:02:51.360> server<00:02:51.660> and<00:02:51.959> have<00:02:52.140> them<00:02:52.319> get 00:02:52.610 --> 00:02:52.620 align:start position:0% second to their server and have them get 00:02:52.620 --> 00:02:54.530 align:start position:0% second to their server and have them get dosed<00:02:53.099> and<00:02:53.220> sometimes<00:02:53.519> if<00:02:53.700> you<00:02:53.819> do<00:02:54.000> this<00:02:54.180> you 00:02:54.530 --> 00:02:54.540 align:start position:0% dosed and sometimes if you do this you 00:02:54.540 --> 00:02:56.630 align:start position:0% dosed and sometimes if you do this you will<00:02:54.720> actually<00:02:55.019> get<00:02:55.560> rate<00:02:55.800> limited<00:02:56.280> or<00:02:56.459> even 00:02:56.630 --> 00:02:56.640 align:start position:0% will actually get rate limited or even 00:02:56.640 --> 00:02:58.490 align:start position:0% will actually get rate limited or even have<00:02:56.819> your<00:02:56.940> IP<00:02:57.239> ban<00:02:57.540> which<00:02:57.780> is<00:02:57.840> why<00:02:58.140> I<00:02:58.379> always 00:02:58.490 --> 00:02:58.500 align:start position:0% have your IP ban which is why I always 00:02:58.500 --> 00:03:00.949 align:start position:0% have your IP ban which is why I always recommend<00:02:58.920> using<00:02:59.340> a<00:02:59.459> VPN<00:02:59.819> in<00:03:00.300> but<00:03:00.660> there<00:03:00.780> is<00:03:00.900> a 00:03:00.949 --> 00:03:00.959 align:start position:0% recommend using a VPN in but there is a 00:03:00.959 --> 00:03:01.910 align:start position:0% recommend using a VPN in but there is a way<00:03:01.019> to<00:03:01.140> go<00:03:01.260> around<00:03:01.319> this<00:03:01.560> and<00:03:01.739> I'm<00:03:01.860> going<00:03:01.920> to 00:03:01.910 --> 00:03:01.920 align:start position:0% way to go around this and I'm going to 00:03:01.920 --> 00:03:03.350 align:start position:0% way to go around this and I'm going to show<00:03:02.099> you<00:03:02.160> that<00:03:02.340> at<00:03:02.640> the<00:03:02.819> end<00:03:02.940> of<00:03:03.060> this<00:03:03.180> video 00:03:03.350 --> 00:03:03.360 align:start position:0% show you that at the end of this video 00:03:03.360 --> 00:03:04.850 align:start position:0% show you that at the end of this video and<00:03:03.660> the<00:03:03.780> second<00:03:03.900> reason<00:03:04.080> a<00:03:04.379> lot<00:03:04.500> of<00:03:04.620> programs 00:03:04.850 --> 00:03:04.860 align:start position:0% and the second reason a lot of programs 00:03:04.860 --> 00:03:05.750 align:start position:0% and the second reason a lot of programs are<00:03:04.980> going<00:03:05.099> to<00:03:05.160> tell<00:03:05.280> you<00:03:05.340> they<00:03:05.459> don't<00:03:05.640> want 00:03:05.750 --> 00:03:05.760 align:start position:0% are going to tell you they don't want 00:03:05.760 --> 00:03:07.309 align:start position:0% are going to tell you they don't want you<00:03:05.879> scanning<00:03:06.239> their<00:03:06.360> network<00:03:06.480> is<00:03:06.840> people 00:03:07.309 --> 00:03:07.319 align:start position:0% you scanning their network is people 00:03:07.319 --> 00:03:09.410 align:start position:0% you scanning their network is people will<00:03:07.560> use<00:03:07.800> vulnerability<00:03:08.459> scanners<00:03:08.940> and<00:03:09.239> this 00:03:09.410 --> 00:03:09.420 align:start position:0% will use vulnerability scanners and this 00:03:09.420 --> 00:03:11.449 align:start position:0% will use vulnerability scanners and this is<00:03:09.599> just<00:03:09.840> really<00:03:10.080> a<00:03:10.319> big<00:03:10.560> No-No<00:03:11.040> don't<00:03:11.280> use 00:03:11.449 --> 00:03:11.459 align:start position:0% is just really a big No-No don't use 00:03:11.459 --> 00:03:13.369 align:start position:0% is just really a big No-No don't use vulnerability<00:03:12.060> scanners<00:03:12.480> recently<00:03:13.080> a 00:03:13.369 --> 00:03:13.379 align:start position:0% vulnerability scanners recently a 00:03:13.379 --> 00:03:15.470 align:start position:0% vulnerability scanners recently a program<00:03:13.680> went<00:03:14.040> live<00:03:14.340> and<00:03:14.819> then<00:03:14.940> they<00:03:15.360> were 00:03:15.470 --> 00:03:15.480 align:start position:0% program went live and then they were 00:03:15.480 --> 00:03:16.729 align:start position:0% program went live and then they were getting<00:03:15.659> scanned<00:03:16.200> so<00:03:16.500> much<00:03:16.560> with 00:03:16.729 --> 00:03:16.739 align:start position:0% getting scanned so much with 00:03:16.739 --> 00:03:18.229 align:start position:0% getting scanned so much with vulnerability<00:03:17.220> scanners<00:03:17.700> that<00:03:18.060> they 00:03:18.229 --> 00:03:18.239 align:start position:0% vulnerability scanners that they 00:03:18.239 --> 00:03:20.030 align:start position:0% vulnerability scanners that they actually<00:03:18.420> removed<00:03:19.080> themselves<00:03:19.379> from<00:03:19.739> the<00:03:19.920> bug 00:03:20.030 --> 00:03:20.040 align:start position:0% actually removed themselves from the bug 00:03:20.040 --> 00:03:21.649 align:start position:0% actually removed themselves from the bug Bounty<00:03:20.580> program<00:03:20.700> so<00:03:21.180> don't<00:03:21.480> use 00:03:21.649 --> 00:03:21.659 align:start position:0% Bounty program so don't use 00:03:21.659 --> 00:03:23.390 align:start position:0% Bounty program so don't use vulnerability<00:03:22.379> scanners<00:03:22.800> these<00:03:23.099> are<00:03:23.159> the<00:03:23.280> two 00:03:23.390 --> 00:03:23.400 align:start position:0% vulnerability scanners these are the two 00:03:23.400 --> 00:03:25.190 align:start position:0% vulnerability scanners these are the two big<00:03:23.580> reasons<00:03:23.940> why<00:03:24.300> a<00:03:24.540> lot<00:03:24.599> of<00:03:24.720> programs<00:03:25.080> will 00:03:25.190 --> 00:03:25.200 align:start position:0% big reasons why a lot of programs will 00:03:25.200 --> 00:03:27.229 align:start position:0% big reasons why a lot of programs will say<00:03:25.379> no<00:03:25.739> scanning<00:03:26.220> and<00:03:26.459> so<00:03:26.580> just<00:03:26.700> be<00:03:26.879> aware<00:03:27.060> of 00:03:27.229 --> 00:03:27.239 align:start position:0% say no scanning and so just be aware of 00:03:27.239 --> 00:03:29.149 align:start position:0% say no scanning and so just be aware of that<00:03:27.360> if<00:03:27.900> you're<00:03:28.019> going<00:03:28.319> to<00:03:28.560> fuzz<00:03:28.980> for 00:03:29.149 --> 00:03:29.159 align:start position:0% that if you're going to fuzz for 00:03:29.159 --> 00:03:31.250 align:start position:0% that if you're going to fuzz for directories<00:03:29.580> make<00:03:29.879> sure<00:03:30.120> to<00:03:30.420> slow<00:03:30.780> down<00:03:31.019> the 00:03:31.250 --> 00:03:31.260 align:start position:0% directories make sure to slow down the 00:03:31.260 --> 00:03:32.270 align:start position:0% directories make sure to slow down the amount<00:03:31.379> of<00:03:31.500> requests<00:03:31.860> which<00:03:31.980> I'm<00:03:32.099> going<00:03:32.220> to 00:03:32.270 --> 00:03:32.280 align:start position:0% amount of requests which I'm going to 00:03:32.280 --> 00:03:33.710 align:start position:0% amount of requests which I'm going to show<00:03:32.400> you<00:03:32.459> how<00:03:32.580> to<00:03:32.700> do<00:03:32.819> and<00:03:33.360> don't<00:03:33.540> use 00:03:33.710 --> 00:03:33.720 align:start position:0% show you how to do and don't use 00:03:33.720 --> 00:03:35.509 align:start position:0% show you how to do and don't use vulnerability<00:03:34.379> scanners<00:03:34.860> now<00:03:35.099> first<00:03:35.220> I<00:03:35.459> want 00:03:35.509 --> 00:03:35.519 align:start position:0% vulnerability scanners now first I want 00:03:35.519 --> 00:03:36.830 align:start position:0% vulnerability scanners now first I want to<00:03:35.640> show<00:03:35.700> you<00:03:35.760> how<00:03:35.940> to<00:03:36.000> use<00:03:36.120> nmap<00:03:36.659> without 00:03:36.830 --> 00:03:36.840 align:start position:0% to show you how to use nmap without 00:03:36.840 --> 00:03:38.809 align:start position:0% to show you how to use nmap without getting<00:03:37.200> yourself<00:03:37.379> into<00:03:37.800> any<00:03:38.159> trouble<00:03:38.340> I've 00:03:38.809 --> 00:03:38.819 align:start position:0% getting yourself into any trouble I've 00:03:38.819 --> 00:03:40.309 align:start position:0% getting yourself into any trouble I've so<00:03:39.060> I've<00:03:39.180> gone<00:03:39.360> ahead<00:03:39.540> and<00:03:39.599> opened<00:03:39.840> up<00:03:39.959> tenant 00:03:40.309 --> 00:03:40.319 align:start position:0% so I've gone ahead and opened up tenant 00:03:40.319 --> 00:03:42.289 align:start position:0% so I've gone ahead and opened up tenant from<00:03:40.500> hack<00:03:40.739> the<00:03:40.920> box<00:03:41.099> here<00:03:41.340> if<00:03:41.640> you<00:03:41.760> follow<00:03:42.120> my 00:03:42.289 --> 00:03:42.299 align:start position:0% from hack the box here if you follow my 00:03:42.299 --> 00:03:44.030 align:start position:0% from hack the box here if you follow my Channel<00:03:42.480> at<00:03:42.720> all<00:03:42.840> you<00:03:43.019> will<00:03:43.140> know<00:03:43.319> this<00:03:43.620> is<00:03:43.799> my 00:03:44.030 --> 00:03:44.040 align:start position:0% Channel at all you will know this is my 00:03:44.040 --> 00:03:47.690 align:start position:0% Channel at all you will know this is my go-to<00:03:44.459> box<00:03:44.819> for<00:03:45.299> web<00:03:45.959> app<00:03:46.200> education<00:03:46.920> and<00:03:47.400> the 00:03:47.690 --> 00:03:47.700 align:start position:0% go-to box for web app education and the 00:03:47.700 --> 00:03:50.149 align:start position:0% go-to box for web app education and the first<00:03:47.879> thing<00:03:48.060> we<00:03:48.299> are<00:03:48.480> going<00:03:48.599> to<00:03:48.720> do<00:03:48.900> is<00:03:49.440> run<00:03:49.799> an 00:03:50.149 --> 00:03:50.159 align:start position:0% first thing we are going to do is run an 00:03:50.159 --> 00:03:53.030 align:start position:0% first thing we are going to do is run an nmap<00:03:50.640> scan<00:03:51.000> so<00:03:51.540> we<00:03:51.900> have<00:03:52.080> opened<00:03:52.560> up<00:03:52.680> our 00:03:53.030 --> 00:03:53.040 align:start position:0% nmap scan so we have opened up our 00:03:53.040 --> 00:03:54.530 align:start position:0% nmap scan so we have opened up our terminal<00:03:53.459> here<00:03:53.700> and<00:03:54.060> you're<00:03:54.299> probably 00:03:54.530 --> 00:03:54.540 align:start position:0% terminal here and you're probably 00:03:54.540 --> 00:03:57.410 align:start position:0% terminal here and you're probably familiar<00:03:55.019> by<00:03:55.200> now<00:03:55.440> within<00:03:56.220> in<00:03:56.459> map<00:03:56.700> scan<00:03:57.120> now 00:03:57.410 --> 00:03:57.420 align:start position:0% familiar by now within in map scan now 00:03:57.420 --> 00:03:59.750 align:start position:0% familiar by now within in map scan now this<00:03:57.720> is<00:03:57.900> the<00:03:58.260> typical<00:03:58.500> nmap<00:03:59.040> scan<00:03:59.340> that<00:03:59.459> I 00:03:59.750 --> 00:03:59.760 align:start position:0% this is the typical nmap scan that I 00:03:59.760 --> 00:04:02.330 align:start position:0% this is the typical nmap scan that I like<00:04:00.239> to<00:04:00.420> run<00:04:00.720> I'm<00:04:01.200> going<00:04:01.379> to<00:04:01.379> change<00:04:01.680> the<00:04:01.980> IP 00:04:02.330 --> 00:04:02.340 align:start position:0% like to run I'm going to change the IP 00:04:02.340 --> 00:04:04.309 align:start position:0% like to run I'm going to change the IP right<00:04:02.580> here<00:04:02.760> so<00:04:03.000> if<00:04:03.239> you<00:04:03.360> would<00:04:03.599> like<00:04:03.720> to<00:04:03.959> jot 00:04:04.309 --> 00:04:04.319 align:start position:0% right here so if you would like to jot 00:04:04.319 --> 00:04:06.410 align:start position:0% right here so if you would like to jot this<00:04:04.500> down<00:04:04.620> this<00:04:04.920> is<00:04:04.980> how<00:04:05.159> I<00:04:05.280> run<00:04:05.519> an<00:04:05.760> nmap<00:04:06.120> scan 00:04:06.410 --> 00:04:06.420 align:start position:0% this down this is how I run an nmap scan 00:04:06.420 --> 00:04:09.289 align:start position:0% this down this is how I run an nmap scan if<00:04:06.900> I'm<00:04:07.080> doing<00:04:07.260> a<00:04:07.560> capture<00:04:07.980> the<00:04:08.159> flag<00:04:08.280> but<00:04:09.000> we 00:04:09.289 --> 00:04:09.299 align:start position:0% if I'm doing a capture the flag but we 00:04:09.299 --> 00:04:10.610 align:start position:0% if I'm doing a capture the flag but we are<00:04:09.420> not<00:04:09.540> doing<00:04:09.720> a<00:04:09.900> capture<00:04:10.200> the<00:04:10.319> flag<00:04:10.439> we're 00:04:10.610 --> 00:04:10.620 align:start position:0% are not doing a capture the flag we're 00:04:10.620 --> 00:04:12.229 align:start position:0% are not doing a capture the flag we're going<00:04:10.739> to<00:04:10.799> be<00:04:10.860> scanning<00:04:11.220> a<00:04:11.519> bug<00:04:11.760> binding 00:04:12.229 --> 00:04:12.239 align:start position:0% going to be scanning a bug binding 00:04:12.239 --> 00:04:14.390 align:start position:0% going to be scanning a bug binding program<00:04:12.420> and<00:04:13.200> and<00:04:13.500> it's<00:04:13.680> going<00:04:13.860> to<00:04:13.980> look<00:04:14.099> a 00:04:14.390 --> 00:04:14.400 align:start position:0% program and and it's going to look a 00:04:14.400 --> 00:04:16.370 align:start position:0% program and and it's going to look a little<00:04:14.519> bit<00:04:14.760> different<00:04:15.239> so<00:04:15.720> we<00:04:15.959> still<00:04:16.139> want 00:04:16.370 --> 00:04:16.380 align:start position:0% little bit different so we still want 00:04:16.380 --> 00:04:18.770 align:start position:0% little bit different so we still want this<00:04:16.620> Dash<00:04:16.979> a<00:04:17.220> we<00:04:17.760> will<00:04:17.880> want<00:04:18.060> a<00:04:18.299> dash<00:04:18.540> capital 00:04:18.770 --> 00:04:18.780 align:start position:0% this Dash a we will want a dash capital 00:04:18.780 --> 00:04:20.810 align:start position:0% this Dash a we will want a dash capital F<00:04:19.139> and<00:04:19.380> this<00:04:19.560> is<00:04:19.680> only<00:04:19.859> going<00:04:20.040> to<00:04:20.160> scan<00:04:20.400> the<00:04:20.639> top 00:04:20.810 --> 00:04:20.820 align:start position:0% F and this is only going to scan the top 00:04:20.820 --> 00:04:22.850 align:start position:0% F and this is only going to scan the top 100<00:04:21.180> ports<00:04:21.780> so<00:04:21.900> the<00:04:22.079> reason<00:04:22.199> I'm<00:04:22.500> telling<00:04:22.800> you 00:04:22.850 --> 00:04:22.860 align:start position:0% 100 ports so the reason I'm telling you 00:04:22.860 --> 00:04:25.189 align:start position:0% 100 ports so the reason I'm telling you to<00:04:23.040> use<00:04:23.220> the<00:04:23.759> dash<00:04:24.000> f<00:04:24.300> is<00:04:24.720> because<00:04:24.840> if<00:04:25.080> you're 00:04:25.189 --> 00:04:25.199 align:start position:0% to use the dash f is because if you're 00:04:25.199 --> 00:04:26.390 align:start position:0% to use the dash f is because if you're new<00:04:25.380> you're<00:04:25.680> probably<00:04:25.860> not<00:04:26.100> going<00:04:26.220> to<00:04:26.280> know 00:04:26.390 --> 00:04:26.400 align:start position:0% new you're probably not going to know 00:04:26.400 --> 00:04:28.909 align:start position:0% new you're probably not going to know which<00:04:26.639> ports<00:04:27.060> you<00:04:27.360> want<00:04:27.600> to<00:04:27.780> look<00:04:27.960> at<00:04:28.080> so<00:04:28.500> I 00:04:28.909 --> 00:04:28.919 align:start position:0% which ports you want to look at so I 00:04:28.919 --> 00:04:31.189 align:start position:0% which ports you want to look at so I have<00:04:29.040> a<00:04:29.160> list<00:04:29.280> of<00:04:29.460> ports<00:04:29.820> that<00:04:30.000> I<00:04:30.360> use<00:04:30.540> when<00:04:31.020> I 00:04:31.189 --> 00:04:31.199 align:start position:0% have a list of ports that I use when I 00:04:31.199 --> 00:04:32.689 align:start position:0% have a list of ports that I use when I run<00:04:31.380> an<00:04:31.560> nmap<00:04:31.919> scan<00:04:32.160> because<00:04:32.280> you<00:04:32.460> don't<00:04:32.580> want 00:04:32.689 --> 00:04:32.699 align:start position:0% run an nmap scan because you don't want 00:04:32.699 --> 00:04:34.850 align:start position:0% run an nmap scan because you don't want to<00:04:32.820> scan<00:04:33.060> all<00:04:33.360> sixty<00:04:33.900> five<00:04:34.199> thousand<00:04:34.560> five 00:04:34.850 --> 00:04:34.860 align:start position:0% to scan all sixty five thousand five 00:04:34.860 --> 00:04:36.770 align:start position:0% to scan all sixty five thousand five hundred<00:04:35.520> and<00:04:35.580> thirty<00:04:36.000> five<00:04:36.060> ports<00:04:36.479> I<00:04:36.660> think 00:04:36.770 --> 00:04:36.780 align:start position:0% hundred and thirty five ports I think 00:04:36.780 --> 00:04:38.390 align:start position:0% hundred and thirty five ports I think that's<00:04:36.900> how<00:04:37.080> many<00:04:37.199> there<00:04:37.440> are<00:04:37.620> you<00:04:38.040> want<00:04:38.220> to 00:04:38.390 --> 00:04:38.400 align:start position:0% that's how many there are you want to 00:04:38.400 --> 00:04:40.969 align:start position:0% that's how many there are you want to scan<00:04:38.639> just<00:04:39.120> a<00:04:39.419> specific<00:04:39.840> number<00:04:40.199> of<00:04:40.440> ports<00:04:40.800> a 00:04:40.969 --> 00:04:40.979 align:start position:0% scan just a specific number of ports a 00:04:40.979 --> 00:04:42.170 align:start position:0% scan just a specific number of ports a lot<00:04:41.100> of<00:04:41.220> networks<00:04:41.580> are<00:04:41.699> not<00:04:41.880> going<00:04:42.000> to<00:04:42.060> want 00:04:42.170 --> 00:04:42.180 align:start position:0% lot of networks are not going to want 00:04:42.180 --> 00:04:43.909 align:start position:0% lot of networks are not going to want you<00:04:42.360> going<00:04:42.540> out<00:04:42.720> and<00:04:42.960> scanning<00:04:43.380> their<00:04:43.560> entire 00:04:43.909 --> 00:04:43.919 align:start position:0% you going out and scanning their entire 00:04:43.919 --> 00:04:46.310 align:start position:0% you going out and scanning their entire network<00:04:44.220> but<00:04:44.880> it's<00:04:45.120> okay<00:04:45.360> to<00:04:45.600> go<00:04:45.720> out<00:04:45.840> and<00:04:46.020> scan 00:04:46.310 --> 00:04:46.320 align:start position:0% network but it's okay to go out and scan 00:04:46.320 --> 00:04:49.070 align:start position:0% network but it's okay to go out and scan the<00:04:46.860> top<00:04:47.160> 100<00:04:47.460> ports<00:04:48.000> they're<00:04:48.540> probably<00:04:48.780> not 00:04:49.070 --> 00:04:49.080 align:start position:0% the top 100 ports they're probably not 00:04:49.080 --> 00:04:50.810 align:start position:0% the top 100 ports they're probably not even<00:04:49.320> going<00:04:49.680> to<00:04:49.860> notice<00:04:50.220> and<00:04:50.400> I'll<00:04:50.580> show<00:04:50.699> you 00:04:50.810 --> 00:04:50.820 align:start position:0% even going to notice and I'll show you 00:04:50.820 --> 00:04:52.189 align:start position:0% even going to notice and I'll show you how<00:04:51.000> to<00:04:51.120> make<00:04:51.300> it<00:04:51.479> so<00:04:51.660> that<00:04:51.780> they're<00:04:51.900> not<00:04:52.020> going 00:04:52.189 --> 00:04:52.199 align:start position:0% how to make it so that they're not going 00:04:52.199 --> 00:04:53.570 align:start position:0% how to make it so that they're not going to<00:04:52.259> notice<00:04:52.560> and<00:04:52.919> you're<00:04:53.040> not<00:04:53.220> going<00:04:53.340> to<00:04:53.460> cause 00:04:53.570 --> 00:04:53.580 align:start position:0% to notice and you're not going to cause 00:04:53.580 --> 00:04:55.129 align:start position:0% to notice and you're not going to cause any<00:04:53.759> kind<00:04:53.940> of<00:04:54.060> intrusion<00:04:54.479> and<00:04:54.780> they're<00:04:55.020> not 00:04:55.129 --> 00:04:55.139 align:start position:0% any kind of intrusion and they're not 00:04:55.139 --> 00:04:57.170 align:start position:0% any kind of intrusion and they're not going<00:04:55.259> to<00:04:55.380> care<00:04:55.500> so<00:04:55.919> we<00:04:56.040> want<00:04:56.160> to<00:04:56.340> run<00:04:56.460> the<00:04:56.820> dash 00:04:57.170 --> 00:04:57.180 align:start position:0% going to care so we want to run the dash 00:04:57.180 --> 00:04:59.689 align:start position:0% going to care so we want to run the dash f<00:04:57.540> for<00:04:58.440> our<00:04:58.740> ports<00:04:59.160> and<00:04:59.340> then<00:04:59.460> you're<00:04:59.580> going 00:04:59.689 --> 00:04:59.699 align:start position:0% f for our ports and then you're going 00:04:59.699 --> 00:05:02.689 align:start position:0% f for our ports and then you're going want<00:05:00.240> to<00:05:00.300> run<00:05:00.419> a<00:05:00.720> dash<00:05:00.960> T<00:05:01.259> and<00:05:01.560> then<00:05:01.740> a<00:05:01.979> one<00:05:02.220> or<00:05:02.520> a 00:05:02.689 --> 00:05:02.699 align:start position:0% want to run a dash T and then a one or a 00:05:02.699 --> 00:05:04.249 align:start position:0% want to run a dash T and then a one or a two<00:05:02.820> this<00:05:03.180> is<00:05:03.300> going<00:05:03.419> to<00:05:03.600> really<00:05:03.780> slow<00:05:04.020> down 00:05:04.249 --> 00:05:04.259 align:start position:0% two this is going to really slow down 00:05:04.259 --> 00:05:06.830 align:start position:0% two this is going to really slow down your<00:05:04.500> network<00:05:04.620> scan<00:05:04.979> I<00:05:05.520> think<00:05:05.639> that<00:05:06.120> nmap<00:05:06.600> runs 00:05:06.830 --> 00:05:06.840 align:start position:0% your network scan I think that nmap runs 00:05:06.840 --> 00:05:09.950 align:start position:0% your network scan I think that nmap runs on<00:05:07.020> a<00:05:07.139> T3<00:05:07.680> automatically<00:05:08.460> and<00:05:09.060> if<00:05:09.419> I'm<00:05:09.600> in<00:05:09.840> a 00:05:09.950 --> 00:05:09.960 align:start position:0% on a T3 automatically and if I'm in a 00:05:09.960 --> 00:05:11.090 align:start position:0% on a T3 automatically and if I'm in a hurry<00:05:10.139> and<00:05:10.199> I<00:05:10.380> just<00:05:10.440> want<00:05:10.560> some<00:05:10.680> ports<00:05:11.040> to 00:05:11.090 --> 00:05:11.100 align:start position:0% hurry and I just want some ports to 00:05:11.100 --> 00:05:13.070 align:start position:0% hurry and I just want some ports to shoot<00:05:11.220> at<00:05:11.400> if<00:05:11.520> I'm<00:05:11.639> in<00:05:11.759> a<00:05:11.880> CTF<00:05:12.240> I'll<00:05:12.419> run<00:05:12.600> as<00:05:12.720> T5 00:05:13.070 --> 00:05:13.080 align:start position:0% shoot at if I'm in a CTF I'll run as T5 00:05:13.080 --> 00:05:15.050 align:start position:0% shoot at if I'm in a CTF I'll run as T5 that's<00:05:13.440> as<00:05:13.620> fast<00:05:13.800> as<00:05:13.979> you<00:05:14.100> can<00:05:14.220> go<00:05:14.340> but<00:05:14.820> if<00:05:14.940> you 00:05:15.050 --> 00:05:15.060 align:start position:0% that's as fast as you can go but if you 00:05:15.060 --> 00:05:17.210 align:start position:0% that's as fast as you can go but if you run<00:05:15.180> a<00:05:15.360> T5<00:05:15.660> in<00:05:16.080> a<00:05:16.259> CTF<00:05:16.620> you<00:05:16.800> can<00:05:16.919> actually<00:05:16.979> miss 00:05:17.210 --> 00:05:17.220 align:start position:0% run a T5 in a CTF you can actually miss 00:05:17.220 --> 00:05:18.650 align:start position:0% run a T5 in a CTF you can actually miss some<00:05:17.400> ports<00:05:17.699> so<00:05:17.820> if<00:05:18.000> you're<00:05:18.180> really<00:05:18.300> nervous 00:05:18.650 --> 00:05:18.660 align:start position:0% some ports so if you're really nervous 00:05:18.660 --> 00:05:20.330 align:start position:0% some ports so if you're really nervous about<00:05:18.780> running<00:05:19.380> any<00:05:19.680> kind<00:05:19.800> of<00:05:19.919> scan<00:05:20.160> you<00:05:20.220> can 00:05:20.330 --> 00:05:20.340 align:start position:0% about running any kind of scan you can 00:05:20.340 --> 00:05:21.890 align:start position:0% about running any kind of scan you can go<00:05:20.400> ahead<00:05:20.520> and<00:05:20.580> run<00:05:20.759> a<00:05:20.940> T1<00:05:21.300> and<00:05:21.660> they're<00:05:21.780> not 00:05:21.890 --> 00:05:21.900 align:start position:0% go ahead and run a T1 and they're not 00:05:21.900 --> 00:05:23.029 align:start position:0% go ahead and run a T1 and they're not going<00:05:22.080> to<00:05:22.139> notice<00:05:22.380> that<00:05:22.560> you're<00:05:22.740> scanning 00:05:23.029 --> 00:05:23.039 align:start position:0% going to notice that you're scanning 00:05:23.039 --> 00:05:24.529 align:start position:0% going to notice that you're scanning their<00:05:23.160> ports<00:05:23.460> this<00:05:23.580> is<00:05:23.699> going<00:05:23.880> to<00:05:24.000> really<00:05:24.300> slow 00:05:24.529 --> 00:05:24.539 align:start position:0% their ports this is going to really slow 00:05:24.539 --> 00:05:26.689 align:start position:0% their ports this is going to really slow down<00:05:24.780> your<00:05:25.020> nmap<00:05:25.380> scan<00:05:25.620> and<00:05:26.039> then<00:05:26.160> this<00:05:26.460> Dash 00:05:26.689 --> 00:05:26.699 align:start position:0% down your nmap scan and then this Dash 00:05:26.699 --> 00:05:28.129 align:start position:0% down your nmap scan and then this Dash view<00:05:27.000> right<00:05:27.180> here<00:05:27.300> will<00:05:27.539> tell<00:05:27.660> you<00:05:27.780> the<00:05:27.960> open 00:05:28.129 --> 00:05:28.139 align:start position:0% view right here will tell you the open 00:05:28.139 --> 00:05:30.409 align:start position:0% view right here will tell you the open ports<00:05:28.620> as<00:05:28.800> it<00:05:29.039> hits<00:05:29.220> them<00:05:29.460> so<00:05:30.000> this<00:05:30.240> is<00:05:30.300> going 00:05:30.409 --> 00:05:30.419 align:start position:0% ports as it hits them so this is going 00:05:30.419 --> 00:05:32.210 align:start position:0% ports as it hits them so this is going to<00:05:30.600> run<00:05:30.660> a<00:05:30.960> really<00:05:31.080> slow<00:05:31.259> scan<00:05:31.680> on<00:05:31.800> the<00:05:31.919> top<00:05:32.039> 100 00:05:32.210 --> 00:05:32.220 align:start position:0% to run a really slow scan on the top 100 00:05:32.220 --> 00:05:34.189 align:start position:0% to run a really slow scan on the top 100 ports<00:05:32.699> and<00:05:32.880> nobody's<00:05:33.360> going<00:05:33.479> to<00:05:33.539> notice<00:05:33.840> so 00:05:34.189 --> 00:05:34.199 align:start position:0% ports and nobody's going to notice so 00:05:34.199 --> 00:05:35.689 align:start position:0% ports and nobody's going to notice so you<00:05:34.320> can<00:05:34.440> go<00:05:34.500> ahead<00:05:34.620> and<00:05:34.740> run<00:05:34.919> this<00:05:35.100> and<00:05:35.460> it 00:05:35.689 --> 00:05:35.699 align:start position:0% you can go ahead and run this and it 00:05:35.699 --> 00:05:37.310 align:start position:0% you can go ahead and run this and it says<00:05:35.940> that<00:05:36.000> there<00:05:36.180> are<00:05:36.300> two<00:05:36.360> ports<00:05:36.720> and<00:05:37.139> it's 00:05:37.310 --> 00:05:37.320 align:start position:0% says that there are two ports and it's 00:05:37.320 --> 00:05:39.710 align:start position:0% says that there are two ports and it's going<00:05:37.500> to<00:05:37.620> pop<00:05:37.740> down<00:05:38.039> with<00:05:38.460> the<00:05:38.639> ports<00:05:39.000> as<00:05:39.419> it 00:05:39.710 --> 00:05:39.720 align:start position:0% going to pop down with the ports as it 00:05:39.720 --> 00:05:41.029 align:start position:0% going to pop down with the ports as it hits<00:05:39.900> them<00:05:40.139> and<00:05:40.380> So<00:05:40.500> eventually<00:05:40.800> you're<00:05:40.919> going 00:05:41.029 --> 00:05:41.039 align:start position:0% hits them and So eventually you're going 00:05:41.039 --> 00:05:42.529 align:start position:0% hits them and So eventually you're going to<00:05:41.160> see<00:05:41.220> Port<00:05:41.460> 80<00:05:41.639> pop<00:05:41.940> up<00:05:42.060> and<00:05:42.180> I'm<00:05:42.300> not<00:05:42.419> really 00:05:42.529 --> 00:05:42.539 align:start position:0% to see Port 80 pop up and I'm not really 00:05:42.539 --> 00:05:44.930 align:start position:0% to see Port 80 pop up and I'm not really sure<00:05:42.660> what<00:05:42.960> other<00:05:43.080> ports<00:05:43.500> are<00:05:44.160> open<00:05:44.400> on<00:05:44.820> this 00:05:44.930 --> 00:05:44.940 align:start position:0% sure what other ports are open on this 00:05:44.940 --> 00:05:47.150 align:start position:0% sure what other ports are open on this program<00:05:45.180> but<00:05:45.600> this<00:05:45.780> is<00:05:45.900> how<00:05:46.199> I<00:05:46.440> would<00:05:46.560> run<00:05:46.800> an 00:05:47.150 --> 00:05:47.160 align:start position:0% program but this is how I would run an 00:05:47.160 --> 00:05:49.129 align:start position:0% program but this is how I would run an nmap<00:05:47.580> scan<00:05:47.880> and<00:05:48.240> so<00:05:48.360> you<00:05:48.479> can<00:05:48.600> see<00:05:48.720> right<00:05:49.020> here 00:05:49.129 --> 00:05:49.139 align:start position:0% nmap scan and so you can see right here 00:05:49.139 --> 00:05:51.650 align:start position:0% nmap scan and so you can see right here it<00:05:49.380> tells<00:05:49.680> us<00:05:49.800> that<00:05:50.280> it's<00:05:50.520> scanning<00:05:51.000> the<00:05:51.360> top 00:05:51.650 --> 00:05:51.660 align:start position:0% it tells us that it's scanning the top 00:05:51.660 --> 00:05:53.810 align:start position:0% it tells us that it's scanning the top 100<00:05:52.080> ports<00:05:52.800> alright<00:05:53.039> so<00:05:53.160> I<00:05:53.280> decided<00:05:53.580> to<00:05:53.699> go 00:05:53.810 --> 00:05:53.820 align:start position:0% 100 ports alright so I decided to go 00:05:53.820 --> 00:05:55.790 align:start position:0% 100 ports alright so I decided to go ahead<00:05:53.940> and<00:05:54.060> add<00:05:54.300> in<00:05:54.479> this<00:05:54.720> nmap<00:05:55.320> network 00:05:55.790 --> 00:05:55.800 align:start position:0% ahead and add in this nmap network 00:05:55.800 --> 00:05:57.770 align:start position:0% ahead and add in this nmap network scanning<00:05:56.340> legal<00:05:56.759> issues<00:05:57.120> page<00:05:57.360> so<00:05:57.539> if<00:05:57.660> you 00:05:57.770 --> 00:05:57.780 align:start position:0% scanning legal issues page so if you 00:05:57.780 --> 00:06:00.110 align:start position:0% scanning legal issues page so if you have<00:05:57.900> any<00:05:58.080> questions<00:05:58.320> about<00:05:59.039> using<00:05:59.400> in<00:05:59.699> up 00:06:00.110 --> 00:06:00.120 align:start position:0% have any questions about using in up 00:06:00.120 --> 00:06:02.990 align:start position:0% have any questions about using in up legally<00:06:00.660> on<00:06:01.380> your<00:06:01.979> specific<00:06:02.280> targets<00:06:02.759> and 00:06:02.990 --> 00:06:03.000 align:start position:0% legally on your specific targets and 00:06:03.000 --> 00:06:04.249 align:start position:0% legally on your specific targets and you're<00:06:03.240> still<00:06:03.419> worried<00:06:03.780> about<00:06:03.840> it<00:06:04.020> you<00:06:04.139> can 00:06:04.249 --> 00:06:04.259 align:start position:0% you're still worried about it you can 00:06:04.259 --> 00:06:06.529 align:start position:0% you're still worried about it you can come<00:06:04.440> and<00:06:04.800> read<00:06:05.220> this<00:06:05.820> right<00:06:06.060> here<00:06:06.180> and<00:06:06.419> it's 00:06:06.529 --> 00:06:06.539 align:start position:0% come and read this right here and it's 00:06:06.539 --> 00:06:08.150 align:start position:0% come and read this right here and it's going<00:06:06.720> to<00:06:06.840> give<00:06:06.900> you<00:06:07.020> a<00:06:07.320> kind<00:06:07.560> of<00:06:07.740> the 00:06:08.150 --> 00:06:08.160 align:start position:0% going to give you a kind of the 00:06:08.160 --> 00:06:10.430 align:start position:0% going to give you a kind of the legalities<00:06:08.880> of<00:06:09.300> using<00:06:09.720> on<00:06:10.139> different 00:06:10.430 --> 00:06:10.440 align:start position:0% legalities of using on different 00:06:10.440 --> 00:06:13.909 align:start position:0% legalities of using on different networks<00:06:10.979> I<00:06:11.520> am<00:06:11.820> not<00:06:12.180> a<00:06:12.419> lawyer<00:06:12.720> so<00:06:13.320> I<00:06:13.560> decided 00:06:13.909 --> 00:06:13.919 align:start position:0% networks I am not a lawyer so I decided 00:06:13.919 --> 00:06:15.770 align:start position:0% networks I am not a lawyer so I decided to<00:06:14.039> go<00:06:14.340> ahead<00:06:14.460> and<00:06:14.580> add<00:06:14.820> this<00:06:15.120> disclaimer<00:06:15.600> in 00:06:15.770 --> 00:06:15.780 align:start position:0% to go ahead and add this disclaimer in 00:06:15.780 --> 00:06:17.570 align:start position:0% to go ahead and add this disclaimer in there<00:06:15.960> that<00:06:16.440> you<00:06:16.680> are<00:06:16.800> using<00:06:17.160> this<00:06:17.280> at<00:06:17.460> your 00:06:17.570 --> 00:06:17.580 align:start position:0% there that you are using this at your 00:06:17.580 --> 00:06:19.790 align:start position:0% there that you are using this at your own<00:06:17.699> risk<00:06:18.000> and<00:06:18.300> you<00:06:18.539> should<00:06:18.720> check<00:06:19.139> with<00:06:19.560> the 00:06:19.790 --> 00:06:19.800 align:start position:0% own risk and you should check with the 00:06:19.800 --> 00:06:21.890 align:start position:0% own risk and you should check with the laws<00:06:20.220> in<00:06:20.400> your<00:06:20.580> specific<00:06:20.820> State<00:06:21.120> on<00:06:21.600> Port 00:06:21.890 --> 00:06:21.900 align:start position:0% laws in your specific State on Port 00:06:21.900 --> 00:06:24.529 align:start position:0% laws in your specific State on Port scanning<00:06:22.440> so<00:06:22.740> this<00:06:23.160> is<00:06:23.340> how<00:06:23.639> I<00:06:23.880> would<00:06:24.060> run<00:06:24.300> an 00:06:24.529 --> 00:06:24.539 align:start position:0% scanning so this is how I would run an 00:06:24.539 --> 00:06:26.570 align:start position:0% scanning so this is how I would run an nmap<00:06:24.900> scan<00:06:25.139> if<00:06:25.319> I'm<00:06:25.500> running<00:06:25.680> one<00:06:25.919> on<00:06:26.160> a<00:06:26.340> bug 00:06:26.570 --> 00:06:26.580 align:start position:0% nmap scan if I'm running one on a bug 00:06:26.580 --> 00:06:28.309 align:start position:0% nmap scan if I'm running one on a bug bunny<00:06:26.819> program<00:06:27.180> this<00:06:27.600> is<00:06:27.660> going<00:06:27.780> to<00:06:27.900> be<00:06:28.020> a 00:06:28.309 --> 00:06:28.319 align:start position:0% bunny program this is going to be a 00:06:28.319 --> 00:06:30.830 align:start position:0% bunny program this is going to be a really<00:06:28.440> safe<00:06:28.800> scan<00:06:29.280> to<00:06:29.880> run<00:06:30.180> and<00:06:30.539> it's<00:06:30.660> going 00:06:30.830 --> 00:06:30.840 align:start position:0% really safe scan to run and it's going 00:06:30.840 --> 00:06:32.150 align:start position:0% really safe scan to run and it's going to<00:06:30.900> tell<00:06:31.080> you<00:06:31.199> the<00:06:31.380> information<00:06:31.560> that<00:06:31.979> you 00:06:32.150 --> 00:06:32.160 align:start position:0% to tell you the information that you 00:06:32.160 --> 00:06:34.070 align:start position:0% to tell you the information that you want<00:06:32.280> from<00:06:32.699> these<00:06:33.060> specific<00:06:33.360> ports<00:06:33.780> which 00:06:34.070 --> 00:06:34.080 align:start position:0% want from these specific ports which 00:06:34.080 --> 00:06:35.689 align:start position:0% want from these specific ports which ports<00:06:34.440> are<00:06:34.560> open<00:06:34.680> what<00:06:35.039> versions<00:06:35.340> are<00:06:35.520> running 00:06:35.689 --> 00:06:35.699 align:start position:0% ports are open what versions are running 00:06:35.699 --> 00:06:38.029 align:start position:0% ports are open what versions are running on<00:06:36.240> your<00:06:36.419> target<00:06:36.780> so<00:06:37.259> you<00:06:37.380> can<00:06:37.500> go<00:06:37.620> ahead<00:06:37.800> and 00:06:38.029 --> 00:06:38.039 align:start position:0% on your target so you can go ahead and 00:06:38.039 --> 00:06:40.309 align:start position:0% on your target so you can go ahead and play<00:06:38.280> around<00:06:38.460> within<00:06:38.880> map<00:06:39.060> this<00:06:39.539> is<00:06:39.720> how<00:06:40.020> I<00:06:40.199> do 00:06:40.309 --> 00:06:40.319 align:start position:0% play around within map this is how I do 00:06:40.319 --> 00:06:41.570 align:start position:0% play around within map this is how I do it<00:06:40.440> though<00:06:40.560> and<00:06:40.800> I<00:06:40.919> want<00:06:41.100> to<00:06:41.160> show<00:06:41.280> you<00:06:41.340> how<00:06:41.460> to 00:06:41.570 --> 00:06:41.580 align:start position:0% it though and I want to show you how to 00:06:41.580 --> 00:06:44.330 align:start position:0% it though and I want to show you how to fuzz<00:06:42.120> for<00:06:42.240> directories<00:06:42.720> in<00:06:43.440> a<00:06:43.740> safe<00:06:43.919> Manner 00:06:44.330 --> 00:06:44.340 align:start position:0% fuzz for directories in a safe Manner 00:06:44.340 --> 00:06:45.590 align:start position:0% fuzz for directories in a safe Manner and<00:06:44.580> you<00:06:44.699> may<00:06:44.819> still<00:06:45.000> end<00:06:45.180> up<00:06:45.300> getting<00:06:45.419> rate 00:06:45.590 --> 00:06:45.600 align:start position:0% and you may still end up getting rate 00:06:45.600 --> 00:06:47.270 align:start position:0% and you may still end up getting rate limited<00:06:46.020> which<00:06:46.199> is<00:06:46.319> fine<00:06:46.500> especially<00:06:46.979> if<00:06:47.100> you 00:06:47.270 --> 00:06:47.280 align:start position:0% limited which is fine especially if you 00:06:47.280 --> 00:06:49.610 align:start position:0% limited which is fine especially if you have<00:06:47.340> VPN<00:06:47.819> you<00:06:48.060> can<00:06:48.120> just<00:06:48.240> switch<00:06:48.419> your<00:06:48.720> VPN<00:06:49.259> so 00:06:49.610 --> 00:06:49.620 align:start position:0% have VPN you can just switch your VPN so 00:06:49.620 --> 00:06:51.290 align:start position:0% have VPN you can just switch your VPN so we're<00:06:49.740> going<00:06:49.860> to<00:06:49.919> go<00:06:50.039> ahead<00:06:50.220> and<00:06:50.400> run<00:06:50.580> F<00:06:51.000> now 00:06:51.290 --> 00:06:51.300 align:start position:0% we're going to go ahead and run F now 00:06:51.300 --> 00:06:53.990 align:start position:0% we're going to go ahead and run F now and<00:06:51.720> this<00:06:52.020> is<00:06:52.199> the<00:06:52.560> Syntax<00:06:52.979> for<00:06:53.220> fuff<00:06:53.699> I'm 00:06:53.990 --> 00:06:54.000 align:start position:0% and this is the Syntax for fuff I'm 00:06:54.000 --> 00:06:55.730 align:start position:0% and this is the Syntax for fuff I'm going<00:06:54.180> to<00:06:54.300> show<00:06:54.419> you<00:06:54.539> this<00:06:54.780> with<00:06:55.259> this<00:06:55.500> a 00:06:55.730 --> 00:06:55.740 align:start position:0% going to show you this with this a 00:06:55.740 --> 00:06:57.050 align:start position:0% going to show you this with this a common<00:06:55.860> word<00:06:56.160> list<00:06:56.340> right<00:06:56.639> here<00:06:56.759> and<00:06:56.940> then 00:06:57.050 --> 00:06:57.060 align:start position:0% common word list right here and then 00:06:57.060 --> 00:06:58.909 align:start position:0% common word list right here and then we'll<00:06:57.180> go<00:06:57.360> ahead<00:06:57.539> and<00:06:57.780> download<00:06:58.080> seclist<00:06:58.680> and 00:06:58.909 --> 00:06:58.919 align:start position:0% we'll go ahead and download seclist and 00:06:58.919 --> 00:07:00.950 align:start position:0% we'll go ahead and download seclist and you<00:06:59.100> can<00:06:59.160> see<00:06:59.280> better<00:06:59.639> are<00:07:00.060> wordless<00:07:00.479> than 00:07:00.950 --> 00:07:00.960 align:start position:0% you can see better are wordless than 00:07:00.960 --> 00:07:03.770 align:start position:0% you can see better are wordless than what<00:07:01.139> is<00:07:01.380> default<00:07:01.979> on<00:07:02.280> the<00:07:02.460> Kali<00:07:02.880> machine<00:07:03.180> we 00:07:03.770 --> 00:07:03.780 align:start position:0% what is default on the Kali machine we 00:07:03.780 --> 00:07:05.870 align:start position:0% what is default on the Kali machine we can<00:07:03.900> actually<00:07:04.020> see<00:07:04.440> what<00:07:04.740> we<00:07:04.979> have<00:07:05.160> as<00:07:05.520> options 00:07:05.870 --> 00:07:05.880 align:start position:0% can actually see what we have as options 00:07:05.880 --> 00:07:08.510 align:start position:0% can actually see what we have as options here<00:07:06.120> and<00:07:06.419> you'll<00:07:06.660> see<00:07:06.840> that<00:07:07.199> I'm<00:07:07.380> using<00:07:07.800> the 00:07:08.510 --> 00:07:08.520 align:start position:0% here and you'll see that I'm using the 00:07:08.520 --> 00:07:11.749 align:start position:0% here and you'll see that I'm using the FC<00:07:08.940> to<00:07:09.600> filter<00:07:10.440> out<00:07:10.740> specific<00:07:11.100> codes<00:07:11.340> that<00:07:11.639> I 00:07:11.749 --> 00:07:11.759 align:start position:0% FC to filter out specific codes that I 00:07:11.759 --> 00:07:13.249 align:start position:0% FC to filter out specific codes that I don't<00:07:11.819> want<00:07:11.940> to<00:07:12.060> see<00:07:12.120> and<00:07:12.419> I<00:07:12.539> think<00:07:12.660> I<00:07:12.840> had<00:07:13.020> a 00:07:13.249 --> 00:07:13.259 align:start position:0% don't want to see and I think I had a 00:07:13.259 --> 00:07:16.189 align:start position:0% don't want to see and I think I had a 402<00:07:13.919> on<00:07:14.580> here<00:07:14.759> a<00:07:15.000> 403<00:07:15.479> I<00:07:15.720> don't<00:07:15.900> want<00:07:16.020> to<00:07:16.080> see 00:07:16.189 --> 00:07:16.199 align:start position:0% 402 on here a 403 I don't want to see 00:07:16.199 --> 00:07:18.830 align:start position:0% 402 on here a 403 I don't want to see the<00:07:16.380> 403s<00:07:16.979> but<00:07:17.280> you<00:07:17.580> can<00:07:17.759> leave<00:07:18.300> those<00:07:18.479> in<00:07:18.660> if 00:07:18.830 --> 00:07:18.840 align:start position:0% the 403s but you can leave those in if 00:07:18.840 --> 00:07:20.930 align:start position:0% the 403s but you can leave those in if you<00:07:18.960> want<00:07:19.139> and<00:07:19.680> then<00:07:19.800> you<00:07:20.039> can<00:07:20.160> filter<00:07:20.400> with 00:07:20.930 --> 00:07:20.940 align:start position:0% you want and then you can filter with 00:07:20.940 --> 00:07:23.809 align:start position:0% you want and then you can filter with other<00:07:21.419> ways<00:07:21.900> but<00:07:22.199> we're<00:07:22.380> looking<00:07:22.620> for<00:07:23.160> that 00:07:23.809 --> 00:07:23.819 align:start position:0% other ways but we're looking for that 00:07:23.819 --> 00:07:26.450 align:start position:0% other ways but we're looking for that Dash<00:07:24.479> p<00:07:24.840> and<00:07:25.319> it<00:07:25.500> is<00:07:25.620> right<00:07:26.039> here<00:07:26.160> and<00:07:26.340> it's 00:07:26.450 --> 00:07:26.460 align:start position:0% Dash p and it is right here and it's 00:07:26.460 --> 00:07:29.330 align:start position:0% Dash p and it is right here and it's going<00:07:26.639> to<00:07:26.759> tell<00:07:26.880> you<00:07:27.060> how<00:07:27.780> to<00:07:28.080> delay<00:07:28.680> your 00:07:29.330 --> 00:07:29.340 align:start position:0% going to tell you how to delay your 00:07:29.340 --> 00:07:31.670 align:start position:0% going to tell you how to delay your requests<00:07:29.880> and<00:07:30.240> you<00:07:30.419> can<00:07:30.539> slow<00:07:30.720> them<00:07:30.960> down<00:07:31.199> by 00:07:31.670 --> 00:07:31.680 align:start position:0% requests and you can slow them down by 00:07:31.680 --> 00:07:33.770 align:start position:0% requests and you can slow them down by however<00:07:32.280> much<00:07:32.460> you<00:07:32.639> want<00:07:32.819> from<00:07:33.120> anywhere<00:07:33.539> from 00:07:33.770 --> 00:07:33.780 align:start position:0% however much you want from anywhere from 00:07:33.780 --> 00:07:36.110 align:start position:0% however much you want from anywhere from 0.1<00:07:34.259> seconds<00:07:34.440> to<00:07:34.800> two<00:07:35.340> seconds<00:07:35.580> in<00:07:36.000> between 00:07:36.110 --> 00:07:36.120 align:start position:0% 0.1 seconds to two seconds in between 00:07:36.120 --> 00:07:38.629 align:start position:0% 0.1 seconds to two seconds in between requests<00:07:36.900> okay<00:07:37.199> so<00:07:37.560> we<00:07:37.740> have<00:07:37.919> this<00:07:38.220> request 00:07:38.629 --> 00:07:38.639 align:start position:0% requests okay so we have this request 00:07:38.639 --> 00:07:40.969 align:start position:0% requests okay so we have this request here<00:07:38.940> and<00:07:39.240> let's<00:07:39.419> say<00:07:39.599> we<00:07:40.020> really<00:07:40.319> want<00:07:40.680> to 00:07:40.969 --> 00:07:40.979 align:start position:0% here and let's say we really want to 00:07:40.979 --> 00:07:43.850 align:start position:0% here and let's say we really want to take<00:07:41.580> our<00:07:41.940> fuzzing<00:07:42.479> really<00:07:42.780> slow<00:07:43.020> you<00:07:43.560> can<00:07:43.680> run 00:07:43.850 --> 00:07:43.860 align:start position:0% take our fuzzing really slow you can run 00:07:43.860 --> 00:07:46.309 align:start position:0% take our fuzzing really slow you can run this<00:07:44.039> with<00:07:44.400> a<00:07:44.759> two<00:07:44.940> second<00:07:45.180> delay<00:07:45.660> or<00:07:45.960> a<00:07:46.139> one 00:07:46.309 --> 00:07:46.319 align:start position:0% this with a two second delay or a one 00:07:46.319 --> 00:07:48.950 align:start position:0% this with a two second delay or a one second<00:07:46.500> delay<00:07:46.919> in<00:07:47.160> between<00:07:47.280> requests<00:07:48.000> we 00:07:48.950 --> 00:07:48.960 align:start position:0% second delay in between requests we 00:07:48.960 --> 00:07:51.589 align:start position:0% second delay in between requests we don't<00:07:49.080> really<00:07:49.259> need<00:07:49.560> to<00:07:49.860> filter<00:07:50.220> out<00:07:50.699> by<00:07:51.240> the 00:07:51.589 --> 00:07:51.599 align:start position:0% don't really need to filter out by the 00:07:51.599 --> 00:07:53.570 align:start position:0% don't really need to filter out by the not<00:07:51.840> founds<00:07:52.380> and<00:07:52.860> then<00:07:52.919> we're<00:07:53.099> going<00:07:53.220> to<00:07:53.400> run 00:07:53.570 --> 00:07:53.580 align:start position:0% not founds and then we're going to run 00:07:53.580 --> 00:07:55.790 align:start position:0% not founds and then we're going to run our<00:07:54.060> word<00:07:54.300> list<00:07:54.539> and<00:07:54.840> we're<00:07:54.960> going<00:07:55.080> to<00:07:55.199> run<00:07:55.319> the 00:07:55.790 --> 00:07:55.800 align:start position:0% our word list and we're going to run the 00:07:55.800 --> 00:07:58.670 align:start position:0% our word list and we're going to run the common<00:07:56.039> word<00:07:56.340> List<00:07:56.639> the<00:07:57.360> common<00:07:57.680> wordless.txt 00:07:58.670 --> 00:07:58.680 align:start position:0% common word List the common wordless.txt 00:07:58.680 --> 00:08:01.129 align:start position:0% common word List the common wordless.txt so<00:07:59.280> if<00:07:59.400> you<00:07:59.580> want<00:08:00.120> to<00:08:00.240> you<00:08:00.479> can<00:08:00.599> go<00:08:00.720> ahead<00:08:00.900> and 00:08:01.129 --> 00:08:01.139 align:start position:0% so if you want to you can go ahead and 00:08:01.139 --> 00:08:03.230 align:start position:0% so if you want to you can go ahead and run<00:08:01.620> it<00:08:01.800> just<00:08:01.979> like<00:08:02.160> this<00:08:02.340> and<00:08:02.699> you<00:08:02.880> will<00:08:03.000> have 00:08:03.230 --> 00:08:03.240 align:start position:0% run it just like this and you will have 00:08:03.240 --> 00:08:05.330 align:start position:0% run it just like this and you will have this<00:08:03.479> word<00:08:03.660> list<00:08:03.960> so<00:08:04.259> if<00:08:04.440> we<00:08:04.560> run<00:08:04.740> this<00:08:04.979> you<00:08:05.220> can 00:08:05.330 --> 00:08:05.340 align:start position:0% this word list so if we run this you can 00:08:05.340 --> 00:08:07.670 align:start position:0% this word list so if we run this you can actually<00:08:05.520> see<00:08:06.000> right<00:08:06.660> here 00:08:07.670 --> 00:08:07.680 align:start position:0% actually see right here 00:08:07.680 --> 00:08:10.070 align:start position:0% actually see right here the<00:08:08.340> progress<00:08:08.819> you<00:08:09.120> can<00:08:09.240> see<00:08:09.419> the<00:08:09.780> number<00:08:09.900> of 00:08:10.070 --> 00:08:10.080 align:start position:0% the progress you can see the number of 00:08:10.080 --> 00:08:12.350 align:start position:0% the progress you can see the number of requests<00:08:10.560> that<00:08:10.680> are<00:08:10.860> being<00:08:11.039> sent<00:08:11.340> and<00:08:12.000> so<00:08:12.120> it's 00:08:12.350 --> 00:08:12.360 align:start position:0% requests that are being sent and so it's 00:08:12.360 --> 00:08:14.990 align:start position:0% requests that are being sent and so it's sending<00:08:12.780> 37<00:08:13.259> requests<00:08:13.800> every<00:08:14.220> second<00:08:14.520> which 00:08:14.990 --> 00:08:15.000 align:start position:0% sending 37 requests every second which 00:08:15.000 --> 00:08:17.089 align:start position:0% sending 37 requests every second which is<00:08:15.120> actually<00:08:15.360> kind<00:08:15.660> of<00:08:15.780> a<00:08:15.900> lot<00:08:16.080> one<00:08:16.979> of<00:08:17.099> the 00:08:17.089 --> 00:08:17.099 align:start position:0% is actually kind of a lot one of the 00:08:17.099 --> 00:08:18.950 align:start position:0% is actually kind of a lot one of the things<00:08:17.280> about<00:08:17.460> fuff<00:08:17.880> is<00:08:18.060> it<00:08:18.240> is<00:08:18.360> really<00:08:18.599> fast 00:08:18.950 --> 00:08:18.960 align:start position:0% things about fuff is it is really fast 00:08:18.960 --> 00:08:21.469 align:start position:0% things about fuff is it is really fast you<00:08:19.620> can<00:08:19.740> actually<00:08:19.979> we'll<00:08:20.819> actually<00:08:21.060> show<00:08:21.300> you 00:08:21.469 --> 00:08:21.479 align:start position:0% you can actually we'll actually show you 00:08:21.479 --> 00:08:23.689 align:start position:0% you can actually we'll actually show you how<00:08:21.780> fast<00:08:21.900> this<00:08:22.139> will<00:08:22.319> run<00:08:22.560> without<00:08:23.220> slowing 00:08:23.689 --> 00:08:23.699 align:start position:0% how fast this will run without slowing 00:08:23.699 --> 00:08:25.730 align:start position:0% how fast this will run without slowing it<00:08:23.819> down<00:08:24.000> and<00:08:24.660> you<00:08:24.780> can<00:08:24.900> see<00:08:25.020> right<00:08:25.259> here<00:08:25.440> it's 00:08:25.730 --> 00:08:25.740 align:start position:0% it down and you can see right here it's 00:08:25.740 --> 00:08:29.809 align:start position:0% it down and you can see right here it's sending<00:08:26.360> 680<00:08:27.360> around<00:08:28.199> 600<00:08:28.800> requests<00:08:29.340> per 00:08:29.809 --> 00:08:29.819 align:start position:0% sending 680 around 600 requests per 00:08:29.819 --> 00:08:31.369 align:start position:0% sending 680 around 600 requests per second<00:08:30.000> and<00:08:30.300> that<00:08:30.479> is<00:08:30.599> really<00:08:30.840> fast<00:08:31.020> you're 00:08:31.369 --> 00:08:31.379 align:start position:0% second and that is really fast you're 00:08:31.379 --> 00:08:32.630 align:start position:0% second and that is really fast you're definitely<00:08:31.620> going<00:08:31.740> to<00:08:31.800> get<00:08:31.919> yourself<00:08:32.099> rate 00:08:32.630 --> 00:08:32.640 align:start position:0% definitely going to get yourself rate 00:08:32.640 --> 00:08:35.089 align:start position:0% definitely going to get yourself rate limited<00:08:33.120> or<00:08:33.539> or<00:08:33.899> picked<00:08:34.320> up<00:08:34.380> running<00:08:34.620> requests 00:08:35.089 --> 00:08:35.099 align:start position:0% limited or or picked up running requests 00:08:35.099 --> 00:08:37.730 align:start position:0% limited or or picked up running requests of<00:08:35.279> that<00:08:35.459> quickly<00:08:35.760> but<00:08:36.240> fuff<00:08:36.899> is<00:08:37.200> my<00:08:37.440> go-to 00:08:37.730 --> 00:08:37.740 align:start position:0% of that quickly but fuff is my go-to 00:08:37.740 --> 00:08:39.290 align:start position:0% of that quickly but fuff is my go-to tool<00:08:38.099> I<00:08:38.279> often<00:08:38.580> tell<00:08:38.700> people<00:08:38.880> that<00:08:39.120> you<00:08:39.180> can 00:08:39.290 --> 00:08:39.300 align:start position:0% tool I often tell people that you can 00:08:39.300 --> 00:08:41.449 align:start position:0% tool I often tell people that you can run<00:08:39.479> derb<00:08:40.020> just<00:08:40.320> like<00:08:40.560> this<00:08:40.740> and<00:08:41.219> you 00:08:41.449 --> 00:08:41.459 align:start position:0% run derb just like this and you 00:08:41.459 --> 00:08:43.010 align:start position:0% run derb just like this and you shouldn't<00:08:41.700> find<00:08:41.880> yourself<00:08:42.120> in<00:08:42.539> any<00:08:42.779> trouble 00:08:43.010 --> 00:08:43.020 align:start position:0% shouldn't find yourself in any trouble 00:08:43.020 --> 00:08:44.990 align:start position:0% shouldn't find yourself in any trouble because<00:08:43.260> derp<00:08:43.680> is<00:08:43.800> pretty<00:08:43.979> slow<00:08:44.159> but<00:08:44.760> I<00:08:44.940> like 00:08:44.990 --> 00:08:45.000 align:start position:0% because derp is pretty slow but I like 00:08:45.000 --> 00:08:47.269 align:start position:0% because derp is pretty slow but I like to<00:08:45.180> use<00:08:45.300> fluff<00:08:45.600> because<00:08:45.899> of<00:08:46.200> the<00:08:46.500> options<00:08:46.920> that 00:08:47.269 --> 00:08:47.279 align:start position:0% to use fluff because of the options that 00:08:47.279 --> 00:08:49.670 align:start position:0% to use fluff because of the options that are<00:08:47.519> available<00:08:47.760> with<00:08:48.660> it<00:08:48.839> now<00:08:49.200> I<00:08:49.380> want<00:08:49.440> to<00:08:49.560> go 00:08:49.670 --> 00:08:49.680 align:start position:0% are available with it now I want to go 00:08:49.680 --> 00:08:51.470 align:start position:0% are available with it now I want to go ahead<00:08:49.800> and<00:08:50.040> show<00:08:50.339> you<00:08:50.459> how<00:08:50.880> to<00:08:51.060> install 00:08:51.470 --> 00:08:51.480 align:start position:0% ahead and show you how to install 00:08:51.480 --> 00:08:53.870 align:start position:0% ahead and show you how to install seclist<00:08:52.320> I'm<00:08:52.980> actually<00:08:53.100> going<00:08:53.339> to<00:08:53.459> come<00:08:53.640> back 00:08:53.870 --> 00:08:53.880 align:start position:0% seclist I'm actually going to come back 00:08:53.880 --> 00:08:56.389 align:start position:0% seclist I'm actually going to come back here<00:08:54.300> I<00:08:54.779> do<00:08:54.899> have<00:08:55.140> seclist<00:08:55.620> already<00:08:55.980> installed 00:08:56.389 --> 00:08:56.399 align:start position:0% here I do have seclist already installed 00:08:56.399 --> 00:08:57.710 align:start position:0% here I do have seclist already installed which<00:08:56.580> will<00:08:56.760> save<00:08:56.940> us<00:08:57.120> some<00:08:57.240> time<00:08:57.360> but<00:08:57.540> you<00:08:57.660> can 00:08:57.710 --> 00:08:57.720 align:start position:0% which will save us some time but you can 00:08:57.720 --> 00:09:00.590 align:start position:0% which will save us some time but you can come<00:08:57.899> out<00:08:58.019> to<00:08:58.200> Google<00:08:58.560> go<00:08:59.339> to<00:08:59.760> their<00:09:00.240> GitHub 00:09:00.590 --> 00:09:00.600 align:start position:0% come out to Google go to their GitHub 00:09:00.600 --> 00:09:03.470 align:start position:0% come out to Google go to their GitHub page<00:09:00.899> right<00:09:01.200> here<00:09:01.440> and<00:09:02.040> you<00:09:02.279> can<00:09:02.339> run<00:09:02.700> a<00:09:03.180> git 00:09:03.470 --> 00:09:03.480 align:start position:0% page right here and you can run a git 00:09:03.480 --> 00:09:05.630 align:start position:0% page right here and you can run a git clone<00:09:03.839> so<00:09:04.080> we'll<00:09:04.260> copy<00:09:04.560> that<00:09:04.740> right<00:09:04.980> here<00:09:05.160> and 00:09:05.630 --> 00:09:05.640 align:start position:0% clone so we'll copy that right here and 00:09:05.640 --> 00:09:07.490 align:start position:0% clone so we'll copy that right here and you'll<00:09:05.820> want<00:09:05.940> a<00:09:06.060> CD<00:09:06.360> into<00:09:06.660> your<00:09:07.019> opt<00:09:07.200> and<00:09:07.380> then 00:09:07.490 --> 00:09:07.500 align:start position:0% you'll want a CD into your opt and then 00:09:07.500 --> 00:09:10.970 align:start position:0% you'll want a CD into your opt and then you<00:09:07.560> can<00:09:07.980> type<00:09:08.399> in<00:09:08.640> a<00:09:09.120> git<00:09:09.839> clone<00:09:10.200> right<00:09:10.740> here 00:09:10.970 --> 00:09:10.980 align:start position:0% you can type in a git clone right here 00:09:10.980 --> 00:09:13.310 align:start position:0% you can type in a git clone right here just<00:09:11.640> like<00:09:11.820> this<00:09:12.060> and<00:09:12.540> you<00:09:12.779> can<00:09:12.839> see<00:09:12.959> it's<00:09:13.140> the 00:09:13.310 --> 00:09:13.320 align:start position:0% just like this and you can see it's the 00:09:13.320 --> 00:09:14.690 align:start position:0% just like this and you can see it's the last<00:09:13.500> thing<00:09:13.680> I<00:09:13.800> actually<00:09:13.920> installed<00:09:14.339> on<00:09:14.519> here 00:09:14.690 --> 00:09:14.700 align:start position:0% last thing I actually installed on here 00:09:14.700 --> 00:09:17.030 align:start position:0% last thing I actually installed on here this<00:09:15.300> will<00:09:15.480> take<00:09:15.779> a<00:09:16.019> little<00:09:16.080> while<00:09:16.260> to<00:09:16.560> run<00:09:16.740> and 00:09:17.030 --> 00:09:17.040 align:start position:0% this will take a little while to run and 00:09:17.040 --> 00:09:19.850 align:start position:0% this will take a little while to run and then<00:09:17.100> you<00:09:17.279> can<00:09:17.399> CD<00:09:17.760> into<00:09:18.600> the<00:09:19.019> seclist<00:09:19.380> and<00:09:19.740> you 00:09:19.850 --> 00:09:19.860 align:start position:0% then you can CD into the seclist and you 00:09:19.860 --> 00:09:21.350 align:start position:0% then you can CD into the seclist and you can<00:09:19.980> start<00:09:20.100> looking<00:09:20.399> through<00:09:20.760> all<00:09:21.060> of<00:09:21.180> the 00:09:21.350 --> 00:09:21.360 align:start position:0% can start looking through all of the 00:09:21.360 --> 00:09:23.570 align:start position:0% can start looking through all of the different<00:09:21.540> word<00:09:22.380> lists<00:09:22.800> that<00:09:22.920> they<00:09:23.220> have<00:09:23.399> in 00:09:23.570 --> 00:09:23.580 align:start position:0% different word lists that they have in 00:09:23.580 --> 00:09:25.430 align:start position:0% different word lists that they have in here<00:09:23.760> so<00:09:23.880> you<00:09:24.060> have<00:09:24.120> a<00:09:24.240> fuzzing<00:09:24.600> directory<00:09:25.200> you 00:09:25.430 --> 00:09:25.440 align:start position:0% here so you have a fuzzing directory you 00:09:25.440 --> 00:09:27.110 align:start position:0% here so you have a fuzzing directory you have<00:09:25.620> a<00:09:25.860> discovery<00:09:26.399> directory<00:09:26.760> and<00:09:27.000> I 00:09:27.110 --> 00:09:27.120 align:start position:0% have a discovery directory and I 00:09:27.120 --> 00:09:30.829 align:start position:0% have a discovery directory and I actually<00:09:27.240> think<00:09:27.620> the<00:09:28.620> discovery<00:09:29.480> has<00:09:30.480> some 00:09:30.829 --> 00:09:30.839 align:start position:0% actually think the discovery has some 00:09:30.839 --> 00:09:32.630 align:start position:0% actually think the discovery has some pretty<00:09:31.019> good<00:09:31.200> word<00:09:31.560> lists<00:09:31.920> and<00:09:32.160> then<00:09:32.279> we<00:09:32.519> can 00:09:32.630 --> 00:09:32.640 align:start position:0% pretty good word lists and then we can 00:09:32.640 --> 00:09:34.910 align:start position:0% pretty good word lists and then we can CD<00:09:33.000> into<00:09:33.360> the<00:09:34.019> fuzzing<00:09:34.380> because<00:09:34.560> that's<00:09:34.740> what 00:09:34.910 --> 00:09:34.920 align:start position:0% CD into the fuzzing because that's what 00:09:34.920 --> 00:09:37.250 align:start position:0% CD into the fuzzing because that's what we're<00:09:35.040> doing<00:09:35.220> and<00:09:35.880> there<00:09:36.180> is<00:09:36.420> all<00:09:36.839> of<00:09:36.959> these 00:09:37.250 --> 00:09:37.260 align:start position:0% we're doing and there is all of these 00:09:37.260 --> 00:09:39.110 align:start position:0% we're doing and there is all of these different<00:09:37.500> word<00:09:37.800> lists<00:09:38.100> for<00:09:38.399> you<00:09:38.519> to<00:09:38.760> pick 00:09:39.110 --> 00:09:39.120 align:start position:0% different word lists for you to pick 00:09:39.120 --> 00:09:41.329 align:start position:0% different word lists for you to pick from<00:09:39.360> when<00:09:39.779> you're<00:09:39.899> doing<00:09:40.140> your<00:09:40.620> fuzzings<00:09:41.100> so 00:09:41.329 --> 00:09:41.339 align:start position:0% from when you're doing your fuzzings so 00:09:41.339 --> 00:09:43.130 align:start position:0% from when you're doing your fuzzings so this<00:09:41.519> is<00:09:41.580> how<00:09:41.760> I<00:09:41.880> would<00:09:42.000> recommend<00:09:42.300> scanning<00:09:42.839> a 00:09:43.130 --> 00:09:43.140 align:start position:0% this is how I would recommend scanning a 00:09:43.140 --> 00:09:45.530 align:start position:0% this is how I would recommend scanning a bug<00:09:43.440> Bounty<00:09:43.920> program<00:09:44.100> if<00:09:44.820> you<00:09:45.000> are<00:09:45.180> looking 00:09:45.530 --> 00:09:45.540 align:start position:0% bug Bounty program if you are looking 00:09:45.540 --> 00:09:47.870 align:start position:0% bug Bounty program if you are looking for<00:09:45.959> specific<00:09:46.320> ports<00:09:46.740> to<00:09:46.860> be<00:09:46.980> open<00:09:47.100> or<00:09:47.459> you<00:09:47.700> are 00:09:47.870 --> 00:09:47.880 align:start position:0% for specific ports to be open or you are 00:09:47.880 --> 00:09:50.389 align:start position:0% for specific ports to be open or you are checking<00:09:48.360> for<00:09:48.720> directories<00:09:49.560> so<00:09:49.920> good<00:09:50.220> luck 00:09:50.389 --> 00:09:50.399 align:start position:0% checking for directories so good luck 00:09:50.399 --> 00:09:52.790 align:start position:0% checking for directories so good luck with<00:09:50.880> your<00:09:51.240> bug<00:09:51.480> hunting<00:09:51.959> we're<00:09:52.260> going<00:09:52.500> to<00:09:52.620> be 00:09:52.790 --> 00:09:52.800 align:start position:0% with your bug hunting we're going to be 00:09:52.800 --> 00:09:55.550 align:start position:0% with your bug hunting we're going to be covering<00:09:53.279> the<00:09:53.820> tool<00:09:54.300> showdan<00:09:54.959> for<00:09:55.440> the 00:09:55.550 --> 00:09:55.560 align:start position:0% covering the tool showdan for the 00:09:55.560 --> 00:09:57.350 align:start position:0% covering the tool showdan for the purpose<00:09:55.800> of<00:09:56.040> a<00:09:56.160> bug<00:09:56.339> bounty<00:09:56.760> hunting<00:09:57.060> and 00:09:57.350 --> 00:09:57.360 align:start position:0% purpose of a bug bounty hunting and 00:09:57.360 --> 00:09:59.810 align:start position:0% purpose of a bug bounty hunting and searching<00:09:57.779> for<00:09:57.959> vulnerabilities<00:09:58.680> as<00:09:59.220> well<00:09:59.399> as 00:09:59.810 --> 00:09:59.820 align:start position:0% searching for vulnerabilities as well as 00:09:59.820 --> 00:10:02.090 align:start position:0% searching for vulnerabilities as well as information<00:10:00.500> disclosure<00:10:01.500> and<00:10:01.740> how<00:10:01.920> to<00:10:01.980> use 00:10:02.090 --> 00:10:02.100 align:start position:0% information disclosure and how to use 00:10:02.100 --> 00:10:04.550 align:start position:0% information disclosure and how to use the<00:10:02.339> tool<00:10:02.580> within<00:10:03.000> the<00:10:03.480> command<00:10:03.839> line<00:10:04.019> as<00:10:04.380> well 00:10:04.550 --> 00:10:04.560 align:start position:0% the tool within the command line as well 00:10:04.560 --> 00:10:08.030 align:start position:0% the tool within the command line as well as<00:10:05.040> the<00:10:05.820> actual<00:10:06.120> browser<00:10:06.720> showdan<00:10:07.320> is<00:10:07.560> an 00:10:08.030 --> 00:10:08.040 align:start position:0% as the actual browser showdan is an 00:10:08.040 --> 00:10:09.650 align:start position:0% as the actual browser showdan is an excellent<00:10:08.339> tool<00:10:08.640> for<00:10:08.760> those<00:10:08.940> who<00:10:09.120> are<00:10:09.240> new<00:10:09.480> to 00:10:09.650 --> 00:10:09.660 align:start position:0% excellent tool for those who are new to 00:10:09.660 --> 00:10:11.269 align:start position:0% excellent tool for those who are new to the<00:10:09.839> world<00:10:09.959> of<00:10:10.080> bug<00:10:10.260> bounty<00:10:10.620> hunting<00:10:10.860> or<00:10:10.980> those 00:10:11.269 --> 00:10:11.279 align:start position:0% the world of bug bounty hunting or those 00:10:11.279 --> 00:10:12.949 align:start position:0% the world of bug bounty hunting or those who<00:10:11.519> are<00:10:11.640> attempted<00:10:12.120> when<00:10:12.300> they<00:10:12.480> read<00:10:12.660> a 00:10:12.949 --> 00:10:12.959 align:start position:0% who are attempted when they read a 00:10:12.959 --> 00:10:14.750 align:start position:0% who are attempted when they read a program<00:10:13.380> and<00:10:13.680> it<00:10:13.860> says<00:10:14.100> that<00:10:14.220> you<00:10:14.399> should<00:10:14.640> not 00:10:14.750 --> 00:10:14.760 align:start position:0% program and it says that you should not 00:10:14.760 --> 00:10:16.910 align:start position:0% program and it says that you should not scan<00:10:15.180> a<00:10:15.360> network<00:10:15.600> and<00:10:16.320> you<00:10:16.500> don't<00:10:16.560> really<00:10:16.740> want 00:10:16.910 --> 00:10:16.920 align:start position:0% scan a network and you don't really want 00:10:16.920 --> 00:10:18.350 align:start position:0% scan a network and you don't really want to<00:10:17.040> run<00:10:17.100> nmap<00:10:17.580> and<00:10:17.700> you're<00:10:17.820> too<00:10:17.940> afraid<00:10:18.240> to 00:10:18.350 --> 00:10:18.360 align:start position:0% to run nmap and you're too afraid to 00:10:18.360 --> 00:10:19.730 align:start position:0% to run nmap and you're too afraid to actually<00:10:18.540> scan<00:10:18.899> the<00:10:19.080> network<00:10:19.260> you<00:10:19.500> can<00:10:19.620> go 00:10:19.730 --> 00:10:19.740 align:start position:0% actually scan the network you can go 00:10:19.740 --> 00:10:21.829 align:start position:0% actually scan the network you can go check<00:10:19.920> out<00:10:20.040> Showdown<00:10:20.519> because<00:10:20.700> showdan<00:10:21.300> scans 00:10:21.829 --> 00:10:21.839 align:start position:0% check out Showdown because showdan scans 00:10:21.839 --> 00:10:23.210 align:start position:0% check out Showdown because showdan scans the<00:10:22.019> network<00:10:22.140> automatically<00:10:22.740> and<00:10:23.100> then 00:10:23.210 --> 00:10:23.220 align:start position:0% the network automatically and then 00:10:23.220 --> 00:10:24.949 align:start position:0% the network automatically and then stores<00:10:23.459> all<00:10:23.700> the<00:10:23.880> information<00:10:24.000> in<00:10:24.600> its 00:10:24.949 --> 00:10:24.959 align:start position:0% stores all the information in its 00:10:24.959 --> 00:10:26.750 align:start position:0% stores all the information in its database<00:10:25.380> so<00:10:25.740> all<00:10:25.920> we<00:10:26.040> have<00:10:26.220> to<00:10:26.279> do<00:10:26.399> is<00:10:26.580> know 00:10:26.750 --> 00:10:26.760 align:start position:0% database so all we have to do is know 00:10:26.760 --> 00:10:28.250 align:start position:0% database so all we have to do is know what<00:10:27.000> queries<00:10:27.360> to<00:10:27.540> run<00:10:27.660> to<00:10:27.839> pull<00:10:28.080> the 00:10:28.250 --> 00:10:28.260 align:start position:0% what queries to run to pull the 00:10:28.260 --> 00:10:30.590 align:start position:0% what queries to run to pull the information<00:10:28.380> from<00:10:28.860> showdan<00:10:29.399> and<00:10:30.000> read<00:10:30.360> their 00:10:30.590 --> 00:10:30.600 align:start position:0% information from showdan and read their 00:10:30.600 --> 00:10:32.630 align:start position:0% information from showdan and read their information<00:10:30.839> from<00:10:31.440> when<00:10:31.560> they<00:10:31.800> have<00:10:31.980> crawled 00:10:32.630 --> 00:10:32.640 align:start position:0% information from when they have crawled 00:10:32.640 --> 00:10:34.430 align:start position:0% information from when they have crawled the<00:10:33.060> network<00:10:33.360> or<00:10:33.720> the<00:10:33.899> web<00:10:34.019> browser 00:10:34.430 --> 00:10:34.440 align:start position:0% the network or the web browser 00:10:34.440 --> 00:10:36.050 align:start position:0% the network or the web browser previously<00:10:34.980> and<00:10:35.160> then<00:10:35.279> we<00:10:35.459> have<00:10:35.580> access<00:10:35.760> to 00:10:36.050 --> 00:10:36.060 align:start position:0% previously and then we have access to 00:10:36.060 --> 00:10:37.670 align:start position:0% previously and then we have access to all<00:10:36.240> of<00:10:36.360> that<00:10:36.480> information<00:10:36.660> without<00:10:37.320> having 00:10:37.670 --> 00:10:37.680 align:start position:0% all of that information without having 00:10:37.680 --> 00:10:39.949 align:start position:0% all of that information without having to<00:10:38.040> scan<00:10:38.519> the<00:10:38.940> actual<00:10:39.180> Target<00:10:39.420> and<00:10:39.779> you<00:10:39.899> don't 00:10:39.949 --> 00:10:39.959 align:start position:0% to scan the actual Target and you don't 00:10:39.959 --> 00:10:41.329 align:start position:0% to scan the actual Target and you don't have<00:10:40.080> to<00:10:40.200> worry<00:10:40.260> about<00:10:40.440> breaking<00:10:40.860> any<00:10:41.040> program 00:10:41.329 --> 00:10:41.339 align:start position:0% have to worry about breaking any program 00:10:41.339 --> 00:10:43.190 align:start position:0% have to worry about breaking any program rules<00:10:41.940> so<00:10:42.180> the<00:10:42.300> way<00:10:42.420> Showdown<00:10:42.779> works<00:10:43.080> is 00:10:43.190 --> 00:10:43.200 align:start position:0% rules so the way Showdown works is 00:10:43.200 --> 00:10:44.509 align:start position:0% rules so the way Showdown works is actually<00:10:43.380> goes<00:10:43.680> out<00:10:43.740> and<00:10:43.860> crawls<00:10:44.339> every 00:10:44.509 --> 00:10:44.519 align:start position:0% actually goes out and crawls every 00:10:44.519 --> 00:10:45.889 align:start position:0% actually goes out and crawls every single<00:10:44.760> device<00:10:44.940> that<00:10:45.300> is<00:10:45.360> connected<00:10:45.660> to<00:10:45.779> the 00:10:45.889 --> 00:10:45.899 align:start position:0% single device that is connected to the 00:10:45.899 --> 00:10:47.329 align:start position:0% single device that is connected to the internet<00:10:46.079> whether<00:10:46.560> it<00:10:46.680> be<00:10:46.800> your<00:10:47.100> thermostat 00:10:47.329 --> 00:10:47.339 align:start position:0% internet whether it be your thermostat 00:10:47.339 --> 00:10:50.329 align:start position:0% internet whether it be your thermostat your<00:10:47.760> refrigerator<00:10:48.200> or<00:10:49.200> your<00:10:49.680> web<00:10:50.100> security 00:10:50.329 --> 00:10:50.339 align:start position:0% your refrigerator or your web security 00:10:50.339 --> 00:10:51.829 align:start position:0% your refrigerator or your web security cameras<00:10:50.880> and<00:10:51.120> it'll<00:10:51.300> see<00:10:51.480> if<00:10:51.600> there's<00:10:51.660> any 00:10:51.829 --> 00:10:51.839 align:start position:0% cameras and it'll see if there's any 00:10:51.839 --> 00:10:53.030 align:start position:0% cameras and it'll see if there's any vulnerabilities<00:10:52.380> it'll<00:10:52.740> store<00:10:52.860> the 00:10:53.030 --> 00:10:53.040 align:start position:0% vulnerabilities it'll store the 00:10:53.040 --> 00:10:55.670 align:start position:0% vulnerabilities it'll store the information<00:10:53.220> such<00:10:53.940> as<00:10:54.120> the<00:10:54.480> software<00:10:55.019> that<00:10:55.440> is 00:10:55.670 --> 00:10:55.680 align:start position:0% information such as the software that is 00:10:55.680 --> 00:10:57.710 align:start position:0% information such as the software that is currently<00:10:56.160> running<00:10:56.399> on<00:10:56.640> it<00:10:56.760> and<00:10:57.000> if<00:10:57.300> it<00:10:57.480> has 00:10:57.710 --> 00:10:57.720 align:start position:0% currently running on it and if it has 00:10:57.720 --> 00:10:59.389 align:start position:0% currently running on it and if it has any<00:10:57.899> vulnerabilities<00:10:58.440> it<00:10:58.740> is<00:10:58.920> now<00:10:59.040> open<00:10:59.220> to 00:10:59.389 --> 00:10:59.399 align:start position:0% any vulnerabilities it is now open to 00:10:59.399 --> 00:11:01.610 align:start position:0% any vulnerabilities it is now open to the<00:10:59.579> web<00:10:59.700> and<00:10:59.940> anyone<00:11:00.240> can<00:11:00.420> access<00:11:00.660> your 00:11:01.610 --> 00:11:01.620 align:start position:0% the web and anyone can access your 00:11:01.620 --> 00:11:03.410 align:start position:0% the web and anyone can access your information<00:11:01.800> your<00:11:02.459> thermostat<00:11:02.700> refrigerator 00:11:03.410 --> 00:11:03.420 align:start position:0% information your thermostat refrigerator 00:11:03.420 --> 00:11:06.470 align:start position:0% information your thermostat refrigerator your<00:11:03.839> webcam<00:11:04.320> or<00:11:04.980> even<00:11:05.160> your<00:11:05.579> printers<00:11:06.060> if 00:11:06.470 --> 00:11:06.480 align:start position:0% your webcam or even your printers if 00:11:06.480 --> 00:11:08.750 align:start position:0% your webcam or even your printers if they<00:11:06.779> have<00:11:06.899> any<00:11:07.079> vulnerability<00:11:07.500> days<00:11:07.980> then 00:11:08.750 --> 00:11:08.760 align:start position:0% they have any vulnerability days then 00:11:08.760 --> 00:11:10.730 align:start position:0% they have any vulnerability days then the<00:11:09.120> whole<00:11:09.240> world<00:11:09.480> will<00:11:09.959> know<00:11:10.200> it<00:11:10.380> because<00:11:10.500> all 00:11:10.730 --> 00:11:10.740 align:start position:0% the whole world will know it because all 00:11:10.740 --> 00:11:12.590 align:start position:0% the whole world will know it because all they<00:11:10.860> have<00:11:10.980> to<00:11:11.100> do<00:11:11.220> is<00:11:11.459> query<00:11:11.940> that<00:11:12.240> specific 00:11:12.590 --> 00:11:12.600 align:start position:0% they have to do is query that specific 00:11:12.600 --> 00:11:15.530 align:start position:0% they have to do is query that specific version<00:11:12.899> such<00:11:13.380> as<00:11:13.620> WordPress<00:11:14.180> 1.4.7<00:11:15.180> and<00:11:15.420> if 00:11:15.530 --> 00:11:15.540 align:start position:0% version such as WordPress 1.4.7 and if 00:11:15.540 --> 00:11:16.850 align:start position:0% version such as WordPress 1.4.7 and if you<00:11:15.660> have<00:11:15.779> a<00:11:15.899> web<00:11:16.019> application<00:11:16.500> that<00:11:16.740> is 00:11:16.850 --> 00:11:16.860 align:start position:0% you have a web application that is 00:11:16.860 --> 00:11:18.350 align:start position:0% you have a web application that is running<00:11:17.040> that<00:11:17.399> specific<00:11:17.700> WordPress<00:11:18.060> version 00:11:18.350 --> 00:11:18.360 align:start position:0% running that specific WordPress version 00:11:18.360 --> 00:11:19.670 align:start position:0% running that specific WordPress version the<00:11:18.660> whole<00:11:18.779> world<00:11:18.899> is<00:11:19.140> going<00:11:19.260> to<00:11:19.380> know<00:11:19.560> it 00:11:19.670 --> 00:11:19.680 align:start position:0% the whole world is going to know it 00:11:19.680 --> 00:11:21.710 align:start position:0% the whole world is going to know it because<00:11:19.860> there<00:11:20.100> will<00:11:20.279> be<00:11:20.339> a<00:11:20.459> cve<00:11:20.700> on<00:11:21.060> it<00:11:21.240> and 00:11:21.710 --> 00:11:21.720 align:start position:0% because there will be a cve on it and 00:11:21.720 --> 00:11:24.050 align:start position:0% because there will be a cve on it and you<00:11:21.899> will<00:11:22.079> be<00:11:22.260> open<00:11:22.680> to<00:11:22.980> a<00:11:23.399> potential<00:11:23.820> attack 00:11:24.050 --> 00:11:24.060 align:start position:0% you will be open to a potential attack 00:11:24.060 --> 00:11:26.389 align:start position:0% you will be open to a potential attack so<00:11:24.600> the<00:11:25.019> way<00:11:25.140> Showdown<00:11:25.620> works<00:11:25.980> is<00:11:26.100> it<00:11:26.279> just 00:11:26.389 --> 00:11:26.399 align:start position:0% so the way Showdown works is it just 00:11:26.399 --> 00:11:27.829 align:start position:0% so the way Showdown works is it just crawls<00:11:26.820> all<00:11:26.940> of<00:11:27.120> the<00:11:27.180> internet<00:11:27.300> and<00:11:27.600> stores 00:11:27.829 --> 00:11:27.839 align:start position:0% crawls all of the internet and stores 00:11:27.839 --> 00:11:29.449 align:start position:0% crawls all of the internet and stores all<00:11:28.260> of<00:11:28.380> the<00:11:28.500> information<00:11:28.680> that<00:11:29.100> it<00:11:29.279> can 00:11:29.449 --> 00:11:29.459 align:start position:0% all of the information that it can 00:11:29.459 --> 00:11:31.550 align:start position:0% all of the information that it can possibly<00:11:29.760> grab<00:11:30.180> for<00:11:30.540> anything<00:11:30.839> that<00:11:31.320> is 00:11:31.550 --> 00:11:31.560 align:start position:0% possibly grab for anything that is 00:11:31.560 --> 00:11:33.590 align:start position:0% possibly grab for anything that is connected<00:11:32.040> to<00:11:32.220> the<00:11:32.519> internet<00:11:32.760> so<00:11:33.300> what<00:11:33.480> we're 00:11:33.590 --> 00:11:33.600 align:start position:0% connected to the internet so what we're 00:11:33.600 --> 00:11:36.350 align:start position:0% connected to the internet so what we're going<00:11:33.720> to<00:11:33.839> do<00:11:33.899> in<00:11:34.380> this<00:11:34.740> video<00:11:34.920> is<00:11:35.399> run<00:11:35.760> queries 00:11:36.350 --> 00:11:36.360 align:start position:0% going to do in this video is run queries 00:11:36.360 --> 00:11:37.790 align:start position:0% going to do in this video is run queries on<00:11:36.600> Showdown<00:11:36.959> but<00:11:37.320> because<00:11:37.380> we're<00:11:37.620> going<00:11:37.740> to 00:11:37.790 --> 00:11:37.800 align:start position:0% on Showdown but because we're going to 00:11:37.800 --> 00:11:38.990 align:start position:0% on Showdown but because we're going to be<00:11:37.860> doing<00:11:37.980> this<00:11:38.100> with<00:11:38.279> a<00:11:38.399> free<00:11:38.519> account<00:11:38.700> you're 00:11:38.990 --> 00:11:39.000 align:start position:0% be doing this with a free account you're 00:11:39.000 --> 00:11:40.370 align:start position:0% be doing this with a free account you're only<00:11:39.120> going<00:11:39.300> to<00:11:39.300> be<00:11:39.420> able<00:11:39.480> to<00:11:39.600> run<00:11:39.899> a<00:11:40.260> very 00:11:40.370 --> 00:11:40.380 align:start position:0% only going to be able to run a very 00:11:40.380 --> 00:11:43.430 align:start position:0% only going to be able to run a very limited<00:11:40.800> amount<00:11:41.220> of<00:11:41.459> commands<00:11:42.060> or<00:11:42.300> scans<00:11:42.839> if 00:11:43.430 --> 00:11:43.440 align:start position:0% limited amount of commands or scans if 00:11:43.440 --> 00:11:45.050 align:start position:0% limited amount of commands or scans if you're<00:11:43.560> actually<00:11:43.740> wanting<00:11:44.100> to<00:11:44.279> use<00:11:44.700> The 00:11:45.050 --> 00:11:45.060 align:start position:0% you're actually wanting to use The 00:11:45.060 --> 00:11:47.150 align:start position:0% you're actually wanting to use The Showdown<00:11:45.600> scan<00:11:46.140> feature<00:11:46.560> you're<00:11:46.920> going<00:11:47.100> to 00:11:47.150 --> 00:11:47.160 align:start position:0% Showdown scan feature you're going to 00:11:47.160 --> 00:11:48.949 align:start position:0% Showdown scan feature you're going to actually<00:11:47.339> have<00:11:47.579> to<00:11:47.820> pay<00:11:48.180> for<00:11:48.360> it<00:11:48.540> I<00:11:48.660> think<00:11:48.779> it's 00:11:48.949 --> 00:11:48.959 align:start position:0% actually have to pay for it I think it's 00:11:48.959 --> 00:11:51.590 align:start position:0% actually have to pay for it I think it's 70<00:11:49.200> a<00:11:49.800> month<00:11:49.980> which<00:11:50.279> is<00:11:50.399> kind<00:11:50.640> of<00:11:50.700> steep<00:11:51.060> I 00:11:51.590 --> 00:11:51.600 align:start position:0% 70 a month which is kind of steep I 00:11:51.600 --> 00:11:52.850 align:start position:0% 70 a month which is kind of steep I personally<00:11:51.959> would<00:11:52.140> rather<00:11:52.260> just<00:11:52.500> scan<00:11:52.680> it 00:11:52.850 --> 00:11:52.860 align:start position:0% personally would rather just scan it 00:11:52.860 --> 00:11:54.650 align:start position:0% personally would rather just scan it myself<00:11:52.980> with<00:11:53.220> nmap<00:11:53.700> and<00:11:53.820> look<00:11:54.000> at<00:11:54.120> the<00:11:54.180> ports<00:11:54.480> I 00:11:54.650 --> 00:11:54.660 align:start position:0% myself with nmap and look at the ports I 00:11:54.660 --> 00:11:55.970 align:start position:0% myself with nmap and look at the ports I specifically<00:11:55.079> want<00:11:55.320> and<00:11:55.620> read<00:11:55.800> the 00:11:55.970 --> 00:11:55.980 align:start position:0% specifically want and read the 00:11:55.980 --> 00:11:58.130 align:start position:0% specifically want and read the information<00:11:56.160> that<00:11:56.579> comes<00:11:56.880> back<00:11:57.000> that<00:11:57.480> way<00:11:57.600> but 00:11:58.130 --> 00:11:58.140 align:start position:0% information that comes back that way but 00:11:58.140 --> 00:11:59.690 align:start position:0% information that comes back that way but I<00:11:58.260> know<00:11:58.440> that<00:11:58.800> some<00:11:58.980> of<00:11:59.100> you<00:11:59.220> would<00:11:59.519> probably 00:11:59.690 --> 00:11:59.700 align:start position:0% I know that some of you would probably 00:11:59.700 --> 00:12:01.610 align:start position:0% I know that some of you would probably rather<00:12:00.000> just<00:12:00.240> pay<00:12:00.360> the<00:12:00.480> 70<00:12:00.660> a<00:12:01.079> month<00:12:01.200> and<00:12:01.380> have 00:12:01.610 --> 00:12:01.620 align:start position:0% rather just pay the 70 a month and have 00:12:01.620 --> 00:12:03.410 align:start position:0% rather just pay the 70 a month and have access<00:12:01.800> to<00:12:02.040> the<00:12:02.220> monitoring<00:12:02.640> feature<00:12:03.180> that 00:12:03.410 --> 00:12:03.420 align:start position:0% access to the monitoring feature that 00:12:03.420 --> 00:12:04.970 align:start position:0% access to the monitoring feature that we're<00:12:03.540> going<00:12:03.660> to<00:12:03.779> cover<00:12:03.899> a<00:12:04.500> little<00:12:04.620> bit<00:12:04.740> later 00:12:04.970 --> 00:12:04.980 align:start position:0% we're going to cover a little bit later 00:12:04.980 --> 00:12:06.410 align:start position:0% we're going to cover a little bit later on<00:12:05.160> so<00:12:05.459> typically<00:12:05.760> when<00:12:05.940> I<00:12:06.060> think<00:12:06.180> of<00:12:06.300> the 00:12:06.410 --> 00:12:06.420 align:start position:0% on so typically when I think of the 00:12:06.420 --> 00:12:08.030 align:start position:0% on so typically when I think of the people<00:12:06.540> who<00:12:06.779> are<00:12:06.899> going<00:12:07.019> to<00:12:07.140> enjoy<00:12:07.440> way<00:12:07.860> it 00:12:08.030 --> 00:12:08.040 align:start position:0% people who are going to enjoy way it 00:12:08.040 --> 00:12:09.889 align:start position:0% people who are going to enjoy way it Showdown<00:12:08.399> the<00:12:08.760> most<00:12:08.880> I<00:12:09.180> often<00:12:09.480> think<00:12:09.600> that 00:12:09.889 --> 00:12:09.899 align:start position:0% Showdown the most I often think that 00:12:09.899 --> 00:12:11.269 align:start position:0% Showdown the most I often think that black<00:12:10.140> hat<00:12:10.380> hackers<00:12:10.740> are<00:12:10.860> going<00:12:10.980> to<00:12:11.100> be<00:12:11.160> the 00:12:11.269 --> 00:12:11.279 align:start position:0% black hat hackers are going to be the 00:12:11.279 --> 00:12:12.889 align:start position:0% black hat hackers are going to be the ones<00:12:11.459> who<00:12:11.640> love<00:12:11.880> Showdown<00:12:12.360> the<00:12:12.600> most<00:12:12.660> because 00:12:12.889 --> 00:12:12.899 align:start position:0% ones who love Showdown the most because 00:12:12.899 --> 00:12:14.509 align:start position:0% ones who love Showdown the most because it<00:12:13.140> stores<00:12:13.380> all<00:12:14.040> the<00:12:14.160> different<00:12:14.339> version 00:12:14.509 --> 00:12:14.519 align:start position:0% it stores all the different version 00:12:14.519 --> 00:12:16.550 align:start position:0% it stores all the different version numbers<00:12:14.820> and<00:12:15.060> if<00:12:15.240> a<00:12:15.360> new<00:12:15.420> cve<00:12:15.779> comes<00:12:16.200> out<00:12:16.260> and 00:12:16.550 --> 00:12:16.560 align:start position:0% numbers and if a new cve comes out and 00:12:16.560 --> 00:12:18.050 align:start position:0% numbers and if a new cve comes out and somebody<00:12:16.860> says<00:12:17.279> okay<00:12:17.459> we<00:12:17.760> have<00:12:17.880> this 00:12:18.050 --> 00:12:18.060 align:start position:0% somebody says okay we have this 00:12:18.060 --> 00:12:20.389 align:start position:0% somebody says okay we have this vulnerability<00:12:18.540> to<00:12:18.959> this<00:12:19.500> specific<00:12:19.980> software 00:12:20.389 --> 00:12:20.399 align:start position:0% vulnerability to this specific software 00:12:20.399 --> 00:12:22.069 align:start position:0% vulnerability to this specific software they<00:12:20.820> can<00:12:20.940> just<00:12:21.060> scan<00:12:21.360> all<00:12:21.660> of<00:12:21.779> the<00:12:21.899> internet 00:12:22.069 --> 00:12:22.079 align:start position:0% they can just scan all of the internet 00:12:22.079 --> 00:12:23.690 align:start position:0% they can just scan all of the internet and<00:12:22.320> find<00:12:22.440> out<00:12:22.620> what<00:12:22.980> devices<00:12:23.220> are<00:12:23.519> running 00:12:23.690 --> 00:12:23.700 align:start position:0% and find out what devices are running 00:12:23.700 --> 00:12:25.069 align:start position:0% and find out what devices are running that<00:12:23.940> specific<00:12:24.180> software<00:12:24.600> because<00:12:24.779> black 00:12:25.069 --> 00:12:25.079 align:start position:0% that specific software because black 00:12:25.079 --> 00:12:26.690 align:start position:0% that specific software because black hats<00:12:25.440> don't<00:12:25.620> really<00:12:25.740> care<00:12:25.980> they<00:12:26.459> can<00:12:26.579> just 00:12:26.690 --> 00:12:26.700 align:start position:0% hats don't really care they can just 00:12:26.700 --> 00:12:28.670 align:start position:0% hats don't really care they can just attack<00:12:26.940> anything<00:12:27.360> but<00:12:27.779> this<00:12:27.959> can<00:12:28.140> also<00:12:28.440> be 00:12:28.670 --> 00:12:28.680 align:start position:0% attack anything but this can also be 00:12:28.680 --> 00:12:30.470 align:start position:0% attack anything but this can also be helpful<00:12:29.040> for<00:12:29.279> bug<00:12:29.519> bounty<00:12:29.940> hunters<00:12:30.180> as<00:12:30.360> well 00:12:30.470 --> 00:12:30.480 align:start position:0% helpful for bug bounty hunters as well 00:12:30.480 --> 00:12:32.569 align:start position:0% helpful for bug bounty hunters as well because<00:12:30.720> if<00:12:31.019> a<00:12:31.140> new<00:12:31.260> CV<00:12:31.560> comes<00:12:31.860> out<00:12:31.980> you<00:12:32.220> can<00:12:32.339> go 00:12:32.569 --> 00:12:32.579 align:start position:0% because if a new CV comes out you can go 00:12:32.579 --> 00:12:34.190 align:start position:0% because if a new CV comes out you can go out<00:12:32.820> the<00:12:33.120> same<00:12:33.240> way<00:12:33.420> as<00:12:33.540> a<00:12:33.660> black<00:12:33.779> cat<00:12:33.959> would 00:12:34.190 --> 00:12:34.200 align:start position:0% out the same way as a black cat would 00:12:34.200 --> 00:12:36.889 align:start position:0% out the same way as a black cat would and<00:12:34.860> say<00:12:35.279> Showdown<00:12:35.880> show<00:12:36.180> me<00:12:36.360> all<00:12:36.540> of<00:12:36.660> the 00:12:36.889 --> 00:12:36.899 align:start position:0% and say Showdown show me all of the 00:12:36.899 --> 00:12:38.449 align:start position:0% and say Showdown show me all of the devices<00:12:37.260> running<00:12:37.620> the<00:12:37.860> specific<00:12:38.160> software 00:12:38.449 --> 00:12:38.459 align:start position:0% devices running the specific software 00:12:38.459 --> 00:12:40.610 align:start position:0% devices running the specific software that<00:12:38.700> are<00:12:38.820> vulnerable<00:12:39.120> to<00:12:39.300> this<00:12:39.540> cve<00:12:39.899> and<00:12:40.500> then 00:12:40.610 --> 00:12:40.620 align:start position:0% that are vulnerable to this cve and then 00:12:40.620 --> 00:12:43.069 align:start position:0% that are vulnerable to this cve and then you<00:12:40.800> can<00:12:40.920> download<00:12:41.220> all<00:12:41.880> of<00:12:42.060> those<00:12:42.480> devices 00:12:43.069 --> 00:12:43.079 align:start position:0% you can download all of those devices 00:12:43.079 --> 00:12:44.569 align:start position:0% you can download all of those devices and<00:12:43.560> look<00:12:43.680> through<00:12:43.860> them<00:12:44.040> to<00:12:44.220> see<00:12:44.279> if<00:12:44.459> there 00:12:44.569 --> 00:12:44.579 align:start position:0% and look through them to see if there 00:12:44.579 --> 00:12:45.829 align:start position:0% and look through them to see if there are<00:12:44.639> any<00:12:44.760> web<00:12:44.940> applications<00:12:45.360> that<00:12:45.660> are 00:12:45.829 --> 00:12:45.839 align:start position:0% are any web applications that are 00:12:45.839 --> 00:12:47.750 align:start position:0% are any web applications that are running<00:12:45.959> that<00:12:46.320> specific<00:12:46.620> software<00:12:47.100> and<00:12:47.639> then 00:12:47.750 --> 00:12:47.760 align:start position:0% running that specific software and then 00:12:47.760 --> 00:12:49.069 align:start position:0% running that specific software and then see<00:12:47.940> if<00:12:48.060> they<00:12:48.180> have<00:12:48.300> a<00:12:48.360> bug<00:12:48.480> binding<00:12:48.959> program 00:12:49.069 --> 00:12:49.079 align:start position:0% see if they have a bug binding program 00:12:49.079 --> 00:12:51.410 align:start position:0% see if they have a bug binding program and<00:12:49.500> report<00:12:49.800> it<00:12:50.160> this<00:12:50.639> is<00:12:50.880> going<00:12:51.060> to<00:12:51.240> be<00:12:51.300> kind 00:12:51.410 --> 00:12:51.420 align:start position:0% and report it this is going to be kind 00:12:51.420 --> 00:12:53.389 align:start position:0% and report it this is going to be kind of<00:12:51.540> tedious<00:12:51.899> but<00:12:52.139> it'll<00:12:52.320> be<00:12:52.440> really<00:12:52.680> easy<00:12:52.860> bugs 00:12:53.389 --> 00:12:53.399 align:start position:0% of tedious but it'll be really easy bugs 00:12:53.399 --> 00:12:56.150 align:start position:0% of tedious but it'll be really easy bugs to<00:12:53.820> find<00:12:54.240> and<00:12:54.839> vulnerabilities<00:12:55.380> to<00:12:55.740> report 00:12:56.150 --> 00:12:56.160 align:start position:0% to find and vulnerabilities to report 00:12:56.160 --> 00:12:57.889 align:start position:0% to find and vulnerabilities to report because<00:12:56.579> all<00:12:56.880> you<00:12:57.000> have<00:12:57.060> to<00:12:57.180> do<00:12:57.300> is<00:12:57.480> read<00:12:57.720> the 00:12:57.889 --> 00:12:57.899 align:start position:0% because all you have to do is read the 00:12:57.899 --> 00:12:59.509 align:start position:0% because all you have to do is read the downloaded<00:12:58.320> file<00:12:58.500> and<00:12:58.740> look<00:12:58.920> for<00:12:59.040> open<00:12:59.279> Bug 00:12:59.509 --> 00:12:59.519 align:start position:0% downloaded file and look for open Bug 00:12:59.519 --> 00:13:01.370 align:start position:0% downloaded file and look for open Bug bounding<00:12:59.940> programs<00:13:00.300> on<00:13:00.600> those<00:13:00.720> specific<00:13:01.079> web 00:13:01.370 --> 00:13:01.380 align:start position:0% bounding programs on those specific web 00:13:01.380 --> 00:13:03.350 align:start position:0% bounding programs on those specific web applications<00:13:01.860> so<00:13:02.399> an<00:13:02.579> example<00:13:02.820> of<00:13:03.000> Showdown 00:13:03.350 --> 00:13:03.360 align:start position:0% applications so an example of Showdown 00:13:03.360 --> 00:13:04.970 align:start position:0% applications so an example of Showdown being<00:13:03.600> used<00:13:03.779> in<00:13:03.959> a<00:13:04.139> really<00:13:04.200> massively<00:13:04.740> way 00:13:04.970 --> 00:13:04.980 align:start position:0% being used in a really massively way 00:13:04.980 --> 00:13:07.009 align:start position:0% being used in a really massively way kind<00:13:05.339> of<00:13:05.459> for<00:13:05.639> an<00:13:05.940> unethical<00:13:06.300> purpose<00:13:06.660> can<00:13:06.899> be 00:13:07.009 --> 00:13:07.019 align:start position:0% kind of for an unethical purpose can be 00:13:07.019 --> 00:13:09.290 align:start position:0% kind of for an unethical purpose can be seen<00:13:07.139> on<00:13:07.320> on<00:13:07.680> Dark<00:13:07.920> Net<00:13:08.100> Diaries<00:13:08.519> I<00:13:08.820> forget<00:13:09.000> the 00:13:09.290 --> 00:13:09.300 align:start position:0% seen on on Dark Net Diaries I forget the 00:13:09.300 --> 00:13:11.210 align:start position:0% seen on on Dark Net Diaries I forget the name<00:13:09.540> of<00:13:09.959> this<00:13:10.139> specific<00:13:10.440> episode<00:13:10.740> I<00:13:11.040> think<00:13:11.100> it 00:13:11.210 --> 00:13:11.220 align:start position:0% name of this specific episode I think it 00:13:11.220 --> 00:13:12.590 align:start position:0% name of this specific episode I think it came<00:13:11.399> out<00:13:11.459> a<00:13:11.579> couple<00:13:11.700> months<00:13:11.940> ago<00:13:12.120> and<00:13:12.300> the<00:13:12.480> guy 00:13:12.590 --> 00:13:12.600 align:start position:0% came out a couple months ago and the guy 00:13:12.600 --> 00:13:14.990 align:start position:0% came out a couple months ago and the guy goes<00:13:12.959> by<00:13:13.139> the<00:13:13.740> hacker<00:13:14.160> giraffe<00:13:14.760> where<00:13:14.880> he 00:13:14.990 --> 00:13:15.000 align:start position:0% goes by the hacker giraffe where he 00:13:15.000 --> 00:13:16.370 align:start position:0% goes by the hacker giraffe where he actually<00:13:15.180> used<00:13:15.360> showdan<00:13:15.839> to<00:13:16.079> look<00:13:16.200> for 00:13:16.370 --> 00:13:16.380 align:start position:0% actually used showdan to look for 00:13:16.380 --> 00:13:18.470 align:start position:0% actually used showdan to look for vulnerable<00:13:16.740> printers<00:13:17.220> and<00:13:17.820> he<00:13:18.060> printed 00:13:18.470 --> 00:13:18.480 align:start position:0% vulnerable printers and he printed 00:13:18.480 --> 00:13:20.930 align:start position:0% vulnerable printers and he printed subscribe<00:13:19.139> to<00:13:19.260> PewDiePie<00:13:19.740> to<00:13:20.040> over<00:13:20.220> 50<00:13:20.820> 000 00:13:20.930 --> 00:13:20.940 align:start position:0% subscribe to PewDiePie to over 50 000 00:13:20.940 --> 00:13:22.550 align:start position:0% subscribe to PewDiePie to over 50 000 different<00:13:21.360> printers<00:13:21.779> he<00:13:22.079> was<00:13:22.200> able<00:13:22.380> to<00:13:22.440> do 00:13:22.550 --> 00:13:22.560 align:start position:0% different printers he was able to do 00:13:22.560 --> 00:13:24.590 align:start position:0% different printers he was able to do this<00:13:22.740> really<00:13:22.920> easily<00:13:23.339> and<00:13:23.940> really<00:13:24.180> quickly 00:13:24.590 --> 00:13:24.600 align:start position:0% this really easily and really quickly 00:13:24.600 --> 00:13:26.030 align:start position:0% this really easily and really quickly because<00:13:24.899> he<00:13:25.139> was<00:13:25.260> able<00:13:25.440> to<00:13:25.560> just<00:13:25.680> use<00:13:25.860> a 00:13:26.030 --> 00:13:26.040 align:start position:0% because he was able to just use a 00:13:26.040 --> 00:13:27.769 align:start position:0% because he was able to just use a showdown<00:13:26.459> to<00:13:26.639> look<00:13:26.760> for<00:13:26.940> vulnerable<00:13:27.420> printers 00:13:27.769 --> 00:13:27.779 align:start position:0% showdown to look for vulnerable printers 00:13:27.779 --> 00:13:29.810 align:start position:0% showdown to look for vulnerable printers and<00:13:28.019> so<00:13:28.139> in<00:13:28.320> that<00:13:28.500> episode<00:13:28.740> of<00:13:29.279> dark<00:13:29.519> net 00:13:29.810 --> 00:13:29.820 align:start position:0% and so in that episode of dark net 00:13:29.820 --> 00:13:31.250 align:start position:0% and so in that episode of dark net Diaries<00:13:30.300> I<00:13:30.540> think<00:13:30.660> you<00:13:30.779> can<00:13:30.899> just<00:13:30.959> look<00:13:31.079> up 00:13:31.250 --> 00:13:31.260 align:start position:0% Diaries I think you can just look up 00:13:31.260 --> 00:13:33.350 align:start position:0% Diaries I think you can just look up darknet<00:13:31.740> Diaries<00:13:32.040> hacker<00:13:32.459> giraffe<00:13:32.940> and 00:13:33.350 --> 00:13:33.360 align:start position:0% darknet Diaries hacker giraffe and 00:13:33.360 --> 00:13:35.030 align:start position:0% darknet Diaries hacker giraffe and listen<00:13:33.600> to<00:13:33.779> it<00:13:33.959> if<00:13:34.079> you<00:13:34.200> want<00:13:34.380> all<00:13:34.620> that<00:13:34.860> guy 00:13:35.030 --> 00:13:35.040 align:start position:0% listen to it if you want all that guy 00:13:35.040 --> 00:13:37.250 align:start position:0% listen to it if you want all that guy did<00:13:35.399> specifically<00:13:36.060> was<00:13:36.300> go<00:13:36.480> to<00:13:36.600> Showdown<00:13:36.959> and 00:13:37.250 --> 00:13:37.260 align:start position:0% did specifically was go to Showdown and 00:13:37.260 --> 00:13:39.050 align:start position:0% did specifically was go to Showdown and look<00:13:37.380> for<00:13:37.560> vulnerable<00:13:38.279> printers<00:13:38.700> and<00:13:38.940> it 00:13:39.050 --> 00:13:39.060 align:start position:0% look for vulnerable printers and it 00:13:39.060 --> 00:13:40.370 align:start position:0% look for vulnerable printers and it seems<00:13:39.300> like<00:13:39.420> that's<00:13:39.600> kind<00:13:39.839> of<00:13:39.899> one<00:13:40.079> of<00:13:40.200> his 00:13:40.370 --> 00:13:40.380 align:start position:0% seems like that's kind of one of his 00:13:40.380 --> 00:13:43.190 align:start position:0% seems like that's kind of one of his go-to<00:13:40.860> tools<00:13:41.339> is<00:13:41.579> to<00:13:41.760> go<00:13:41.880> to<00:13:42.060> Showdown<00:13:42.959> look 00:13:43.190 --> 00:13:43.200 align:start position:0% go-to tools is to go to Showdown look 00:13:43.200 --> 00:13:45.110 align:start position:0% go-to tools is to go to Showdown look for<00:13:43.440> some<00:13:43.800> vulnerable<00:13:44.399> software<00:13:44.760> and<00:13:45.000> then 00:13:45.110 --> 00:13:45.120 align:start position:0% for some vulnerable software and then 00:13:45.120 --> 00:13:46.670 align:start position:0% for some vulnerable software and then look<00:13:45.240> at<00:13:45.420> all<00:13:45.660> of<00:13:45.779> the<00:13:45.899> devices<00:13:46.139> that<00:13:46.500> happen 00:13:46.670 --> 00:13:46.680 align:start position:0% look at all of the devices that happen 00:13:46.680 --> 00:13:48.650 align:start position:0% look at all of the devices that happen to<00:13:46.860> be<00:13:47.040> vulnerable<00:13:47.459> to<00:13:47.820> that<00:13:48.360> specific 00:13:48.650 --> 00:13:48.660 align:start position:0% to be vulnerable to that specific 00:13:48.660 --> 00:13:51.050 align:start position:0% to be vulnerable to that specific software<00:13:49.320> or<00:13:49.620> cve<00:13:50.100> so<00:13:50.519> let's<00:13:50.579> go<00:13:50.760> ahead<00:13:50.880> and 00:13:51.050 --> 00:13:51.060 align:start position:0% software or cve so let's go ahead and 00:13:51.060 --> 00:13:53.329 align:start position:0% software or cve so let's go ahead and jump<00:13:51.360> into<00:13:51.540> it<00:13:51.720> here<00:13:51.959> we<00:13:52.139> are<00:13:52.320> I<00:13:52.860> have<00:13:53.040> gone 00:13:53.329 --> 00:13:53.339 align:start position:0% jump into it here we are I have gone 00:13:53.339 --> 00:13:55.550 align:start position:0% jump into it here we are I have gone ahead<00:13:53.639> and<00:13:53.940> opened<00:13:54.420> up<00:13:54.540> a<00:13:54.779> terminal<00:13:55.079> which<00:13:55.380> you 00:13:55.550 --> 00:13:55.560 align:start position:0% ahead and opened up a terminal which you 00:13:55.560 --> 00:13:56.930 align:start position:0% ahead and opened up a terminal which you will<00:13:55.680> want<00:13:55.860> to<00:13:55.920> do<00:13:56.040> and<00:13:56.279> then<00:13:56.459> you<00:13:56.579> will<00:13:56.700> also 00:13:56.930 --> 00:13:56.940 align:start position:0% will want to do and then you will also 00:13:56.940 --> 00:13:59.269 align:start position:0% will want to do and then you will also want<00:13:57.120> to<00:13:57.240> go<00:13:57.420> to<00:13:57.740> showdan.io<00:13:58.740> I'm<00:13:59.100> already 00:13:59.269 --> 00:13:59.279 align:start position:0% want to go to showdan.io I'm already 00:13:59.279 --> 00:14:01.970 align:start position:0% want to go to showdan.io I'm already logged<00:13:59.700> in<00:13:59.760> you'll<00:14:00.060> click<00:14:00.300> login<00:14:00.600> over<00:14:00.959> here<00:14:01.200> I 00:14:01.970 --> 00:14:01.980 align:start position:0% logged in you'll click login over here I 00:14:01.980 --> 00:14:04.730 align:start position:0% logged in you'll click login over here I personally<00:14:02.399> just<00:14:02.639> log<00:14:02.820> in<00:14:03.060> with<00:14:03.360> Google<00:14:03.779> and 00:14:04.730 --> 00:14:04.740 align:start position:0% personally just log in with Google and 00:14:04.740 --> 00:14:07.730 align:start position:0% personally just log in with Google and this<00:14:05.100> is<00:14:05.279> a<00:14:05.639> non-paid<00:14:06.300> account<00:14:06.540> so<00:14:07.019> we<00:14:07.320> you're 00:14:07.730 --> 00:14:07.740 align:start position:0% this is a non-paid account so we you're 00:14:07.740 --> 00:14:09.650 align:start position:0% this is a non-paid account so we you're going<00:14:07.920> to<00:14:08.100> be<00:14:08.160> looking<00:14:08.519> at<00:14:08.820> basically<00:14:09.360> the 00:14:09.650 --> 00:14:09.660 align:start position:0% going to be looking at basically the 00:14:09.660 --> 00:14:11.569 align:start position:0% going to be looking at basically the exact<00:14:09.959> same<00:14:10.139> setup<00:14:10.440> that<00:14:10.680> you're<00:14:10.980> going<00:14:11.339> to 00:14:11.569 --> 00:14:11.579 align:start position:0% exact same setup that you're going to 00:14:11.579 --> 00:14:13.910 align:start position:0% exact same setup that you're going to have<00:14:12.000> when<00:14:12.600> you<00:14:12.720> first<00:14:12.899> open<00:14:13.139> up<00:14:13.320> a<00:14:13.500> showdan 00:14:13.910 --> 00:14:13.920 align:start position:0% have when you first open up a showdan 00:14:13.920 --> 00:14:15.530 align:start position:0% have when you first open up a showdan the<00:14:14.220> first<00:14:14.339> thing<00:14:14.459> we're<00:14:14.639> going<00:14:14.760> to<00:14:14.820> do<00:14:15.000> is<00:14:15.240> be 00:14:15.530 --> 00:14:15.540 align:start position:0% the first thing we're going to do is be 00:14:15.540 --> 00:14:17.870 align:start position:0% the first thing we're going to do is be using<00:14:15.779> showdan<00:14:16.380> from<00:14:16.860> the<00:14:17.220> terminal<00:14:17.519> so<00:14:17.760> if 00:14:17.870 --> 00:14:17.880 align:start position:0% using showdan from the terminal so if 00:14:17.880 --> 00:14:19.329 align:start position:0% using showdan from the terminal so if you<00:14:18.000> just<00:14:18.120> come<00:14:18.300> in<00:14:18.420> here<00:14:18.540> and<00:14:18.779> type<00:14:18.959> in 00:14:19.329 --> 00:14:19.339 align:start position:0% you just come in here and type in 00:14:19.339 --> 00:14:21.829 align:start position:0% you just come in here and type in showdan<00:14:20.339> and<00:14:20.519> hit<00:14:20.700> enter<00:14:20.880> you're<00:14:21.300> going<00:14:21.600> to 00:14:21.829 --> 00:14:21.839 align:start position:0% showdan and hit enter you're going to 00:14:21.839 --> 00:14:24.470 align:start position:0% showdan and hit enter you're going to get<00:14:22.320> a<00:14:22.560> bunch<00:14:22.860> of<00:14:23.100> options<00:14:23.579> now<00:14:23.880> these<00:14:24.180> options 00:14:24.470 --> 00:14:24.480 align:start position:0% get a bunch of options now these options 00:14:24.480 --> 00:14:26.569 align:start position:0% get a bunch of options now these options are<00:14:24.660> going<00:14:24.779> to<00:14:24.959> be<00:14:25.079> default<00:14:25.740> and<00:14:26.040> Showdown 00:14:26.569 --> 00:14:26.579 align:start position:0% are going to be default and Showdown 00:14:26.579 --> 00:14:28.610 align:start position:0% are going to be default and Showdown should<00:14:26.820> already<00:14:27.060> be<00:14:27.300> installed<00:14:27.839> on<00:14:28.079> your<00:14:28.200> Kali 00:14:28.610 --> 00:14:28.620 align:start position:0% should already be installed on your Kali 00:14:28.620 --> 00:14:30.590 align:start position:0% should already be installed on your Kali Linux<00:14:28.920> machine<00:14:29.160> so<00:14:30.000> I'm<00:14:30.180> not<00:14:30.300> going<00:14:30.480> to 00:14:30.590 --> 00:14:30.600 align:start position:0% Linux machine so I'm not going to 00:14:30.600 --> 00:14:32.329 align:start position:0% Linux machine so I'm not going to actually<00:14:30.660> walk<00:14:30.959> you<00:14:31.139> through<00:14:31.380> how<00:14:31.860> to<00:14:32.040> install 00:14:32.329 --> 00:14:32.339 align:start position:0% actually walk you through how to install 00:14:32.339 --> 00:14:33.829 align:start position:0% actually walk you through how to install Showdown<00:14:32.940> because<00:14:33.120> we're<00:14:33.300> going<00:14:33.420> to<00:14:33.540> run<00:14:33.660> it 00:14:33.829 --> 00:14:33.839 align:start position:0% Showdown because we're going to run it 00:14:33.839 --> 00:14:36.230 align:start position:0% Showdown because we're going to run it straight<00:14:34.079> from<00:14:34.380> here<00:14:34.620> first<00:14:35.399> in<00:14:35.820> the<00:14:36.000> terminal 00:14:36.230 --> 00:14:36.240 align:start position:0% straight from here first in the terminal 00:14:36.240 --> 00:14:37.910 align:start position:0% straight from here first in the terminal and<00:14:36.540> then<00:14:36.660> we'll<00:14:36.839> go<00:14:37.079> through<00:14:37.320> and<00:14:37.740> actually 00:14:37.910 --> 00:14:37.920 align:start position:0% and then we'll go through and actually 00:14:37.920 --> 00:14:41.329 align:start position:0% and then we'll go through and actually check<00:14:38.339> out<00:14:38.579> the<00:14:39.120> browser<00:14:40.019> version<00:14:40.440> later<00:14:41.100> on 00:14:41.329 --> 00:14:41.339 align:start position:0% check out the browser version later on 00:14:41.339 --> 00:14:43.310 align:start position:0% check out the browser version later on I've<00:14:41.699> decided<00:14:42.120> to<00:14:42.240> show<00:14:42.660> both<00:14:42.839> the<00:14:43.079> terminal 00:14:43.310 --> 00:14:43.320 align:start position:0% I've decided to show both the terminal 00:14:43.320 --> 00:14:45.350 align:start position:0% I've decided to show both the terminal and<00:14:43.620> the<00:14:43.980> browser<00:14:44.399> because<00:14:44.820> there<00:14:45.120> are<00:14:45.240> some 00:14:45.350 --> 00:14:45.360 align:start position:0% and the browser because there are some 00:14:45.360 --> 00:14:46.790 align:start position:0% and the browser because there are some people<00:14:45.480> who<00:14:45.779> really<00:14:45.959> like<00:14:46.139> running<00:14:46.440> things 00:14:46.790 --> 00:14:46.800 align:start position:0% people who really like running things 00:14:46.800 --> 00:14:48.470 align:start position:0% people who really like running things straight<00:14:47.100> from<00:14:47.279> the<00:14:47.459> terminal<00:14:47.699> and<00:14:48.240> you'll<00:14:48.360> be 00:14:48.470 --> 00:14:48.480 align:start position:0% straight from the terminal and you'll be 00:14:48.480 --> 00:14:49.730 align:start position:0% straight from the terminal and you'll be able<00:14:48.600> to<00:14:48.720> play<00:14:48.839> around<00:14:49.019> with<00:14:49.260> it<00:14:49.380> and<00:14:49.560> figure 00:14:49.730 --> 00:14:49.740 align:start position:0% able to play around with it and figure 00:14:49.740 --> 00:14:51.230 align:start position:0% able to play around with it and figure out<00:14:49.860> exactly<00:14:50.339> what<00:14:50.519> you<00:14:50.639> like<00:14:50.760> and<00:14:51.000> then<00:14:51.120> there 00:14:51.230 --> 00:14:51.240 align:start position:0% out exactly what you like and then there 00:14:51.240 --> 00:14:52.910 align:start position:0% out exactly what you like and then there are<00:14:51.420> other<00:14:51.480> people<00:14:51.720> who<00:14:52.139> like<00:14:52.380> to<00:14:52.560> have<00:14:52.740> a 00:14:52.910 --> 00:14:52.920 align:start position:0% are other people who like to have a 00:14:52.920 --> 00:14:54.949 align:start position:0% are other people who like to have a graphical<00:14:53.220> user<00:14:53.579> interface<00:14:54.000> and<00:14:54.660> they'll 00:14:54.949 --> 00:14:54.959 align:start position:0% graphical user interface and they'll 00:14:54.959 --> 00:14:57.530 align:start position:0% graphical user interface and they'll like<00:14:55.139> the<00:14:55.260> browsing<00:14:55.620> version<00:14:56.040> better<00:14:56.820> and<00:14:57.300> so 00:14:57.530 --> 00:14:57.540 align:start position:0% like the browsing version better and so 00:14:57.540 --> 00:14:59.090 align:start position:0% like the browsing version better and so what<00:14:57.779> we're<00:14:57.899> going<00:14:58.019> to<00:14:58.139> do<00:14:58.260> is<00:14:58.380> go<00:14:58.680> ahead<00:14:58.860> and 00:14:59.090 --> 00:14:59.100 align:start position:0% what we're going to do is go ahead and 00:14:59.100 --> 00:15:02.150 align:start position:0% what we're going to do is go ahead and initialize<00:14:59.940> our<00:15:00.839> Showdown<00:15:01.440> for<00:15:01.680> the<00:15:01.860> terminal 00:15:02.150 --> 00:15:02.160 align:start position:0% initialize our Showdown for the terminal 00:15:02.160 --> 00:15:03.769 align:start position:0% initialize our Showdown for the terminal and<00:15:02.399> you<00:15:02.579> can<00:15:02.699> see<00:15:02.940> this<00:15:03.180> right<00:15:03.360> here<00:15:03.540> this 00:15:03.769 --> 00:15:03.779 align:start position:0% and you can see this right here this 00:15:03.779 --> 00:15:05.449 align:start position:0% and you can see this right here this init<00:15:04.199> so<00:15:04.440> we're<00:15:04.560> going<00:15:04.680> to<00:15:04.740> end<00:15:04.860> up<00:15:04.920> running<00:15:05.160> a 00:15:05.449 --> 00:15:05.459 align:start position:0% init so we're going to end up running a 00:15:05.459 --> 00:15:08.449 align:start position:0% init so we're going to end up running a showdan<00:15:06.060> init<00:15:06.480> but<00:15:06.959> we<00:15:07.079> also<00:15:07.260> also<00:15:07.800> need<00:15:08.220> to 00:15:08.449 --> 00:15:08.459 align:start position:0% showdan init but we also also need to 00:15:08.459 --> 00:15:10.790 align:start position:0% showdan init but we also also need to have<00:15:08.760> our<00:15:09.240> API<00:15:09.720> key<00:15:09.899> so<00:15:10.199> you'll<00:15:10.440> want<00:15:10.620> to<00:15:10.740> go 00:15:10.790 --> 00:15:10.800 align:start position:0% have our API key so you'll want to go 00:15:10.800 --> 00:15:12.949 align:start position:0% have our API key so you'll want to go ahead<00:15:11.040> and<00:15:11.220> log<00:15:12.000> in<00:15:12.240> so<00:15:12.420> you'll<00:15:12.660> want<00:15:12.779> to<00:15:12.839> go 00:15:12.949 --> 00:15:12.959 align:start position:0% ahead and log in so you'll want to go 00:15:12.959 --> 00:15:14.629 align:start position:0% ahead and log in so you'll want to go ahead<00:15:13.079> and<00:15:13.260> create<00:15:13.440> an<00:15:13.620> account<00:15:13.740> and<00:15:14.040> log<00:15:14.399> in 00:15:14.629 --> 00:15:14.639 align:start position:0% ahead and create an account and log in 00:15:14.639 --> 00:15:17.269 align:start position:0% ahead and create an account and log in to<00:15:14.940> Showdown<00:15:15.480> just<00:15:15.839> like<00:15:16.079> this<00:15:16.260> and<00:15:16.860> then<00:15:16.980> you 00:15:17.269 --> 00:15:17.279 align:start position:0% to Showdown just like this and then you 00:15:17.279 --> 00:15:19.069 align:start position:0% to Showdown just like this and then you will<00:15:17.399> click<00:15:17.639> account<00:15:17.880> and<00:15:18.420> you'll<00:15:18.660> be<00:15:18.779> able<00:15:18.899> to 00:15:19.069 --> 00:15:19.079 align:start position:0% will click account and you'll be able to 00:15:19.079 --> 00:15:21.710 align:start position:0% will click account and you'll be able to grab<00:15:19.560> your<00:15:19.800> API<00:15:20.220> key<00:15:20.399> right<00:15:20.880> here<00:15:21.180> so<00:15:21.540> we'll 00:15:21.710 --> 00:15:21.720 align:start position:0% grab your API key right here so we'll 00:15:21.720 --> 00:15:23.930 align:start position:0% grab your API key right here so we'll copy<00:15:22.079> this<00:15:22.260> and<00:15:22.920> come<00:15:23.100> back<00:15:23.279> to<00:15:23.459> our<00:15:23.579> terminal 00:15:23.930 --> 00:15:23.940 align:start position:0% copy this and come back to our terminal 00:15:23.940 --> 00:15:27.350 align:start position:0% copy this and come back to our terminal and<00:15:24.420> we're<00:15:24.600> going<00:15:24.779> to<00:15:24.839> type<00:15:25.079> in<00:15:25.320> shonan 00:15:27.350 --> 00:15:27.360 align:start position:0% and we're going to type in shonan 00:15:27.360 --> 00:15:30.530 align:start position:0% and we're going to type in shonan init<00:15:28.079> and<00:15:28.560> then<00:15:28.680> you<00:15:28.920> will<00:15:29.040> paste<00:15:29.459> in<00:15:29.579> your<00:15:30.120> API 00:15:30.530 --> 00:15:30.540 align:start position:0% init and then you will paste in your API 00:15:30.540 --> 00:15:32.210 align:start position:0% init and then you will paste in your API key<00:15:30.720> and<00:15:31.079> hit<00:15:31.320> enter 00:15:32.210 --> 00:15:32.220 align:start position:0% key and hit enter 00:15:32.220 --> 00:15:34.750 align:start position:0% key and hit enter and<00:15:32.699> it<00:15:32.820> tells<00:15:33.120> us<00:15:33.180> that<00:15:33.420> it<00:15:33.600> has<00:15:33.839> successfully 00:15:34.750 --> 00:15:34.760 align:start position:0% and it tells us that it has successfully 00:15:34.760 --> 00:15:36.949 align:start position:0% and it tells us that it has successfully initialized<00:15:35.760> and<00:15:36.060> now<00:15:36.180> we<00:15:36.360> are<00:15:36.540> ready<00:15:36.660> to 00:15:36.949 --> 00:15:36.959 align:start position:0% initialized and now we are ready to 00:15:36.959 --> 00:15:39.410 align:start position:0% initialized and now we are ready to start<00:15:37.260> making<00:15:37.560> some<00:15:37.980> Showdown<00:15:38.519> queries<00:15:39.120> so 00:15:39.410 --> 00:15:39.420 align:start position:0% start making some Showdown queries so 00:15:39.420 --> 00:15:41.269 align:start position:0% start making some Showdown queries so the<00:15:39.600> first<00:15:39.720> thing<00:15:39.839> we<00:15:39.959> can<00:15:40.079> do<00:15:40.199> is<00:15:40.380> just<00:15:40.620> run<00:15:40.860> a 00:15:41.269 --> 00:15:41.279 align:start position:0% the first thing we can do is just run a 00:15:41.279 --> 00:15:44.269 align:start position:0% the first thing we can do is just run a showdown<00:15:41.760> info<00:15:42.300> right<00:15:42.600> here<00:15:42.720> and<00:15:43.079> see<00:15:43.320> what<00:15:44.100> it 00:15:44.269 --> 00:15:44.279 align:start position:0% showdown info right here and see what it 00:15:44.279 --> 00:15:46.310 align:start position:0% showdown info right here and see what it tells<00:15:44.699> us<00:15:44.760> about<00:15:45.060> our<00:15:45.540> account<00:15:45.779> so<00:15:46.079> we<00:15:46.260> can 00:15:46.310 --> 00:15:46.320 align:start position:0% tells us about our account so we can 00:15:46.320 --> 00:15:48.170 align:start position:0% tells us about our account so we can type<00:15:46.440> in<00:15:46.680> showdan 00:15:48.170 --> 00:15:48.180 align:start position:0% type in showdan 00:15:48.180 --> 00:15:50.030 align:start position:0% type in showdan info 00:15:50.030 --> 00:15:50.040 align:start position:0% info 00:15:50.040 --> 00:15:51.829 align:start position:0% info and<00:15:50.519> then<00:15:50.579> to<00:15:50.760> enter<00:15:50.940> and<00:15:51.360> it's<00:15:51.480> going<00:15:51.660> to<00:15:51.720> tell 00:15:51.829 --> 00:15:51.839 align:start position:0% and then to enter and it's going to tell 00:15:51.839 --> 00:15:54.110 align:start position:0% and then to enter and it's going to tell us<00:15:51.959> we<00:15:52.139> have<00:15:52.320> zero<00:15:52.800> credits<00:15:53.220> available<00:15:53.579> and 00:15:54.110 --> 00:15:54.120 align:start position:0% us we have zero credits available and 00:15:54.120 --> 00:15:56.329 align:start position:0% us we have zero credits available and scan<00:15:54.600> credits<00:15:55.079> available<00:15:55.260> and<00:15:55.980> that<00:15:56.160> is 00:15:56.329 --> 00:15:56.339 align:start position:0% scan credits available and that is 00:15:56.339 --> 00:15:59.030 align:start position:0% scan credits available and that is probably<00:15:56.519> because<00:15:57.000> I<00:15:57.480> have<00:15:57.660> already<00:15:57.959> ran<00:15:58.500> some 00:15:59.030 --> 00:15:59.040 align:start position:0% probably because I have already ran some 00:15:59.040 --> 00:16:01.129 align:start position:0% probably because I have already ran some queries<00:15:59.639> with<00:15:59.940> this<00:16:00.120> over<00:16:00.420> here<00:16:00.600> on<00:16:00.959> the 00:16:01.129 --> 00:16:01.139 align:start position:0% queries with this over here on the 00:16:01.139 --> 00:16:02.449 align:start position:0% queries with this over here on the website<00:16:01.560> but<00:16:01.860> it's<00:16:01.980> not<00:16:02.160> really<00:16:02.279> going<00:16:02.399> to 00:16:02.449 --> 00:16:02.459 align:start position:0% website but it's not really going to 00:16:02.459 --> 00:16:03.650 align:start position:0% website but it's not really going to make<00:16:02.579> a<00:16:02.699> difference<00:16:02.820> I'm<00:16:03.120> going<00:16:03.300> to<00:16:03.360> show<00:16:03.480> you 00:16:03.650 --> 00:16:03.660 align:start position:0% make a difference I'm going to show you 00:16:03.660 --> 00:16:05.509 align:start position:0% make a difference I'm going to show you how<00:16:03.899> to<00:16:04.019> run<00:16:04.199> these<00:16:04.680> queries<00:16:04.980> I<00:16:05.220> just<00:16:05.339> might 00:16:05.509 --> 00:16:05.519 align:start position:0% how to run these queries I just might 00:16:05.519 --> 00:16:07.970 align:start position:0% how to run these queries I just might not<00:16:05.699> get<00:16:05.940> the<00:16:06.420> results<00:16:06.899> back<00:16:07.260> that<00:16:07.620> you<00:16:07.800> will 00:16:07.970 --> 00:16:07.980 align:start position:0% not get the results back that you will 00:16:07.980 --> 00:16:11.150 align:start position:0% not get the results back that you will every<00:16:08.459> time<00:16:08.699> you<00:16:09.240> make<00:16:09.660> a<00:16:10.019> request<00:16:10.380> whether<00:16:10.860> it 00:16:11.150 --> 00:16:11.160 align:start position:0% every time you make a request whether it 00:16:11.160 --> 00:16:14.930 align:start position:0% every time you make a request whether it is<00:16:11.339> over<00:16:11.639> here<00:16:11.940> on<00:16:12.480> the<00:16:12.959> actual<00:16:13.320> browser<00:16:13.860> or<00:16:14.579> it 00:16:14.930 --> 00:16:14.940 align:start position:0% is over here on the actual browser or it 00:16:14.940 --> 00:16:18.050 align:start position:0% is over here on the actual browser or it is<00:16:15.180> inside<00:16:15.600> of<00:16:16.079> the<00:16:16.500> terminal<00:16:17.040> it<00:16:17.579> is<00:16:17.699> going<00:16:17.940> to 00:16:18.050 --> 00:16:18.060 align:start position:0% is inside of the terminal it is going to 00:16:18.060 --> 00:16:21.170 align:start position:0% is inside of the terminal it is going to use<00:16:18.540> one<00:16:19.019> of<00:16:19.199> the<00:16:19.620> credits<00:16:20.220> that<00:16:20.399> you<00:16:20.639> have<00:16:20.820> but 00:16:21.170 --> 00:16:21.180 align:start position:0% use one of the credits that you have but 00:16:21.180 --> 00:16:23.269 align:start position:0% use one of the credits that you have but you<00:16:21.360> can<00:16:21.480> always<00:16:21.660> pay<00:16:22.199> And<00:16:22.680> subscribe<00:16:23.100> to 00:16:23.269 --> 00:16:23.279 align:start position:0% you can always pay And subscribe to 00:16:23.279 --> 00:16:26.329 align:start position:0% you can always pay And subscribe to Showdown<00:16:23.699> and<00:16:24.300> have<00:16:24.660> more<00:16:25.019> credits<00:16:25.560> most<00:16:25.980> of 00:16:26.329 --> 00:16:26.339 align:start position:0% Showdown and have more credits most of 00:16:26.339 --> 00:16:28.430 align:start position:0% Showdown and have more credits most of the<00:16:26.519> bug<00:16:27.000> Hunters<00:16:27.420> who<00:16:27.660> are<00:16:27.839> successful<00:16:28.260> will 00:16:28.430 --> 00:16:28.440 align:start position:0% the bug Hunters who are successful will 00:16:28.440 --> 00:16:30.949 align:start position:0% the bug Hunters who are successful will have<00:16:28.680> a<00:16:28.800> paid<00:16:29.040> subscription<00:16:29.519> to<00:16:29.760> Showdown<00:16:30.300> and 00:16:30.949 --> 00:16:30.959 align:start position:0% have a paid subscription to Showdown and 00:16:30.959 --> 00:16:32.569 align:start position:0% have a paid subscription to Showdown and they<00:16:31.199> really<00:16:31.380> like<00:16:31.620> using<00:16:31.980> Showdown<00:16:32.339> and 00:16:32.569 --> 00:16:32.579 align:start position:0% they really like using Showdown and 00:16:32.579 --> 00:16:34.189 align:start position:0% they really like using Showdown and we're<00:16:32.699> going<00:16:32.820> to<00:16:32.940> cover<00:16:33.060> why<00:16:33.600> it's<00:16:33.899> helpful 00:16:34.189 --> 00:16:34.199 align:start position:0% we're going to cover why it's helpful 00:16:34.199 --> 00:16:36.530 align:start position:0% we're going to cover why it's helpful but<00:16:34.800> personally<00:16:35.220> a<00:16:35.639> lot<00:16:35.760> of<00:16:35.940> the<00:16:36.180> stuff<00:16:36.420> you're 00:16:36.530 --> 00:16:36.540 align:start position:0% but personally a lot of the stuff you're 00:16:36.540 --> 00:16:37.970 align:start position:0% but personally a lot of the stuff you're going<00:16:36.720> to<00:16:36.779> be<00:16:36.839> able<00:16:36.899> to<00:16:37.019> get<00:16:37.139> on<00:16:37.320> Showdown<00:16:37.740> you 00:16:37.970 --> 00:16:37.980 align:start position:0% going to be able to get on Showdown you 00:16:37.980 --> 00:16:40.189 align:start position:0% going to be able to get on Showdown you can<00:16:38.100> find<00:16:38.339> your<00:16:38.639> own<00:16:38.820> self<00:16:39.240> by<00:16:39.540> running<00:16:39.779> some 00:16:40.189 --> 00:16:40.199 align:start position:0% can find your own self by running some 00:16:40.199 --> 00:16:41.990 align:start position:0% can find your own self by running some different<00:16:40.440> tools<00:16:40.800> which<00:16:41.040> I've<00:16:41.220> covered<00:16:41.459> on<00:16:41.759> my 00:16:41.990 --> 00:16:42.000 align:start position:0% different tools which I've covered on my 00:16:42.000 --> 00:16:44.090 align:start position:0% different tools which I've covered on my channel<00:16:42.120> previously<00:16:42.660> but<00:16:43.079> that<00:16:43.560> is<00:16:43.740> not<00:16:43.920> the 00:16:44.090 --> 00:16:44.100 align:start position:0% channel previously but that is not the 00:16:44.100 --> 00:16:45.290 align:start position:0% channel previously but that is not the purpose<00:16:44.339> of<00:16:44.399> this<00:16:44.519> video<00:16:44.639> so<00:16:45.060> the<00:16:45.180> second 00:16:45.290 --> 00:16:45.300 align:start position:0% purpose of this video so the second 00:16:45.300 --> 00:16:47.749 align:start position:0% purpose of this video so the second thing<00:16:45.540> I<00:16:45.720> want<00:16:45.839> to<00:16:46.019> show<00:16:46.139> you<00:16:46.320> is<00:16:46.920> often<00:16:47.399> when 00:16:47.749 --> 00:16:47.759 align:start position:0% thing I want to show you is often when 00:16:47.759 --> 00:16:49.430 align:start position:0% thing I want to show you is often when you<00:16:48.000> want<00:16:48.240> to<00:16:48.360> run<00:16:48.600> something<00:16:48.839> like<00:16:49.139> let's<00:16:49.259> say 00:16:49.430 --> 00:16:49.440 align:start position:0% you want to run something like let's say 00:16:49.440 --> 00:16:52.730 align:start position:0% you want to run something like let's say we<00:16:49.560> want<00:16:49.740> to<00:16:49.920> run<00:16:50.519> this<00:16:51.300> showdown<00:16:52.019> scan<00:16:52.500> right 00:16:52.730 --> 00:16:52.740 align:start position:0% we want to run this showdown scan right 00:16:52.740 --> 00:16:54.530 align:start position:0% we want to run this showdown scan right here<00:16:52.860> what<00:16:53.100> we<00:16:53.279> can<00:16:53.399> do<00:16:53.579> is<00:16:54.060> we<00:16:54.240> can<00:16:54.360> run 00:16:54.530 --> 00:16:54.540 align:start position:0% here what we can do is we can run 00:16:54.540 --> 00:16:58.490 align:start position:0% here what we can do is we can run showdan<00:16:55.440> scan<00:16:56.339> and<00:16:56.820> then<00:16:57.000> a<00:16:57.240> dash<00:16:57.600> H<00:16:57.839> and<00:16:58.380> it's 00:16:58.490 --> 00:16:58.500 align:start position:0% showdan scan and then a dash H and it's 00:16:58.500 --> 00:17:01.189 align:start position:0% showdan scan and then a dash H and it's going<00:16:58.680> to<00:16:58.740> tell<00:16:58.860> us<00:16:59.040> the<00:16:59.459> options<00:16:59.880> for<00:17:00.720> the 00:17:01.189 --> 00:17:01.199 align:start position:0% going to tell us the options for the 00:17:01.199 --> 00:17:03.590 align:start position:0% going to tell us the options for the actual<00:17:01.620> scan<00:17:02.279> right<00:17:02.699> here<00:17:02.880> so<00:17:03.120> you<00:17:03.240> can<00:17:03.360> run<00:17:03.480> a 00:17:03.590 --> 00:17:03.600 align:start position:0% actual scan right here so you can run a 00:17:03.600 --> 00:17:05.750 align:start position:0% actual scan right here so you can run a showdown<00:17:03.899> Dash<00:17:04.260> H<00:17:04.439> and<00:17:04.980> then<00:17:05.100> you<00:17:05.220> can<00:17:05.339> run<00:17:05.520> The 00:17:05.750 --> 00:17:05.760 align:start position:0% showdown Dash H and then you can run The 00:17:05.760 --> 00:17:07.730 align:start position:0% showdown Dash H and then you can run The Showdown<00:17:06.419> scanned<00:17:06.900> sh<00:17:07.020> and<00:17:07.380> it's<00:17:07.439> going<00:17:07.620> to 00:17:07.730 --> 00:17:07.740 align:start position:0% Showdown scanned sh and it's going to 00:17:07.740 --> 00:17:09.890 align:start position:0% Showdown scanned sh and it's going to tell<00:17:07.799> you<00:17:07.980> the<00:17:08.760> list<00:17:09.000> of<00:17:09.179> commands<00:17:09.600> that<00:17:09.720> you 00:17:09.890 --> 00:17:09.900 align:start position:0% tell you the list of commands that you 00:17:09.900 --> 00:17:13.069 align:start position:0% tell you the list of commands that you can<00:17:09.959> run<00:17:10.260> with<00:17:10.860> each<00:17:11.220> one<00:17:11.520> of<00:17:12.120> these<00:17:12.600> with<00:17:12.900> each 00:17:13.069 --> 00:17:13.079 align:start position:0% can run with each one of these with each 00:17:13.079 --> 00:17:14.630 align:start position:0% can run with each one of these with each one<00:17:13.199> of<00:17:13.319> these<00:17:13.500> commands<00:17:13.919> that<00:17:14.040> comes<00:17:14.339> first 00:17:14.630 --> 00:17:14.640 align:start position:0% one of these commands that comes first 00:17:14.640 --> 00:17:16.189 align:start position:0% one of these commands that comes first so<00:17:14.880> when<00:17:15.059> you're<00:17:15.179> using<00:17:15.419> Showdown<00:17:15.780> it'll<00:17:16.079> be 00:17:16.189 --> 00:17:16.199 align:start position:0% so when you're using Showdown it'll be 00:17:16.199 --> 00:17:17.809 align:start position:0% so when you're using Showdown it'll be really<00:17:16.260> helpful<00:17:16.620> for<00:17:17.100> you<00:17:17.160> to<00:17:17.339> know<00:17:17.459> that<00:17:17.640> you 00:17:17.809 --> 00:17:17.819 align:start position:0% really helpful for you to know that you 00:17:17.819 --> 00:17:20.030 align:start position:0% really helpful for you to know that you can<00:17:17.939> run<00:17:18.059> the<00:17:18.240> Das<00:17:18.480> H<00:17:18.660> with<00:17:19.319> each<00:17:19.559> one<00:17:19.740> of<00:17:19.799> these 00:17:20.030 --> 00:17:20.040 align:start position:0% can run the Das H with each one of these 00:17:20.040 --> 00:17:21.470 align:start position:0% can run the Das H with each one of these so<00:17:20.339> that<00:17:20.520> you<00:17:20.640> know<00:17:20.819> exactly<00:17:21.240> what<00:17:21.360> you're 00:17:21.470 --> 00:17:21.480 align:start position:0% so that you know exactly what you're 00:17:21.480 --> 00:17:22.909 align:start position:0% so that you know exactly what you're going<00:17:21.600> to<00:17:21.720> be<00:17:21.780> getting<00:17:21.900> back<00:17:22.140> and<00:17:22.439> exactly<00:17:22.799> how 00:17:22.909 --> 00:17:22.919 align:start position:0% going to be getting back and exactly how 00:17:22.919 --> 00:17:24.949 align:start position:0% going to be getting back and exactly how to<00:17:23.100> get<00:17:23.220> the<00:17:23.400> information<00:17:23.579> that<00:17:24.480> you<00:17:24.600> want<00:17:24.720> in 00:17:24.949 --> 00:17:24.959 align:start position:0% to get the information that you want in 00:17:24.959 --> 00:17:26.030 align:start position:0% to get the information that you want in the<00:17:25.079> future<00:17:25.199> and<00:17:25.620> a<00:17:25.740> lot<00:17:25.860> of<00:17:25.919> your 00:17:26.030 --> 00:17:26.040 align:start position:0% the future and a lot of your 00:17:26.040 --> 00:17:28.189 align:start position:0% the future and a lot of your understanding<00:17:26.579> from<00:17:27.120> these<00:17:27.600> right<00:17:27.780> here<00:17:27.959> is 00:17:28.189 --> 00:17:28.199 align:start position:0% understanding from these right here is 00:17:28.199 --> 00:17:29.630 align:start position:0% understanding from these right here is going<00:17:28.319> to<00:17:28.439> come<00:17:28.559> from<00:17:28.860> playing<00:17:29.220> around<00:17:29.460> with 00:17:29.630 --> 00:17:29.640 align:start position:0% going to come from playing around with 00:17:29.640 --> 00:17:31.370 align:start position:0% going to come from playing around with them<00:17:29.820> and<00:17:30.000> reading<00:17:30.299> the<00:17:30.480> documentation<00:17:31.020> and 00:17:31.370 --> 00:17:31.380 align:start position:0% them and reading the documentation and 00:17:31.380 --> 00:17:33.890 align:start position:0% them and reading the documentation and just<00:17:31.559> pressing<00:17:31.980> the<00:17:32.580> Das<00:17:32.880> h<00:17:33.120> on<00:17:33.419> each<00:17:33.600> one<00:17:33.780> of 00:17:33.890 --> 00:17:33.900 align:start position:0% just pressing the Das h on each one of 00:17:33.900 --> 00:17:36.169 align:start position:0% just pressing the Das h on each one of them<00:17:34.020> and<00:17:34.500> figuring<00:17:34.860> out<00:17:34.980> what<00:17:35.460> exactly<00:17:35.820> they 00:17:36.169 --> 00:17:36.179 align:start position:0% them and figuring out what exactly they 00:17:36.179 --> 00:17:37.730 align:start position:0% them and figuring out what exactly they do<00:17:36.360> it's<00:17:36.539> one<00:17:36.720> of<00:17:36.840> the<00:17:36.900> first<00:17:37.020> ways<00:17:37.320> to<00:17:37.440> check 00:17:37.730 --> 00:17:37.740 align:start position:0% do it's one of the first ways to check 00:17:37.740 --> 00:17:39.890 align:start position:0% do it's one of the first ways to check out<00:17:37.860> showdan<00:17:38.400> is<00:17:38.580> we<00:17:38.700> can<00:17:38.820> just<00:17:38.940> say<00:17:39.120> showdan 00:17:39.890 --> 00:17:39.900 align:start position:0% out showdan is we can just say showdan 00:17:39.900 --> 00:17:42.049 align:start position:0% out showdan is we can just say showdan and<00:17:40.559> then<00:17:40.679> count<00:17:40.980> and<00:17:41.580> then<00:17:41.700> we'll<00:17:41.880> say 00:17:42.049 --> 00:17:42.059 align:start position:0% and then count and then we'll say 00:17:42.059 --> 00:17:44.750 align:start position:0% and then count and then we'll say WordPress<00:17:42.720> and<00:17:43.440> when<00:17:43.679> you<00:17:43.860> run<00:17:44.160> this<00:17:44.400> this 00:17:44.750 --> 00:17:44.760 align:start position:0% WordPress and when you run this this 00:17:44.760 --> 00:17:45.890 align:start position:0% WordPress and when you run this this might<00:17:44.940> not<00:17:45.120> work<00:17:45.240> for<00:17:45.419> me<00:17:45.539> because<00:17:45.660> I<00:17:45.780> don't 00:17:45.890 --> 00:17:45.900 align:start position:0% might not work for me because I don't 00:17:45.900 --> 00:17:47.810 align:start position:0% might not work for me because I don't have<00:17:45.960> any<00:17:46.080> credits<00:17:46.559> but<00:17:47.039> when<00:17:47.280> you<00:17:47.460> run 00:17:47.810 --> 00:17:47.820 align:start position:0% have any credits but when you run 00:17:47.820 --> 00:17:49.669 align:start position:0% have any credits but when you run something<00:17:48.179> like<00:17:48.419> this<00:17:48.600> you<00:17:48.960> can<00:17:49.080> see<00:17:49.260> that<00:17:49.500> we 00:17:49.669 --> 00:17:49.679 align:start position:0% something like this you can see that we 00:17:49.679 --> 00:17:51.289 align:start position:0% something like this you can see that we just<00:17:49.799> want<00:17:49.860> want<00:17:50.280> to<00:17:50.400> count<00:17:50.640> the<00:17:50.940> number<00:17:51.120> of 00:17:51.289 --> 00:17:51.299 align:start position:0% just want want to count the number of 00:17:51.299 --> 00:17:53.270 align:start position:0% just want want to count the number of results<00:17:51.660> for<00:17:51.960> this<00:17:52.140> search<00:17:52.320> so<00:17:52.980> what<00:17:53.100> will 00:17:53.270 --> 00:17:53.280 align:start position:0% results for this search so what will 00:17:53.280 --> 00:17:55.010 align:start position:0% results for this search so what will happen<00:17:53.460> is<00:17:53.760> a<00:17:53.940> showdown<00:17:54.240> will<00:17:54.539> go<00:17:54.660> out<00:17:54.780> and 00:17:55.010 --> 00:17:55.020 align:start position:0% happen is a showdown will go out and 00:17:55.020 --> 00:17:57.350 align:start position:0% happen is a showdown will go out and count<00:17:55.260> all<00:17:55.679> of<00:17:55.919> the<00:17:56.340> servers<00:17:56.760> that<00:17:56.880> it<00:17:57.059> has<00:17:57.179> and 00:17:57.350 --> 00:17:57.360 align:start position:0% count all of the servers that it has and 00:17:57.360 --> 00:17:59.570 align:start position:0% count all of the servers that it has and it's<00:17:57.539> a<00:17:57.720> database<00:17:58.020> that<00:17:58.679> are<00:17:58.919> running<00:17:59.160> this 00:17:59.570 --> 00:17:59.580 align:start position:0% it's a database that are running this 00:17:59.580 --> 00:18:01.310 align:start position:0% it's a database that are running this WordPress<00:18:00.059> right<00:18:00.480> here<00:18:00.600> and<00:18:00.780> it<00:18:00.960> actually<00:18:01.080> did 00:18:01.310 --> 00:18:01.320 align:start position:0% WordPress right here and it actually did 00:18:01.320 --> 00:18:03.830 align:start position:0% WordPress right here and it actually did tell<00:18:01.440> us<00:18:01.559> it<00:18:01.740> tells<00:18:02.039> us<00:18:02.100> it<00:18:02.280> has<00:18:02.400> 52<00:18:02.820> but<00:18:03.360> if<00:18:03.720> you 00:18:03.830 --> 00:18:03.840 align:start position:0% tell us it tells us it has 52 but if you 00:18:03.840 --> 00:18:06.590 align:start position:0% tell us it tells us it has 52 but if you wanted<00:18:04.140> to<00:18:04.580> run<00:18:05.580> something<00:18:06.059> a<00:18:06.299> little<00:18:06.419> more 00:18:06.590 --> 00:18:06.600 align:start position:0% wanted to run something a little more 00:18:06.600 --> 00:18:08.330 align:start position:0% wanted to run something a little more specific<00:18:06.900> I<00:18:07.200> spelled<00:18:07.559> that<00:18:07.620> wrong<00:18:07.799> that<00:18:08.160> makes 00:18:08.330 --> 00:18:08.340 align:start position:0% specific I spelled that wrong that makes 00:18:08.340 --> 00:18:12.409 align:start position:0% specific I spelled that wrong that makes more<00:18:08.580> sense<00:18:08.960> so<00:18:09.960> 500<00:18:10.919> 000<00:18:11.100> so<00:18:11.640> if<00:18:11.880> you<00:18:12.059> were<00:18:12.240> to 00:18:12.409 --> 00:18:12.419 align:start position:0% more sense so 500 000 so if you were to 00:18:12.419 --> 00:18:14.690 align:start position:0% more sense so 500 000 so if you were to run<00:18:12.840> something<00:18:13.080> like<00:18:13.440> this<00:18:13.620> you<00:18:14.460> might<00:18:14.580> want 00:18:14.690 --> 00:18:14.700 align:start position:0% run something like this you might want 00:18:14.700 --> 00:18:16.370 align:start position:0% run something like this you might want to<00:18:14.820> say<00:18:14.940> you're<00:18:15.240> looking<00:18:15.539> for<00:18:15.780> a<00:18:15.960> WordPress 00:18:16.370 --> 00:18:16.380 align:start position:0% to say you're looking for a WordPress 00:18:16.380 --> 00:18:17.470 align:start position:0% to say you're looking for a WordPress version 00:18:17.470 --> 00:18:17.480 align:start position:0% version 00:18:17.480 --> 00:18:20.150 align:start position:0% version 1.4.7<00:18:18.480> because<00:18:18.840> that's<00:18:19.200> what<00:18:19.500> your<00:18:19.620> target<00:18:19.919> is 00:18:20.150 --> 00:18:20.160 align:start position:0% 1.4.7 because that's what your target is 00:18:20.160 --> 00:18:22.549 align:start position:0% 1.4.7 because that's what your target is running<00:18:20.340> or<00:18:20.640> there's<00:18:20.880> maybe<00:18:21.179> a<00:18:21.480> new<00:18:21.660> cve<00:18:22.020> out 00:18:22.549 --> 00:18:22.559 align:start position:0% running or there's maybe a new cve out 00:18:22.559 --> 00:18:25.070 align:start position:0% running or there's maybe a new cve out there<00:18:22.679> and<00:18:23.280> you<00:18:23.460> just<00:18:23.580> want<00:18:23.700> to<00:18:23.880> see<00:18:24.059> okay<00:18:24.480> what 00:18:25.070 --> 00:18:25.080 align:start position:0% there and you just want to see okay what 00:18:25.080 --> 00:18:28.730 align:start position:0% there and you just want to see okay what web<00:18:25.320> apps<00:18:25.679> are<00:18:25.799> running<00:18:25.980> WordPress<00:18:27.020> 1.4.7<00:18:28.020> and 00:18:28.730 --> 00:18:28.740 align:start position:0% web apps are running WordPress 1.4.7 and 00:18:28.740 --> 00:18:30.890 align:start position:0% web apps are running WordPress 1.4.7 and then<00:18:28.919> you'll<00:18:29.340> get<00:18:29.640> Showdown<00:18:30.059> will<00:18:30.360> give<00:18:30.539> you<00:18:30.600> a 00:18:30.890 --> 00:18:30.900 align:start position:0% then you'll get Showdown will give you a 00:18:30.900 --> 00:18:33.230 align:start position:0% then you'll get Showdown will give you a list<00:18:31.080> of<00:18:31.320> those<00:18:31.679> actual<00:18:32.160> web<00:18:32.520> apps<00:18:33.000> that<00:18:33.120> are 00:18:33.230 --> 00:18:33.240 align:start position:0% list of those actual web apps that are 00:18:33.240 --> 00:18:34.970 align:start position:0% list of those actual web apps that are running<00:18:33.419> that<00:18:33.720> and<00:18:34.200> then<00:18:34.260> you<00:18:34.440> can<00:18:34.559> see<00:18:34.679> if<00:18:34.799> any 00:18:34.970 --> 00:18:34.980 align:start position:0% running that and then you can see if any 00:18:34.980 --> 00:18:37.310 align:start position:0% running that and then you can see if any of<00:18:35.100> them<00:18:35.220> have<00:18:35.580> a<00:18:36.000> bug<00:18:36.360> Bounty<00:18:36.840> program<00:18:37.020> and 00:18:37.310 --> 00:18:37.320 align:start position:0% of them have a bug Bounty program and 00:18:37.320 --> 00:18:39.590 align:start position:0% of them have a bug Bounty program and then<00:18:37.500> report<00:18:37.740> to<00:18:38.039> them<00:18:38.160> hey<00:18:38.400> this<00:18:38.700> new<00:18:38.820> cve<00:18:39.179> for 00:18:39.590 --> 00:18:39.600 align:start position:0% then report to them hey this new cve for 00:18:39.600 --> 00:18:41.930 align:start position:0% then report to them hey this new cve for this<00:18:39.900> WordPress<00:18:40.260> has<00:18:40.500> come<00:18:40.740> out<00:18:40.919> so<00:18:41.460> it<00:18:41.700> saves 00:18:41.930 --> 00:18:41.940 align:start position:0% this WordPress has come out so it saves 00:18:41.940 --> 00:18:43.490 align:start position:0% this WordPress has come out so it saves you<00:18:42.059> from<00:18:42.179> having<00:18:42.360> to<00:18:42.539> go<00:18:42.840> out<00:18:42.960> and<00:18:43.320> actually 00:18:43.490 --> 00:18:43.500 align:start position:0% you from having to go out and actually 00:18:43.500 --> 00:18:47.330 align:start position:0% you from having to go out and actually find<00:18:43.919> a<00:18:44.460> specific<00:18:44.940> Target<00:18:45.360> and<00:18:46.320> then<00:18:46.620> looking 00:18:47.330 --> 00:18:47.340 align:start position:0% find a specific Target and then looking 00:18:47.340 --> 00:18:49.070 align:start position:0% find a specific Target and then looking to<00:18:47.580> see<00:18:47.760> what<00:18:48.240> it<00:18:48.419> is<00:18:48.539> running<00:18:48.720> because 00:18:49.070 --> 00:18:49.080 align:start position:0% to see what it is running because 00:18:49.080 --> 00:18:50.870 align:start position:0% to see what it is running because Showdown<00:18:49.500> will<00:18:49.620> actually<00:18:49.799> do<00:18:50.460> the<00:18:50.640> heavy 00:18:50.870 --> 00:18:50.880 align:start position:0% Showdown will actually do the heavy 00:18:50.880 --> 00:18:52.789 align:start position:0% Showdown will actually do the heavy lifting<00:18:51.179> for<00:18:51.360> you<00:18:51.480> and<00:18:52.020> so<00:18:52.260> all<00:18:52.440> you<00:18:52.559> have<00:18:52.679> to 00:18:52.789 --> 00:18:52.799 align:start position:0% lifting for you and so all you have to 00:18:52.799 --> 00:18:55.190 align:start position:0% lifting for you and so all you have to do<00:18:52.980> if<00:18:53.460> you<00:18:53.640> are<00:18:53.760> a<00:18:53.820> bug<00:18:53.940> Bounty<00:18:54.360> Hunter<00:18:54.480> is<00:18:54.960> say 00:18:55.190 --> 00:18:55.200 align:start position:0% do if you are a bug Bounty Hunter is say 00:18:55.200 --> 00:18:56.810 align:start position:0% do if you are a bug Bounty Hunter is say this<00:18:55.500> is<00:18:55.559> the<00:18:55.740> version<00:18:55.860> the<00:18:56.160> brand<00:18:56.340> new<00:18:56.460> cve 00:18:56.810 --> 00:18:56.820 align:start position:0% this is the version the brand new cve 00:18:56.820 --> 00:18:58.430 align:start position:0% this is the version the brand new cve has<00:18:57.179> come<00:18:57.299> out<00:18:57.419> for<00:18:57.539> it<00:18:57.720> so<00:18:57.900> you<00:18:58.080> would<00:18:58.260> say 00:18:58.430 --> 00:18:58.440 align:start position:0% has come out for it so you would say 00:18:58.440 --> 00:19:01.490 align:start position:0% has come out for it so you would say Showdown<00:18:59.780> 1.4.7<00:19:00.780> which<00:19:01.020> I<00:19:01.200> actually<00:19:01.320> don't 00:19:01.490 --> 00:19:01.500 align:start position:0% Showdown 1.4.7 which I actually don't 00:19:01.500 --> 00:19:03.470 align:start position:0% Showdown 1.4.7 which I actually don't even<00:19:01.679> know<00:19:01.860> if<00:19:02.100> this<00:19:02.280> is<00:19:02.400> a<00:19:02.580> real<00:19:02.700> version<00:19:02.940> you 00:19:03.470 --> 00:19:03.480 align:start position:0% even know if this is a real version you 00:19:03.480 --> 00:19:05.930 align:start position:0% even know if this is a real version you would<00:19:03.660> run<00:19:03.840> this<00:19:04.080> and<00:19:04.440> it<00:19:04.620> is<00:19:04.799> and<00:19:05.520> you<00:19:05.820> would 00:19:05.930 --> 00:19:05.940 align:start position:0% would run this and it is and you would 00:19:05.940 --> 00:19:08.090 align:start position:0% would run this and it is and you would say<00:19:06.120> okay<00:19:06.240> there's<00:19:06.660> seven<00:19:07.020> web<00:19:07.500> apps<00:19:07.860> that<00:19:07.980> are 00:19:08.090 --> 00:19:08.100 align:start position:0% say okay there's seven web apps that are 00:19:08.100 --> 00:19:10.730 align:start position:0% say okay there's seven web apps that are running<00:19:08.280> this<00:19:08.760> version<00:19:08.940> currently<00:19:09.900> in<00:19:10.380> The 00:19:10.730 --> 00:19:10.740 align:start position:0% running this version currently in The 00:19:10.740 --> 00:19:12.710 align:start position:0% running this version currently in The Showdown<00:19:11.220> database<00:19:11.820> and<00:19:12.360> then<00:19:12.419> you<00:19:12.600> would 00:19:12.710 --> 00:19:12.720 align:start position:0% Showdown database and then you would 00:19:12.720 --> 00:19:14.870 align:start position:0% Showdown database and then you would just<00:19:12.900> go<00:19:13.080> out<00:19:13.260> and<00:19:13.799> look<00:19:14.100> to<00:19:14.220> see<00:19:14.400> if<00:19:14.520> any<00:19:14.700> of 00:19:14.870 --> 00:19:14.880 align:start position:0% just go out and look to see if any of 00:19:14.880 --> 00:19:16.610 align:start position:0% just go out and look to see if any of these<00:19:15.059> seven<00:19:15.179> have<00:19:15.600> a<00:19:15.840> bug<00:19:16.020> Bounty<00:19:16.500> program 00:19:16.610 --> 00:19:16.620 align:start position:0% these seven have a bug Bounty program 00:19:16.620 --> 00:19:18.590 align:start position:0% these seven have a bug Bounty program and<00:19:16.860> if<00:19:17.039> they<00:19:17.160> do<00:19:17.280> you<00:19:17.580> can<00:19:17.700> report<00:19:17.880> hey<00:19:18.299> the 00:19:18.590 --> 00:19:18.600 align:start position:0% and if they do you can report hey the 00:19:18.600 --> 00:19:21.289 align:start position:0% and if they do you can report hey the cve<00:19:18.960> came<00:19:19.320> out<00:19:19.500> and<00:19:20.160> You're<00:19:20.340> vulnerable<00:19:20.700> to<00:19:21.120> it 00:19:21.289 --> 00:19:21.299 align:start position:0% cve came out and You're vulnerable to it 00:19:21.299 --> 00:19:23.390 align:start position:0% cve came out and You're vulnerable to it and<00:19:21.720> so<00:19:21.840> that's<00:19:22.020> a<00:19:22.260> really<00:19:22.440> simple<00:19:22.740> way<00:19:23.160> to 00:19:23.390 --> 00:19:23.400 align:start position:0% and so that's a really simple way to 00:19:23.400 --> 00:19:25.850 align:start position:0% and so that's a really simple way to find<00:19:23.760> bugs<00:19:24.179> and<00:19:24.539> it's<00:19:24.720> all<00:19:25.080> based<00:19:25.440> on<00:19:25.500> recon 00:19:25.850 --> 00:19:25.860 align:start position:0% find bugs and it's all based on recon 00:19:25.860 --> 00:19:27.289 align:start position:0% find bugs and it's all based on recon and<00:19:26.100> you<00:19:26.220> really<00:19:26.340> don't<00:19:26.520> have<00:19:26.700> to<00:19:26.820> do<00:19:27.000> any 00:19:27.289 --> 00:19:27.299 align:start position:0% and you really don't have to do any 00:19:27.299 --> 00:19:29.330 align:start position:0% and you really don't have to do any heavy<00:19:27.600> lifting<00:19:27.960> very<00:19:28.620> simple<00:19:28.799> you've<00:19:29.220> seen 00:19:29.330 --> 00:19:29.340 align:start position:0% heavy lifting very simple you've seen 00:19:29.340 --> 00:19:31.789 align:start position:0% heavy lifting very simple you've seen how<00:19:29.820> fast<00:19:30.120> this<00:19:30.419> has<00:19:30.600> gone<00:19:30.780> and<00:19:31.380> you<00:19:31.620> could 00:19:31.789 --> 00:19:31.799 align:start position:0% how fast this has gone and you could 00:19:31.799 --> 00:19:34.190 align:start position:0% how fast this has gone and you could potentially<00:19:32.280> have<00:19:32.580> found<00:19:32.940> a<00:19:33.120> bug<00:19:33.299> if<00:19:33.840> this 00:19:34.190 --> 00:19:34.200 align:start position:0% potentially have found a bug if this 00:19:34.200 --> 00:19:36.950 align:start position:0% potentially have found a bug if this version<00:19:34.500> were<00:19:34.980> vulnerable<00:19:35.520> to<00:19:35.880> a<00:19:36.240> cve<00:19:36.600> that 00:19:36.950 --> 00:19:36.960 align:start position:0% version were vulnerable to a cve that 00:19:36.960 --> 00:19:38.390 align:start position:0% version were vulnerable to a cve that had<00:19:37.080> just<00:19:37.320> come<00:19:37.500> out<00:19:37.679> so<00:19:37.860> if<00:19:37.980> you're<00:19:38.100> familiar 00:19:38.390 --> 00:19:38.400 align:start position:0% had just come out so if you're familiar 00:19:38.400 --> 00:19:40.130 align:start position:0% had just come out so if you're familiar with<00:19:38.520> nmap<00:19:39.000> what<00:19:39.179> Showdown<00:19:39.480> does<00:19:39.780> is<00:19:39.960> pretty 00:19:40.130 --> 00:19:40.140 align:start position:0% with nmap what Showdown does is pretty 00:19:40.140 --> 00:19:41.990 align:start position:0% with nmap what Showdown does is pretty similar<00:19:40.440> it<00:19:40.860> goes<00:19:41.100> out<00:19:41.160> scans<00:19:41.640> the<00:19:41.820> network 00:19:41.990 --> 00:19:42.000 align:start position:0% similar it goes out scans the network 00:19:42.000 --> 00:19:44.029 align:start position:0% similar it goes out scans the network and<00:19:42.299> it<00:19:42.480> pulls<00:19:42.900> all<00:19:43.080> of<00:19:43.200> the<00:19:43.380> internet<00:19:43.500> and 00:19:44.029 --> 00:19:44.039 align:start position:0% and it pulls all of the internet and 00:19:44.039 --> 00:19:46.549 align:start position:0% and it pulls all of the internet and pulls<00:19:44.400> the<00:19:44.520> banners<00:19:44.880> the<00:19:45.120> versions<00:19:45.559> what's 00:19:46.549 --> 00:19:46.559 align:start position:0% pulls the banners the versions what's 00:19:46.559 --> 00:19:48.470 align:start position:0% pulls the banners the versions what's running<00:19:46.799> if<00:19:47.160> it's<00:19:47.280> Apache<00:19:47.760> if<00:19:47.940> it's<00:19:48.120> Windows 00:19:48.470 --> 00:19:48.480 align:start position:0% running if it's Apache if it's Windows 00:19:48.480 --> 00:19:50.750 align:start position:0% running if it's Apache if it's Windows if<00:19:48.660> it's<00:19:48.840> got<00:19:49.020> WordPress<00:19:49.380> running<00:19:49.980> and<00:19:50.580> what 00:19:50.750 --> 00:19:50.760 align:start position:0% if it's got WordPress running and what 00:19:50.760 --> 00:19:52.970 align:start position:0% if it's got WordPress running and what ports<00:19:51.120> are<00:19:51.240> open<00:19:51.419> and<00:19:51.840> so<00:19:52.020> with<00:19:52.260> Showdown<00:19:52.620> we 00:19:52.970 --> 00:19:52.980 align:start position:0% ports are open and so with Showdown we 00:19:52.980 --> 00:19:54.830 align:start position:0% ports are open and so with Showdown we can<00:19:53.100> just<00:19:53.340> query<00:19:53.760> all<00:19:54.000> of<00:19:54.120> this<00:19:54.240> and<00:19:54.480> it<00:19:54.660> stores 00:19:54.830 --> 00:19:54.840 align:start position:0% can just query all of this and it stores 00:19:54.840 --> 00:19:56.330 align:start position:0% can just query all of this and it stores this<00:19:55.080> in<00:19:55.260> the<00:19:55.380> database<00:19:55.679> and<00:19:55.860> that's<00:19:56.039> how<00:19:56.160> it 00:19:56.330 --> 00:19:56.340 align:start position:0% this in the database and that's how it 00:19:56.340 --> 00:19:59.150 align:start position:0% this in the database and that's how it already<00:19:56.520> knows<00:19:56.940> that<00:19:57.480> there<00:19:57.840> is<00:19:58.020> seven<00:19:58.620> web 00:19:59.150 --> 00:19:59.160 align:start position:0% already knows that there is seven web 00:19:59.160 --> 00:20:01.669 align:start position:0% already knows that there is seven web apps<00:19:59.520> running<00:19:59.820> this<00:20:00.120> WordPress<00:20:00.679> 1.4.7 00:20:01.669 --> 00:20:01.679 align:start position:0% apps running this WordPress 1.4.7 00:20:01.679 --> 00:20:04.310 align:start position:0% apps running this WordPress 1.4.7 because<00:20:02.460> it<00:20:03.120> is<00:20:03.240> already<00:20:03.419> all<00:20:03.840> it<00:20:03.960> has<00:20:04.080> to<00:20:04.200> do 00:20:04.310 --> 00:20:04.320 align:start position:0% because it is already all it has to do 00:20:04.320 --> 00:20:06.110 align:start position:0% because it is already all it has to do is<00:20:04.559> check<00:20:04.860> its<00:20:05.280> database<00:20:05.640> and<00:20:05.880> it<00:20:06.000> doesn't 00:20:06.110 --> 00:20:06.120 align:start position:0% is check its database and it doesn't 00:20:06.120 --> 00:20:07.850 align:start position:0% is check its database and it doesn't actually<00:20:06.299> have<00:20:06.419> to<00:20:06.539> go<00:20:06.720> out<00:20:06.840> and<00:20:07.020> scan<00:20:07.320> but 00:20:07.850 --> 00:20:07.860 align:start position:0% actually have to go out and scan but 00:20:07.860 --> 00:20:10.970 align:start position:0% actually have to go out and scan but showed<00:20:08.340> but<00:20:08.580> we<00:20:08.760> can<00:20:09.000> scan<00:20:09.600> with<00:20:09.960> showdan<00:20:10.500> and 00:20:10.970 --> 00:20:10.980 align:start position:0% showed but we can scan with showdan and 00:20:10.980 --> 00:20:12.529 align:start position:0% showed but we can scan with showdan and we're<00:20:11.100> going<00:20:11.220> to<00:20:11.280> look<00:20:11.400> at<00:20:11.520> this<00:20:11.760> in<00:20:12.179> a<00:20:12.360> little 00:20:12.529 --> 00:20:12.539 align:start position:0% we're going to look at this in a little 00:20:12.539 --> 00:20:14.510 align:start position:0% we're going to look at this in a little bit<00:20:12.720> but<00:20:13.200> I<00:20:13.320> just<00:20:13.440> want<00:20:13.559> you<00:20:13.679> to<00:20:13.799> know<00:20:13.980> how 00:20:14.510 --> 00:20:14.520 align:start position:0% bit but I just want you to know how 00:20:14.520 --> 00:20:17.210 align:start position:0% bit but I just want you to know how Showdown<00:20:15.000> works<00:20:15.480> and<00:20:15.780> it<00:20:15.960> already<00:20:16.140> has<00:20:16.559> stored 00:20:17.210 --> 00:20:17.220 align:start position:0% Showdown works and it already has stored 00:20:17.220 --> 00:20:19.070 align:start position:0% Showdown works and it already has stored all<00:20:17.460> of<00:20:17.580> this<00:20:17.760> information<00:20:17.940> on<00:20:18.360> there<00:20:18.600> so<00:20:18.900> now 00:20:19.070 --> 00:20:19.080 align:start position:0% all of this information on there so now 00:20:19.080 --> 00:20:21.770 align:start position:0% all of this information on there so now you<00:20:19.260> can<00:20:19.380> see<00:20:19.559> how<00:20:19.919> this<00:20:20.400> is<00:20:20.700> kind<00:20:21.120> of<00:20:21.240> a<00:20:21.539> go-to 00:20:21.770 --> 00:20:21.780 align:start position:0% you can see how this is kind of a go-to 00:20:21.780 --> 00:20:24.650 align:start position:0% you can see how this is kind of a go-to tool<00:20:22.260> for<00:20:22.559> the<00:20:23.039> black<00:20:23.340> hat<00:20:23.580> hackers<00:20:24.059> because 00:20:24.650 --> 00:20:24.660 align:start position:0% tool for the black hat hackers because 00:20:24.660 --> 00:20:26.990 align:start position:0% tool for the black hat hackers because they<00:20:25.140> don't<00:20:25.260> really<00:20:25.380> care<00:20:25.679> if<00:20:26.220> these<00:20:26.700> seven 00:20:26.990 --> 00:20:27.000 align:start position:0% they don't really care if these seven 00:20:27.000 --> 00:20:29.870 align:start position:0% they don't really care if these seven web<00:20:27.539> applications<00:20:28.080> have<00:20:28.860> a<00:20:29.280> bug<00:20:29.460> Bounty 00:20:29.870 --> 00:20:29.880 align:start position:0% web applications have a bug Bounty 00:20:29.880 --> 00:20:31.310 align:start position:0% web applications have a bug Bounty program<00:20:30.059> or<00:20:30.299> not<00:20:30.480> they<00:20:30.720> just<00:20:30.900> are<00:20:31.020> going<00:20:31.200> to 00:20:31.310 --> 00:20:31.320 align:start position:0% program or not they just are going to 00:20:31.320 --> 00:20:32.810 align:start position:0% program or not they just are going to attack<00:20:31.440> it<00:20:31.679> and<00:20:31.919> see<00:20:32.039> what<00:20:32.220> information<00:20:32.400> they 00:20:32.810 --> 00:20:32.820 align:start position:0% attack it and see what information they 00:20:32.820 --> 00:20:34.070 align:start position:0% attack it and see what information they can<00:20:32.940> get<00:20:33.059> out<00:20:33.179> because<00:20:33.419> they<00:20:33.840> don't<00:20:33.960> really 00:20:34.070 --> 00:20:34.080 align:start position:0% can get out because they don't really 00:20:34.080 --> 00:20:37.310 align:start position:0% can get out because they don't really care<00:20:34.320> about<00:20:34.440> following<00:20:34.980> the<00:20:35.700> legal<00:20:36.240> rules<00:20:37.080> and 00:20:37.310 --> 00:20:37.320 align:start position:0% care about following the legal rules and 00:20:37.320 --> 00:20:39.590 align:start position:0% care about following the legal rules and the<00:20:37.500> law<00:20:37.620> but<00:20:38.340> as<00:20:38.520> a<00:20:38.640> bug<00:20:38.760> Bounty<00:20:39.179> Hunter<00:20:39.299> you 00:20:39.590 --> 00:20:39.600 align:start position:0% the law but as a bug Bounty Hunter you 00:20:39.600 --> 00:20:41.450 align:start position:0% the law but as a bug Bounty Hunter you need<00:20:39.780> to<00:20:39.900> make<00:20:40.020> sure<00:20:40.200> that<00:20:40.559> these<00:20:40.919> seven<00:20:41.160> web 00:20:41.450 --> 00:20:41.460 align:start position:0% need to make sure that these seven web 00:20:41.460 --> 00:20:44.029 align:start position:0% need to make sure that these seven web apps<00:20:41.760> if<00:20:42.059> they<00:20:42.240> were<00:20:42.360> vulnerable<00:20:42.780> to<00:20:43.200> a<00:20:43.679> cve 00:20:44.029 --> 00:20:44.039 align:start position:0% apps if they were vulnerable to a cve 00:20:44.039 --> 00:20:47.150 align:start position:0% apps if they were vulnerable to a cve they<00:20:44.700> could<00:20:44.880> attack<00:20:45.000> WordPress<00:20:45.480> 1.4.7<00:20:46.440> you 00:20:47.150 --> 00:20:47.160 align:start position:0% they could attack WordPress 1.4.7 you 00:20:47.160 --> 00:20:48.409 align:start position:0% they could attack WordPress 1.4.7 you would<00:20:47.340> want<00:20:47.520> to<00:20:47.700> make<00:20:48.000> sure<00:20:48.120> you<00:20:48.299> do 00:20:48.409 --> 00:20:48.419 align:start position:0% would want to make sure you do 00:20:48.419 --> 00:20:50.270 align:start position:0% would want to make sure you do everything<00:20:48.600> legally<00:20:49.260> that<00:20:49.620> you<00:20:49.740> act<00:20:49.919> actually 00:20:50.270 --> 00:20:50.280 align:start position:0% everything legally that you act actually 00:20:50.280 --> 00:20:52.850 align:start position:0% everything legally that you act actually don't<00:20:50.580> exploit<00:20:51.059> the<00:20:51.299> cve<00:20:51.600> there's<00:20:52.080> no<00:20:52.320> need<00:20:52.559> to 00:20:52.850 --> 00:20:52.860 align:start position:0% don't exploit the cve there's no need to 00:20:52.860 --> 00:20:54.710 align:start position:0% don't exploit the cve there's no need to actually<00:20:52.980> go<00:20:53.280> and<00:20:53.460> try<00:20:53.640> and<00:20:53.760> exploit<00:20:54.179> it<00:20:54.299> you 00:20:54.710 --> 00:20:54.720 align:start position:0% actually go and try and exploit it you 00:20:54.720 --> 00:20:56.750 align:start position:0% actually go and try and exploit it you can<00:20:54.780> just<00:20:54.960> report<00:20:55.200> it<00:20:55.500> hey<00:20:55.860> there's<00:20:56.280> the<00:20:56.460> cve 00:20:56.750 --> 00:20:56.760 align:start position:0% can just report it hey there's the cve 00:20:56.760 --> 00:20:59.390 align:start position:0% can just report it hey there's the cve that<00:20:57.059> came<00:20:57.179> out<00:20:57.299> and<00:20:57.960> you<00:20:58.260> are<00:20:58.380> vulnerable<00:20:58.860> and 00:20:59.390 --> 00:20:59.400 align:start position:0% that came out and you are vulnerable and 00:20:59.400 --> 00:21:01.490 align:start position:0% that came out and you are vulnerable and you<00:20:59.640> should<00:20:59.820> be<00:21:00.059> rewarded<00:21:00.600> for<00:21:00.780> it<00:21:00.900> and<00:21:01.140> so<00:21:01.320> as 00:21:01.490 --> 00:21:01.500 align:start position:0% you should be rewarded for it and so as 00:21:01.500 --> 00:21:03.350 align:start position:0% you should be rewarded for it and so as a<00:21:01.799> Bug<00:21:01.980> Hunter<00:21:02.220> and<00:21:02.460> a<00:21:02.580> penetration<00:21:02.880> tester 00:21:03.350 --> 00:21:03.360 align:start position:0% a Bug Hunter and a penetration tester 00:21:03.360 --> 00:21:06.049 align:start position:0% a Bug Hunter and a penetration tester we're<00:21:03.780> looking<00:21:04.020> for<00:21:04.500> very<00:21:04.919> specific<00:21:05.460> targets 00:21:06.049 --> 00:21:06.059 align:start position:0% we're looking for very specific targets 00:21:06.059 --> 00:21:07.850 align:start position:0% we're looking for very specific targets and<00:21:06.299> then<00:21:06.419> we<00:21:06.660> can<00:21:06.840> just<00:21:07.020> run<00:21:07.260> through<00:21:07.440> these 00:21:07.850 --> 00:21:07.860 align:start position:0% and then we can just run through these 00:21:07.860 --> 00:21:09.890 align:start position:0% and then we can just run through these seven<00:21:08.039> real<00:21:08.280> quick<00:21:08.460> and<00:21:08.760> see<00:21:09.000> who<00:21:09.299> actually<00:21:09.600> is 00:21:09.890 --> 00:21:09.900 align:start position:0% seven real quick and see who actually is 00:21:09.900 --> 00:21:12.110 align:start position:0% seven real quick and see who actually is vulnerable<00:21:10.500> so<00:21:10.860> now<00:21:11.039> if<00:21:11.340> we<00:21:11.580> actually<00:21:11.700> want<00:21:12.000> to 00:21:12.110 --> 00:21:12.120 align:start position:0% vulnerable so now if we actually want to 00:21:12.120 --> 00:21:14.210 align:start position:0% vulnerable so now if we actually want to see<00:21:12.360> what<00:21:12.780> these<00:21:13.200> seven<00:21:13.440> web<00:21:13.740> applications 00:21:14.210 --> 00:21:14.220 align:start position:0% see what these seven web applications 00:21:14.220 --> 00:21:15.830 align:start position:0% see what these seven web applications are<00:21:14.580> that<00:21:14.820> are<00:21:14.940> running<00:21:15.059> this<00:21:15.360> WordPress 00:21:15.830 --> 00:21:15.840 align:start position:0% are that are running this WordPress 00:21:15.840 --> 00:21:18.669 align:start position:0% are that are running this WordPress right<00:21:16.200> here<00:21:16.380> we<00:21:17.039> can<00:21:17.160> use<00:21:17.400> the<00:21:18.000> download 00:21:18.669 --> 00:21:18.679 align:start position:0% right here we can use the download 00:21:18.679 --> 00:21:21.950 align:start position:0% right here we can use the download feature<00:21:19.679> within<00:21:20.160> showdan<00:21:20.700> now<00:21:21.059> I<00:21:21.480> personally 00:21:21.950 --> 00:21:21.960 align:start position:0% feature within showdan now I personally 00:21:21.960 --> 00:21:24.049 align:start position:0% feature within showdan now I personally if<00:21:22.260> I<00:21:22.440> was<00:21:22.559> attacking<00:21:23.039> a<00:21:23.400> specific<00:21:23.820> Target 00:21:24.049 --> 00:21:24.059 align:start position:0% if I was attacking a specific Target 00:21:24.059 --> 00:21:26.330 align:start position:0% if I was attacking a specific Target would<00:21:24.480> just<00:21:24.660> run<00:21:24.840> in<00:21:25.140> map<00:21:25.380> instead<00:21:25.919> of<00:21:26.039> using 00:21:26.330 --> 00:21:26.340 align:start position:0% would just run in map instead of using 00:21:26.340 --> 00:21:28.669 align:start position:0% would just run in map instead of using showdan<00:21:26.940> for<00:21:27.299> this<00:21:27.480> but<00:21:28.020> I<00:21:28.200> want<00:21:28.260> you<00:21:28.380> to<00:21:28.559> be 00:21:28.669 --> 00:21:28.679 align:start position:0% showdan for this but I want you to be 00:21:28.679 --> 00:21:30.409 align:start position:0% showdan for this but I want you to be aware<00:21:29.039> that<00:21:29.280> you<00:21:29.460> can<00:21:29.580> actually<00:21:29.760> pull<00:21:30.179> down 00:21:30.409 --> 00:21:30.419 align:start position:0% aware that you can actually pull down 00:21:30.419 --> 00:21:33.350 align:start position:0% aware that you can actually pull down version<00:21:30.840> numbers<00:21:31.140> of<00:21:31.679> web<00:21:31.980> apps<00:21:32.340> with<00:21:32.760> showdan 00:21:33.350 --> 00:21:33.360 align:start position:0% version numbers of web apps with showdan 00:21:33.360 --> 00:21:35.990 align:start position:0% version numbers of web apps with showdan itself<00:21:33.780> but<00:21:34.440> personally<00:21:34.919> I<00:21:35.220> would<00:21:35.280> run<00:21:35.460> nmap 00:21:35.990 --> 00:21:36.000 align:start position:0% itself but personally I would run nmap 00:21:36.000 --> 00:21:37.970 align:start position:0% itself but personally I would run nmap just<00:21:36.419> to<00:21:36.659> grab<00:21:37.020> the<00:21:37.200> banners<00:21:37.500> in<00:21:37.679> the<00:21:37.860> version 00:21:37.970 --> 00:21:37.980 align:start position:0% just to grab the banners in the version 00:21:37.980 --> 00:21:40.370 align:start position:0% just to grab the banners in the version of<00:21:38.400> a<00:21:38.760> specific<00:21:39.120> Target<00:21:39.360> this<00:21:40.080> is<00:21:40.140> something 00:21:40.370 --> 00:21:40.380 align:start position:0% of a specific Target this is something 00:21:40.380 --> 00:21:42.230 align:start position:0% of a specific Target this is something that<00:21:40.799> you<00:21:40.919> would<00:21:41.039> be<00:21:41.159> using<00:21:41.400> if<00:21:41.700> you<00:21:41.880> were<00:21:42.000> just 00:21:42.230 --> 00:21:42.240 align:start position:0% that you would be using if you were just 00:21:42.240 --> 00:21:44.149 align:start position:0% that you would be using if you were just looking<00:21:42.600> for<00:21:42.900> a<00:21:43.080> cve<00:21:43.380> that<00:21:43.740> just<00:21:43.860> came<00:21:43.980> out 00:21:44.149 --> 00:21:44.159 align:start position:0% looking for a cve that just came out 00:21:44.159 --> 00:21:45.409 align:start position:0% looking for a cve that just came out like<00:21:44.340> we<00:21:44.520> were<00:21:44.700> previously<00:21:45.059> talking<00:21:45.240> about 00:21:45.409 --> 00:21:45.419 align:start position:0% like we were previously talking about 00:21:45.419 --> 00:21:47.990 align:start position:0% like we were previously talking about and<00:21:46.320> we<00:21:46.500> would<00:21:46.620> use<00:21:46.799> the<00:21:47.100> download<00:21:47.400> function 00:21:47.990 --> 00:21:48.000 align:start position:0% and we would use the download function 00:21:48.000 --> 00:21:49.850 align:start position:0% and we would use the download function for<00:21:48.360> this<00:21:48.539> so<00:21:48.960> we<00:21:49.140> would<00:21:49.260> just<00:21:49.440> grab<00:21:49.620> show 00:21:49.850 --> 00:21:49.860 align:start position:0% for this so we would just grab show 00:21:49.860 --> 00:21:52.909 align:start position:0% for this so we would just grab show showed<00:21:50.460> in<00:21:50.640> and<00:21:51.240> then<00:21:51.419> we<00:21:51.659> would<00:21:51.780> say<00:21:52.140> download 00:21:52.909 --> 00:21:52.919 align:start position:0% showed in and then we would say download 00:21:52.919 --> 00:21:55.490 align:start position:0% showed in and then we would say download and<00:21:53.820> then<00:21:53.940> we're<00:21:54.240> going<00:21:54.360> to<00:21:54.480> download<00:21:54.720> the 00:21:55.490 --> 00:21:55.500 align:start position:0% and then we're going to download the 00:21:55.500 --> 00:22:00.649 align:start position:0% and then we're going to download the file<00:21:56.240> as<00:21:57.240> let's<00:21:57.780> say<00:21:57.960> WordPress<00:21:58.799> file 00:22:00.649 --> 00:22:00.659 align:start position:0% file as let's say WordPress file 00:22:00.659 --> 00:22:02.450 align:start position:0% file as let's say WordPress file and<00:22:01.140> I'm<00:22:01.380> not<00:22:01.559> actually<00:22:01.799> sure<00:22:02.039> if<00:22:02.220> it<00:22:02.340> will 00:22:02.450 --> 00:22:02.460 align:start position:0% and I'm not actually sure if it will 00:22:02.460 --> 00:22:03.950 align:start position:0% and I'm not actually sure if it will work<00:22:02.640> with<00:22:02.940> this<00:22:03.059> version<00:22:03.240> number<00:22:03.539> I've<00:22:03.780> only 00:22:03.950 --> 00:22:03.960 align:start position:0% work with this version number I've only 00:22:03.960 --> 00:22:05.570 align:start position:0% work with this version number I've only ever<00:22:04.140> ran<00:22:04.559> it<00:22:04.740> without<00:22:04.860> the<00:22:05.159> version<00:22:05.280> number 00:22:05.570 --> 00:22:05.580 align:start position:0% ever ran it without the version number 00:22:05.580 --> 00:22:08.750 align:start position:0% ever ran it without the version number so<00:22:06.360> maybe<00:22:06.659> we<00:22:07.020> can<00:22:07.260> throw<00:22:07.799> this<00:22:08.159> inside<00:22:08.460> of 00:22:08.750 --> 00:22:08.760 align:start position:0% so maybe we can throw this inside of 00:22:08.760 --> 00:22:11.270 align:start position:0% so maybe we can throw this inside of quotes<00:22:09.000> and<00:22:09.780> see<00:22:09.960> if<00:22:10.080> this<00:22:10.260> works<00:22:10.500> if<00:22:10.740> not<00:22:10.919> we 00:22:11.270 --> 00:22:11.280 align:start position:0% quotes and see if this works if not we 00:22:11.280 --> 00:22:12.950 align:start position:0% quotes and see if this works if not we will<00:22:11.460> just<00:22:11.640> run<00:22:11.880> it<00:22:12.059> without<00:22:12.179> quotes<00:22:12.480> and<00:22:12.780> see 00:22:12.950 --> 00:22:12.960 align:start position:0% will just run it without quotes and see 00:22:12.960 --> 00:22:16.789 align:start position:0% will just run it without quotes and see how<00:22:13.140> that<00:22:13.320> runs<00:22:13.679> so<00:22:13.980> we'll<00:22:14.100> run<00:22:14.400> this 00:22:16.789 --> 00:22:16.799 align:start position:0% 00:22:16.799 --> 00:22:20.210 align:start position:0% and<00:22:17.580> it<00:22:17.820> has<00:22:18.059> saved<00:22:18.600> Five<00:22:18.780> results<00:22:19.080> into<00:22:19.679> our 00:22:20.210 --> 00:22:20.220 align:start position:0% and it has saved Five results into our 00:22:20.220 --> 00:22:24.169 align:start position:0% and it has saved Five results into our WordPress<00:22:20.700> Json<00:22:21.299> file<00:22:21.840> dot<00:22:22.679> gz<00:22:23.039> and<00:22:23.700> we<00:22:24.000> can 00:22:24.169 --> 00:22:24.179 align:start position:0% WordPress Json file dot gz and we can 00:22:24.179 --> 00:22:26.810 align:start position:0% WordPress Json file dot gz and we can unzip<00:22:24.840> this<00:22:25.080> and<00:22:25.440> grab<00:22:25.799> the<00:22:25.919> file<00:22:26.159> by<00:22:26.460> typing 00:22:26.810 --> 00:22:26.820 align:start position:0% unzip this and grab the file by typing 00:22:26.820 --> 00:22:30.529 align:start position:0% unzip this and grab the file by typing in<00:22:27.000> a<00:22:27.299> g<00:22:27.799> unzip<00:22:28.799> and<00:22:29.460> then<00:22:29.520> we<00:22:29.760> want<00:22:29.880> to<00:22:30.000> run<00:22:30.240> our 00:22:30.529 --> 00:22:30.539 align:start position:0% in a g unzip and then we want to run our 00:22:30.539 --> 00:22:33.409 align:start position:0% in a g unzip and then we want to run our WordPress<00:22:30.960> file<00:22:31.380> and<00:22:31.919> then<00:22:31.980> if<00:22:32.159> we<00:22:32.280> LS<00:22:32.700> we 00:22:33.409 --> 00:22:33.419 align:start position:0% WordPress file and then if we LS we 00:22:33.419 --> 00:22:36.710 align:start position:0% WordPress file and then if we LS we should<00:22:33.659> have<00:22:34.020> our<00:22:34.380> WordPress<00:22:34.740> file.json<00:22:35.720> and 00:22:36.710 --> 00:22:36.720 align:start position:0% should have our WordPress file.json and 00:22:36.720 --> 00:22:38.750 align:start position:0% should have our WordPress file.json and I<00:22:37.080> do<00:22:37.260> not<00:22:37.380> have<00:22:37.500> G<00:22:37.740> edit<00:22:38.100> installed<00:22:38.580> because 00:22:38.750 --> 00:22:38.760 align:start position:0% I do not have G edit installed because 00:22:38.760 --> 00:22:40.430 align:start position:0% I do not have G edit installed because this<00:22:39.059> is<00:22:39.179> a<00:22:39.299> new<00:22:39.419> machine<00:22:39.659> and<00:22:39.900> if<00:22:40.080> you<00:22:40.200> don't 00:22:40.430 --> 00:22:40.440 align:start position:0% this is a new machine and if you don't 00:22:40.440 --> 00:22:42.529 align:start position:0% this is a new machine and if you don't have<00:22:40.559> G<00:22:40.799> edit<00:22:41.159> installed<00:22:41.520> either<00:22:41.700> you<00:22:42.419> can 00:22:42.529 --> 00:22:42.539 align:start position:0% have G edit installed either you can 00:22:42.539 --> 00:22:45.350 align:start position:0% have G edit installed either you can sudo<00:22:43.080> apt<00:22:43.380> update<00:22:43.799> and<00:22:44.340> I've<00:22:44.580> already<00:22:44.760> done<00:22:45.120> a 00:22:45.350 --> 00:22:45.360 align:start position:0% sudo apt update and I've already done a 00:22:45.360 --> 00:22:48.409 align:start position:0% sudo apt update and I've already done a sudo<00:22:45.720> apt<00:22:46.020> update<00:22:46.440> recently<00:22:47.220> so<00:22:47.880> I'm<00:22:48.059> going<00:22:48.299> to 00:22:48.409 --> 00:22:48.419 align:start position:0% sudo apt update recently so I'm going to 00:22:48.419 --> 00:22:52.250 align:start position:0% sudo apt update recently so I'm going to sudo<00:22:49.080> apt<00:22:49.620> install<00:22:50.299> G<00:22:51.299> edit<00:22:51.659> and<00:22:51.960> this<00:22:52.140> will 00:22:52.250 --> 00:22:52.260 align:start position:0% sudo apt install G edit and this will 00:22:52.260 --> 00:22:54.590 align:start position:0% sudo apt install G edit and this will only<00:22:52.380> take<00:22:52.679> a<00:22:52.980> second<00:22:53.220> to<00:22:53.520> download<00:22:53.700> and<00:22:54.419> now 00:22:54.590 --> 00:22:54.600 align:start position:0% only take a second to download and now 00:22:54.600 --> 00:22:57.590 align:start position:0% only take a second to download and now we<00:22:54.900> can<00:22:55.080> G<00:22:55.440> edit<00:22:55.860> our<00:22:56.280> WordPress<00:22:56.940> file<00:22:57.360> right 00:22:57.590 --> 00:22:57.600 align:start position:0% we can G edit our WordPress file right 00:22:57.600 --> 00:22:59.870 align:start position:0% we can G edit our WordPress file right here<00:22:57.780> and<00:22:58.260> we<00:22:58.380> can<00:22:58.500> look<00:22:58.620> at<00:22:58.799> the<00:22:58.980> contents<00:22:59.460> and 00:22:59.870 --> 00:22:59.880 align:start position:0% here and we can look at the contents and 00:22:59.880 --> 00:23:02.330 align:start position:0% here and we can look at the contents and this<00:23:00.299> looks<00:23:00.720> really<00:23:01.020> messy<00:23:01.440> so<00:23:01.919> what<00:23:02.100> you<00:23:02.220> can 00:23:02.330 --> 00:23:02.340 align:start position:0% this looks really messy so what you can 00:23:02.340 --> 00:23:04.789 align:start position:0% this looks really messy so what you can do<00:23:02.520> is<00:23:02.880> actually<00:23:03.240> just<00:23:03.659> copy<00:23:04.140> this<00:23:04.320> hit<00:23:04.620> a 00:23:04.789 --> 00:23:04.799 align:start position:0% do is actually just copy this hit a 00:23:04.799 --> 00:23:07.549 align:start position:0% do is actually just copy this hit a command<00:23:05.220> a<00:23:05.400> and<00:23:05.880> a<00:23:06.059> command<00:23:06.360> C<00:23:06.539> and<00:23:07.260> then<00:23:07.380> we 00:23:07.549 --> 00:23:07.559 align:start position:0% command a and a command C and then we 00:23:07.559 --> 00:23:09.470 align:start position:0% command a and a command C and then we can<00:23:07.679> come<00:23:07.919> over<00:23:08.220> here<00:23:08.460> and<00:23:08.700> we<00:23:08.880> can<00:23:09.000> just<00:23:09.240> type 00:23:09.470 --> 00:23:09.480 align:start position:0% can come over here and we can just type 00:23:09.480 --> 00:23:10.690 align:start position:0% can come over here and we can just type in 00:23:10.690 --> 00:23:10.700 align:start position:0% in 00:23:10.700 --> 00:23:13.669 align:start position:0% in beaudifier<00:23:11.700> like<00:23:12.179> this 00:23:13.669 --> 00:23:13.679 align:start position:0% beaudifier like this 00:23:13.679 --> 00:23:15.830 align:start position:0% beaudifier like this and<00:23:14.220> we<00:23:14.460> can<00:23:14.520> just<00:23:14.640> click<00:23:14.820> on<00:23:14.940> the<00:23:15.059> top<00:23:15.179> one<00:23:15.419> and 00:23:15.830 --> 00:23:15.840 align:start position:0% and we can just click on the top one and 00:23:15.840 --> 00:23:18.830 align:start position:0% and we can just click on the top one and see<00:23:16.020> if<00:23:16.140> it<00:23:16.320> will<00:23:16.500> work<00:23:16.679> for<00:23:16.860> us<00:23:17.039> paste<00:23:18.000> in<00:23:18.179> the 00:23:18.830 --> 00:23:18.840 align:start position:0% see if it will work for us paste in the 00:23:18.840 --> 00:23:21.590 align:start position:0% see if it will work for us paste in the Json<00:23:19.500> for<00:23:19.860> us<00:23:20.039> and<00:23:20.580> type<00:23:20.820> you<00:23:21.240> can<00:23:21.299> click 00:23:21.590 --> 00:23:21.600 align:start position:0% Json for us and type you can click 00:23:21.600 --> 00:23:24.470 align:start position:0% Json for us and type you can click beautify<00:23:22.200> and<00:23:22.919> now<00:23:23.280> we<00:23:23.580> have<00:23:23.820> our<00:23:24.240> results 00:23:24.470 --> 00:23:24.480 align:start position:0% beautify and now we have our results 00:23:24.480 --> 00:23:27.110 align:start position:0% beautify and now we have our results right<00:23:24.780> here<00:23:25.020> so<00:23:25.740> it<00:23:26.039> actually<00:23:26.159> looks<00:23:26.640> the<00:23:27.000> same 00:23:27.110 --> 00:23:27.120 align:start position:0% right here so it actually looks the same 00:23:27.120 --> 00:23:28.250 align:start position:0% right here so it actually looks the same over<00:23:27.299> here<00:23:27.480> it<00:23:27.600> actually<00:23:27.720> didn't<00:23:27.960> make<00:23:28.140> any 00:23:28.250 --> 00:23:28.260 align:start position:0% over here it actually didn't make any 00:23:28.260 --> 00:23:30.470 align:start position:0% over here it actually didn't make any difference<00:23:28.500> so<00:23:28.980> maybe<00:23:29.520> this<00:23:29.940> one<00:23:30.059> doesn't 00:23:30.470 --> 00:23:30.480 align:start position:0% difference so maybe this one doesn't 00:23:30.480 --> 00:23:33.470 align:start position:0% difference so maybe this one doesn't work<00:23:30.780> for<00:23:31.020> us 00:23:33.470 --> 00:23:33.480 align:start position:0% 00:23:33.480 --> 00:23:35.450 align:start position:0% it<00:23:33.960> tells<00:23:34.200> us<00:23:34.260> we<00:23:34.380> have<00:23:34.559> an<00:23:34.679> error<00:23:34.980> okay<00:23:35.220> we're 00:23:35.450 --> 00:23:35.460 align:start position:0% it tells us we have an error okay we're 00:23:35.460 --> 00:23:37.610 align:start position:0% it tells us we have an error okay we're gonna<00:23:35.640> just<00:23:35.880> look<00:23:36.000> at<00:23:36.120> it<00:23:36.240> right<00:23:36.419> here<00:23:36.600> so<00:23:37.260> you 00:23:37.610 --> 00:23:37.620 align:start position:0% gonna just look at it right here so you 00:23:37.620 --> 00:23:39.710 align:start position:0% gonna just look at it right here so you can<00:23:37.740> actually<00:23:37.919> see<00:23:38.400> right<00:23:38.760> here<00:23:38.940> you<00:23:39.240> get<00:23:39.419> a 00:23:39.710 --> 00:23:39.720 align:start position:0% can actually see right here you get a 00:23:39.720 --> 00:23:42.289 align:start position:0% can actually see right here you get a hash<00:23:39.960> you<00:23:40.440> are<00:23:40.679> told<00:23:40.860> it's<00:23:41.039> from<00:23:41.400> Showdown 00:23:42.289 --> 00:23:42.299 align:start position:0% hash you are told it's from Showdown 00:23:42.299 --> 00:23:44.810 align:start position:0% hash you are told it's from Showdown it'll<00:23:42.659> tell<00:23:42.840> you<00:23:42.960> the<00:23:43.320> region<00:23:43.679> from<00:23:44.220> where<00:23:44.640> the 00:23:44.810 --> 00:23:44.820 align:start position:0% it'll tell you the region from where the 00:23:44.820 --> 00:23:46.610 align:start position:0% it'll tell you the region from where the web<00:23:45.000> app<00:23:45.179> is<00:23:45.360> coming<00:23:45.600> where<00:23:45.900> the<00:23:46.080> web<00:23:46.200> app<00:23:46.380> is 00:23:46.610 --> 00:23:46.620 align:start position:0% web app is coming where the web app is 00:23:46.620 --> 00:23:49.549 align:start position:0% web app is coming where the web app is coming<00:23:46.799> from<00:23:46.980> it's<00:23:47.880> going<00:23:48.240> to<00:23:48.539> give<00:23:49.020> us<00:23:49.200> the 00:23:49.549 --> 00:23:49.559 align:start position:0% coming from it's going to give us the 00:23:49.559 --> 00:23:52.370 align:start position:0% coming from it's going to give us the time<00:23:49.740> that<00:23:50.159> it<00:23:50.400> was<00:23:50.580> crawled<00:23:51.120> we<00:23:51.720> get<00:23:51.900> the 00:23:52.370 --> 00:23:52.380 align:start position:0% time that it was crawled we get the 00:23:52.380 --> 00:23:55.250 align:start position:0% time that it was crawled we get the server<00:23:52.980> that<00:23:53.280> it<00:23:53.460> is<00:23:53.580> running<00:23:53.760> on 00:23:55.250 --> 00:23:55.260 align:start position:0% server that it is running on 00:23:55.260 --> 00:23:57.049 align:start position:0% server that it is running on and<00:23:55.980> we<00:23:56.159> have<00:23:56.340> all<00:23:56.580> of<00:23:56.700> this<00:23:56.760> different 00:23:57.049 --> 00:23:57.059 align:start position:0% and we have all of this different 00:23:57.059 --> 00:23:59.870 align:start position:0% and we have all of this different information<00:23:57.480> here<00:23:58.080> that<00:23:58.860> it<00:23:59.220> that<00:23:59.520> Showdown 00:23:59.870 --> 00:23:59.880 align:start position:0% information here that it that Showdown 00:23:59.880 --> 00:24:02.930 align:start position:0% information here that it that Showdown has<00:24:00.240> crawled<00:24:00.659> from<00:24:00.980> this<00:24:01.980> specific<00:24:02.280> Target<00:24:02.520> we 00:24:02.930 --> 00:24:02.940 align:start position:0% has crawled from this specific Target we 00:24:02.940 --> 00:24:05.630 align:start position:0% has crawled from this specific Target we actually<00:24:03.120> grab<00:24:03.659> an<00:24:03.840> ASN<00:24:04.320> number<00:24:04.500> if<00:24:04.980> you<00:24:05.340> were 00:24:05.630 --> 00:24:05.640 align:start position:0% actually grab an ASN number if you were 00:24:05.640 --> 00:24:09.049 align:start position:0% actually grab an ASN number if you were looking<00:24:06.000> for<00:24:06.419> a<00:24:07.020> specific<00:24:07.440> Target<00:24:07.980> and<00:24:08.880> you 00:24:09.049 --> 00:24:09.059 align:start position:0% looking for a specific Target and you 00:24:09.059 --> 00:24:12.110 align:start position:0% looking for a specific Target and you needed<00:24:09.299> to<00:24:09.539> and<00:24:10.020> you<00:24:10.200> needed<00:24:10.559> to<00:24:11.100> pull<00:24:11.520> down<00:24:11.760> a 00:24:12.110 --> 00:24:12.120 align:start position:0% needed to and you needed to pull down a 00:24:12.120 --> 00:24:13.610 align:start position:0% needed to and you needed to pull down a version<00:24:12.240> and<00:24:12.600> you<00:24:12.720> were<00:24:12.900> looking<00:24:13.140> for<00:24:13.440> a 00:24:13.610 --> 00:24:13.620 align:start position:0% version and you were looking for a 00:24:13.620 --> 00:24:15.770 align:start position:0% version and you were looking for a specific<00:24:13.860> cve<00:24:14.280> and<00:24:14.880> you<00:24:15.000> wanted<00:24:15.120> to<00:24:15.360> download 00:24:15.770 --> 00:24:15.780 align:start position:0% specific cve and you wanted to download 00:24:15.780 --> 00:24:17.990 align:start position:0% specific cve and you wanted to download so<00:24:16.140> you<00:24:16.320> could<00:24:16.440> actually<00:24:16.559> see<00:24:17.159> what<00:24:17.580> the 00:24:17.990 --> 00:24:18.000 align:start position:0% so you could actually see what the 00:24:18.000 --> 00:24:20.630 align:start position:0% so you could actually see what the Showdown<00:24:18.659> databases<00:24:19.500> have<00:24:19.740> stored<00:24:20.220> for<00:24:20.460> the 00:24:20.630 --> 00:24:20.640 align:start position:0% Showdown databases have stored for the 00:24:20.640 --> 00:24:23.090 align:start position:0% Showdown databases have stored for the WordPress<00:24:21.020> 1.4.7<00:24:22.020> instead<00:24:22.679> of<00:24:22.740> just<00:24:22.919> seeing 00:24:23.090 --> 00:24:23.100 align:start position:0% WordPress 1.4.7 instead of just seeing 00:24:23.100 --> 00:24:24.409 align:start position:0% WordPress 1.4.7 instead of just seeing Oh<00:24:23.220> there's<00:24:23.520> seven<00:24:23.700> of<00:24:23.880> them<00:24:24.000> you<00:24:24.299> would 00:24:24.409 --> 00:24:24.419 align:start position:0% Oh there's seven of them you would 00:24:24.419 --> 00:24:26.810 align:start position:0% Oh there's seven of them you would download<00:24:24.659> it<00:24:24.960> into<00:24:25.200> a<00:24:25.620> file<00:24:25.919> just<00:24:26.280> like<00:24:26.520> this 00:24:26.810 --> 00:24:26.820 align:start position:0% download it into a file just like this 00:24:26.820 --> 00:24:29.450 align:start position:0% download it into a file just like this right<00:24:27.059> here<00:24:27.720> and<00:24:28.320> then<00:24:28.440> you<00:24:28.679> would<00:24:28.860> unzip<00:24:29.280> it 00:24:29.450 --> 00:24:29.460 align:start position:0% right here and then you would unzip it 00:24:29.460 --> 00:24:31.490 align:start position:0% right here and then you would unzip it and<00:24:29.820> then<00:24:29.940> you<00:24:30.240> can<00:24:30.360> G<00:24:30.720> edit<00:24:31.080> and<00:24:31.320> actually 00:24:31.490 --> 00:24:31.500 align:start position:0% and then you can G edit and actually 00:24:31.500 --> 00:24:34.010 align:start position:0% and then you can G edit and actually look<00:24:31.799> at<00:24:31.980> the<00:24:32.220> contents<00:24:32.700> of<00:24:32.820> the<00:24:33.059> file<00:24:33.360> and 00:24:34.010 --> 00:24:34.020 align:start position:0% look at the contents of the file and 00:24:34.020 --> 00:24:36.470 align:start position:0% look at the contents of the file and find<00:24:34.200> the<00:24:34.440> servers<00:24:34.860> and<00:24:35.280> the<00:24:35.640> subdomains<00:24:36.360> the 00:24:36.470 --> 00:24:36.480 align:start position:0% find the servers and the subdomains the 00:24:36.480 --> 00:24:39.169 align:start position:0% find the servers and the subdomains the URLs<00:24:37.080> the<00:24:37.559> as<00:24:37.799> numbers<00:24:38.220> and<00:24:38.640> there's<00:24:38.760> a<00:24:38.940> lot<00:24:39.059> of 00:24:39.169 --> 00:24:39.179 align:start position:0% URLs the as numbers and there's a lot of 00:24:39.179 --> 00:24:40.370 align:start position:0% URLs the as numbers and there's a lot of information<00:24:39.299> in<00:24:39.720> there<00:24:39.840> that's<00:24:40.020> going<00:24:40.200> to<00:24:40.260> be 00:24:40.370 --> 00:24:40.380 align:start position:0% information in there that's going to be 00:24:40.380 --> 00:24:42.890 align:start position:0% information in there that's going to be really<00:24:40.500> helpful<00:24:40.860> for<00:24:41.159> you<00:24:41.280> in<00:24:41.700> your<00:24:42.120> recon 00:24:42.890 --> 00:24:42.900 align:start position:0% really helpful for you in your recon 00:24:42.900 --> 00:24:44.990 align:start position:0% really helpful for you in your recon phase<00:24:43.320> if<00:24:43.799> these<00:24:44.159> targets<00:24:44.580> are<00:24:44.880> actually 00:24:44.990 --> 00:24:45.000 align:start position:0% phase if these targets are actually 00:24:45.000 --> 00:24:47.570 align:start position:0% phase if these targets are actually vulnerable<00:24:45.480> and<00:24:45.720> they<00:24:45.960> do<00:24:46.080> have<00:24:46.260> a<00:24:46.620> bug<00:24:47.039> Bounty 00:24:47.570 --> 00:24:47.580 align:start position:0% vulnerable and they do have a bug Bounty 00:24:47.580 --> 00:24:49.190 align:start position:0% vulnerable and they do have a bug Bounty program<00:24:48.059> so<00:24:48.600> one<00:24:48.720> of<00:24:48.840> the<00:24:48.900> other<00:24:49.020> things 00:24:49.190 --> 00:24:49.200 align:start position:0% program so one of the other things 00:24:49.200 --> 00:24:52.130 align:start position:0% program so one of the other things you're<00:24:49.380> able<00:24:49.559> to<00:24:49.679> do<00:24:49.740> with<00:24:49.919> Showdown<00:24:50.280> is<00:24:50.820> run<00:24:51.600> a 00:24:52.130 --> 00:24:52.140 align:start position:0% you're able to do with Showdown is run a 00:24:52.140 --> 00:24:55.669 align:start position:0% you're able to do with Showdown is run a is<00:24:52.380> to<00:24:52.620> run<00:24:52.799> an<00:24:53.039> IP<00:24:53.340> address<00:24:53.659> on<00:24:54.659> the<00:24:55.020> showdan 00:24:55.669 --> 00:24:55.679 align:start position:0% is to run an IP address on the showdan 00:24:55.679 --> 00:24:58.070 align:start position:0% is to run an IP address on the showdan Crawlers<00:24:56.400> and<00:24:56.760> so<00:24:56.940> you're<00:24:57.179> and<00:24:57.720> one<00:24:57.900> of<00:24:57.960> the 00:24:58.070 --> 00:24:58.080 align:start position:0% Crawlers and so you're and one of the 00:24:58.080 --> 00:25:01.250 align:start position:0% Crawlers and so you're and one of the ways<00:24:58.380> to<00:24:58.799> grab<00:24:59.340> an<00:25:00.000> IP<00:25:00.360> address<00:25:00.539> so<00:25:00.960> one<00:25:01.140> of<00:25:01.200> the 00:25:01.250 --> 00:25:01.260 align:start position:0% ways to grab an IP address so one of the 00:25:01.260 --> 00:25:02.330 align:start position:0% ways to grab an IP address so one of the ways<00:25:01.440> you're<00:25:01.559> going<00:25:01.679> to<00:25:01.679> be<00:25:01.799> able<00:25:01.860> to<00:25:01.980> find<00:25:02.100> the 00:25:02.330 --> 00:25:02.340 align:start position:0% ways you're going to be able to find the 00:25:02.340 --> 00:25:03.470 align:start position:0% ways you're going to be able to find the IP<00:25:02.580> address<00:25:02.700> there's<00:25:03.059> several<00:25:03.360> different 00:25:03.470 --> 00:25:03.480 align:start position:0% IP address there's several different 00:25:03.480 --> 00:25:05.330 align:start position:0% IP address there's several different ways<00:25:03.780> that<00:25:03.900> are<00:25:04.020> going<00:25:04.080> to<00:25:04.140> be<00:25:04.200> really<00:25:04.380> easy<00:25:04.559> so 00:25:05.330 --> 00:25:05.340 align:start position:0% ways that are going to be really easy so 00:25:05.340 --> 00:25:07.750 align:start position:0% ways that are going to be really easy so if<00:25:05.580> we<00:25:05.700> wanted<00:25:05.820> to<00:25:06.120> run<00:25:06.539> just<00:25:06.840> say<00:25:07.020> a<00:25:07.380> host 00:25:07.750 --> 00:25:07.760 align:start position:0% if we wanted to run just say a host 00:25:07.760 --> 00:25:10.430 align:start position:0% if we wanted to run just say a host yahoo.com<00:25:08.760> it's<00:25:09.600> going<00:25:09.780> to<00:25:09.900> give<00:25:10.020> us<00:25:10.200> back 00:25:10.430 --> 00:25:10.440 align:start position:0% yahoo.com it's going to give us back 00:25:10.440 --> 00:25:12.770 align:start position:0% yahoo.com it's going to give us back right<00:25:10.740> here<00:25:10.980> this<00:25:11.460> range<00:25:11.760> of<00:25:11.940> IP<00:25:12.299> addresses 00:25:12.770 --> 00:25:12.780 align:start position:0% right here this range of IP addresses 00:25:12.780 --> 00:25:15.130 align:start position:0% right here this range of IP addresses that<00:25:13.500> are<00:25:13.679> running<00:25:13.919> on 00:25:15.130 --> 00:25:15.140 align:start position:0% that are running on 00:25:15.140 --> 00:25:18.890 align:start position:0% that are running on yahoo.com<00:25:16.159> and<00:25:17.159> if<00:25:17.520> you<00:25:17.640> wanted<00:25:17.880> to<00:25:18.179> just<00:25:18.480> ping 00:25:18.890 --> 00:25:18.900 align:start position:0% yahoo.com and if you wanted to just ping 00:25:18.900 --> 00:25:20.510 align:start position:0% yahoo.com and if you wanted to just ping Yahoo 00:25:20.510 --> 00:25:20.520 align:start position:0% Yahoo 00:25:20.520 --> 00:25:23.930 align:start position:0% Yahoo .com<00:25:21.000> we<00:25:21.720> will<00:25:21.960> be<00:25:22.260> told<00:25:22.440> right<00:25:22.740> here<00:25:22.919> is<00:25:23.400> one 00:25:23.930 --> 00:25:23.940 align:start position:0% .com we will be told right here is one 00:25:23.940 --> 00:25:25.909 align:start position:0% .com we will be told right here is one of<00:25:24.059> the<00:25:24.179> IP<00:25:24.480> addresses<00:25:24.960> that<00:25:25.320> we<00:25:25.500> were<00:25:25.620> able<00:25:25.860> to 00:25:25.909 --> 00:25:25.919 align:start position:0% of the IP addresses that we were able to 00:25:25.919 --> 00:25:30.310 align:start position:0% of the IP addresses that we were able to Ping<00:25:26.159> so<00:25:26.340> if<00:25:26.520> you<00:25:26.640> look<00:25:26.760> for<00:25:27.000> this 00:25:30.310 --> 00:25:30.320 align:start position:0% 00:25:30.320 --> 00:25:33.590 align:start position:0% 74.14326<00:25:31.320> we<00:25:31.860> can<00:25:31.980> scroll<00:25:32.340> up<00:25:32.520> and<00:25:32.940> see<00:25:33.179> that 00:25:33.590 --> 00:25:33.600 align:start position:0% 74.14326 we can scroll up and see that 00:25:33.600 --> 00:25:35.390 align:start position:0% 74.14326 we can scroll up and see that this<00:25:33.900> is<00:25:34.080> one<00:25:34.380> of<00:25:34.500> the<00:25:34.559> IP<00:25:34.799> addresses<00:25:35.220> right 00:25:35.390 --> 00:25:35.400 align:start position:0% this is one of the IP addresses right 00:25:35.400 --> 00:25:37.789 align:start position:0% this is one of the IP addresses right here<00:25:35.580> you're<00:25:36.120> actually<00:25:36.360> able<00:25:36.659> to<00:25:36.900> find<00:25:37.380> IP 00:25:37.789 --> 00:25:37.799 align:start position:0% here you're actually able to find IP 00:25:37.799 --> 00:25:40.549 align:start position:0% here you're actually able to find IP addresses<00:25:38.279> through<00:25:38.580> burp<00:25:39.179> as<00:25:39.360> well<00:25:39.480> so<00:25:40.320> what 00:25:40.549 --> 00:25:40.559 align:start position:0% addresses through burp as well so what 00:25:40.559 --> 00:25:42.830 align:start position:0% addresses through burp as well so what we<00:25:40.679> can<00:25:40.860> do<00:25:41.039> is<00:25:41.460> come<00:25:41.760> over<00:25:41.940> here<00:25:42.120> and<00:25:42.360> open<00:25:42.600> up 00:25:42.830 --> 00:25:42.840 align:start position:0% we can do is come over here and open up 00:25:42.840 --> 00:25:45.490 align:start position:0% we can do is come over here and open up a<00:25:43.200> new<00:25:43.380> tab<00:25:43.559> type<00:25:43.860> in<00:25:44.039> yahoo.com 00:25:45.490 --> 00:25:45.500 align:start position:0% a new tab type in yahoo.com 00:25:45.500 --> 00:25:50.210 align:start position:0% a new tab type in yahoo.com and<00:25:46.500> we<00:25:47.039> can<00:25:47.580> open<00:25:47.820> up<00:25:48.000> burp<00:25:48.539> and<00:25:49.220> intercept 00:25:50.210 --> 00:25:50.220 align:start position:0% and we can open up burp and intercept 00:25:50.220 --> 00:25:52.370 align:start position:0% and we can open up burp and intercept with<00:25:50.820> the<00:25:51.000> proxy 00:25:52.370 --> 00:25:52.380 align:start position:0% with the proxy 00:25:52.380 --> 00:25:54.409 align:start position:0% with the proxy and<00:25:52.860> if<00:25:53.039> we<00:25:53.220> run<00:25:53.520> this<00:25:53.760> you'll<00:25:54.120> actually<00:25:54.240> be 00:25:54.409 --> 00:25:54.419 align:start position:0% and if we run this you'll actually be 00:25:54.419 --> 00:25:57.470 align:start position:0% and if we run this you'll actually be able<00:25:54.539> to<00:25:54.659> see<00:25:54.900> right<00:25:55.380> here<00:25:55.620> on<00:25:56.460> 443<00:25:57.179> you<00:25:57.360> have 00:25:57.470 --> 00:25:57.480 align:start position:0% able to see right here on 443 you have 00:25:57.480 --> 00:26:00.850 align:start position:0% able to see right here on 443 you have this 00:26:00.850 --> 00:26:00.860 align:start position:0% 00:26:00.860 --> 00:26:03.590 align:start position:0% 98371163<00:26:01.860> and<00:26:02.340> if<00:26:02.520> you<00:26:02.580> come<00:26:02.760> back<00:26:02.880> here<00:26:03.120> you 00:26:03.590 --> 00:26:03.600 align:start position:0% 98371163 and if you come back here you 00:26:03.600 --> 00:26:05.630 align:start position:0% 98371163 and if you come back here you should<00:26:03.779> be<00:26:03.900> able<00:26:04.020> to<00:26:04.140> find<00:26:04.320> right<00:26:04.740> here<00:26:04.980> and<00:26:05.460> so 00:26:05.630 --> 00:26:05.640 align:start position:0% should be able to find right here and so 00:26:05.640 --> 00:26:07.190 align:start position:0% should be able to find right here and so there's<00:26:05.820> a<00:26:06.000> several<00:26:06.179> different<00:26:06.299> ways<00:26:06.659> to<00:26:06.779> find 00:26:07.190 --> 00:26:07.200 align:start position:0% there's a several different ways to find 00:26:07.200 --> 00:26:10.130 align:start position:0% there's a several different ways to find IP<00:26:07.679> addresses<00:26:08.159> for<00:26:08.460> a<00:26:08.700> specific<00:26:09.120> domain 00:26:10.130 --> 00:26:10.140 align:start position:0% IP addresses for a specific domain 00:26:10.140 --> 00:26:11.390 align:start position:0% IP addresses for a specific domain I'm<00:26:10.380> actually<00:26:10.559> going<00:26:10.799> to<00:26:10.799> close<00:26:10.980> out<00:26:11.159> of<00:26:11.279> this 00:26:11.390 --> 00:26:11.400 align:start position:0% I'm actually going to close out of this 00:26:11.400 --> 00:26:13.730 align:start position:0% I'm actually going to close out of this but<00:26:12.179> this<00:26:12.480> is<00:26:12.659> one<00:26:12.960> way<00:26:13.080> to<00:26:13.260> do<00:26:13.380> that<00:26:13.440> and<00:26:13.620> then 00:26:13.730 --> 00:26:13.740 align:start position:0% but this is one way to do that and then 00:26:13.740 --> 00:26:16.130 align:start position:0% but this is one way to do that and then you<00:26:13.860> can<00:26:13.980> just<00:26:14.100> type<00:26:14.220> in<00:26:14.460> showdan<00:26:15.240> and<00:26:15.900> then<00:26:15.960> we 00:26:16.130 --> 00:26:16.140 align:start position:0% you can just type in showdan and then we 00:26:16.140 --> 00:26:18.230 align:start position:0% you can just type in showdan and then we would<00:26:16.260> type<00:26:16.440> in<00:26:16.620> host<00:26:16.860> and<00:26:17.279> then<00:26:17.400> we<00:26:17.580> can<00:26:17.760> grab 00:26:18.230 --> 00:26:18.240 align:start position:0% would type in host and then we can grab 00:26:18.240 --> 00:26:21.350 align:start position:0% would type in host and then we can grab one<00:26:18.960> of<00:26:19.140> these<00:26:19.440> IP<00:26:19.799> addresses<00:26:20.279> that<00:26:20.700> we<00:26:20.940> just 00:26:21.350 --> 00:26:21.360 align:start position:0% one of these IP addresses that we just 00:26:21.360 --> 00:26:22.130 align:start position:0% one of these IP addresses that we just saw 00:26:22.130 --> 00:26:22.140 align:start position:0% saw 00:26:22.140 --> 00:26:25.310 align:start position:0% saw and<00:26:23.100> run<00:26:23.820> it<00:26:24.000> within<00:26:24.299> Showdown<00:26:24.720> and<00:26:25.260> it's 00:26:25.310 --> 00:26:25.320 align:start position:0% and run it within Showdown and it's 00:26:25.320 --> 00:26:26.690 align:start position:0% and run it within Showdown and it's going<00:26:25.500> to<00:26:25.620> give<00:26:25.679> us<00:26:25.860> some<00:26:26.039> information<00:26:26.220> right 00:26:26.690 --> 00:26:26.700 align:start position:0% going to give us some information right 00:26:26.700 --> 00:26:27.950 align:start position:0% going to give us some information right here<00:26:26.820> it's<00:26:26.940> going<00:26:27.120> to<00:26:27.179> tell<00:26:27.299> us<00:26:27.419> that<00:26:27.659> this 00:26:27.950 --> 00:26:27.960 align:start position:0% here it's going to tell us that this 00:26:27.960 --> 00:26:32.210 align:start position:0% here it's going to tell us that this port<00:26:28.260> 80<00:26:28.860> is<00:26:29.400> open<00:26:29.700> and<00:26:30.299> Port<00:26:30.539> 443<00:26:31.140> is<00:26:31.320> open<00:26:31.500> and 00:26:32.210 --> 00:26:32.220 align:start position:0% port 80 is open and Port 443 is open and 00:26:32.220 --> 00:26:34.010 align:start position:0% port 80 is open and Port 443 is open and it'll<00:26:32.460> give<00:26:32.640> us<00:26:32.760> other<00:26:33.000> information<00:26:33.299> if<00:26:33.840> you 00:26:34.010 --> 00:26:34.020 align:start position:0% it'll give us other information if you 00:26:34.020 --> 00:26:36.409 align:start position:0% it'll give us other information if you specifically<00:26:34.440> want<00:26:34.740> to<00:26:34.919> look<00:26:35.340> for<00:26:35.640> an<00:26:35.940> SSL 00:26:36.409 --> 00:26:36.419 align:start position:0% specifically want to look for an SSL 00:26:36.419 --> 00:26:39.049 align:start position:0% specifically want to look for an SSL certification<00:26:37.380> you<00:26:38.159> can<00:26:38.340> find<00:26:38.640> those<00:26:38.880> and 00:26:39.049 --> 00:26:39.059 align:start position:0% certification you can find those and 00:26:39.059 --> 00:26:40.370 align:start position:0% certification you can find those and it's<00:26:39.179> going<00:26:39.299> to<00:26:39.360> tell<00:26:39.480> us<00:26:39.600> it's<00:26:39.779> running<00:26:39.960> these 00:26:40.370 --> 00:26:40.380 align:start position:0% it's going to tell us it's running these 00:26:40.380 --> 00:26:41.690 align:start position:0% it's going to tell us it's running these different<00:26:40.620> versions<00:26:40.980> and<00:26:41.220> you<00:26:41.340> can<00:26:41.460> go<00:26:41.520> check 00:26:41.690 --> 00:26:41.700 align:start position:0% different versions and you can go check 00:26:41.700 --> 00:26:44.269 align:start position:0% different versions and you can go check to<00:26:41.940> see<00:26:42.120> if<00:26:42.360> these<00:26:42.659> SSL<00:26:43.080> versions<00:26:43.440> are<00:26:43.679> out<00:26:44.159> of 00:26:44.269 --> 00:26:44.279 align:start position:0% to see if these SSL versions are out of 00:26:44.279 --> 00:26:46.310 align:start position:0% to see if these SSL versions are out of date<00:26:44.460> or<00:26:44.760> what<00:26:45.000> you<00:26:45.179> can<00:26:45.360> do<00:26:45.720> with<00:26:46.080> these 00:26:46.310 --> 00:26:46.320 align:start position:0% date or what you can do with these 00:26:46.320 --> 00:26:49.250 align:start position:0% date or what you can do with these within<00:26:47.039> your<00:26:47.400> recon<00:26:48.000> phase<00:26:48.539> you<00:26:48.779> also<00:26:49.020> get 00:26:49.250 --> 00:26:49.260 align:start position:0% within your recon phase you also get 00:26:49.260 --> 00:26:51.409 align:start position:0% within your recon phase you also get these<00:26:49.679> other<00:26:49.860> host<00:26:50.100> names<00:26:50.400> right<00:26:50.940> here<00:26:51.120> that 00:26:51.409 --> 00:26:51.419 align:start position:0% these other host names right here that 00:26:51.419 --> 00:26:54.289 align:start position:0% these other host names right here that can<00:26:51.600> be<00:26:51.779> associated<00:26:52.380> with<00:26:52.799> IP<00:26:53.279> ranges<00:26:53.700> and<00:26:54.120> you 00:26:54.289 --> 00:26:54.299 align:start position:0% can be associated with IP ranges and you 00:26:54.299 --> 00:26:57.230 align:start position:0% can be associated with IP ranges and you can<00:26:54.419> run<00:26:54.659> a<00:26:54.960> showdown<00:26:55.380> host<00:26:55.679> with<00:26:56.400> an<00:26:56.580> IP<00:26:56.880> range 00:26:57.230 --> 00:26:57.240 align:start position:0% can run a showdown host with an IP range 00:26:57.240 --> 00:26:59.090 align:start position:0% can run a showdown host with an IP range and<00:26:57.539> it's<00:26:57.659> going<00:26:57.840> to<00:26:57.900> pull<00:26:58.020> down<00:26:58.200> a<00:26:58.559> bunch<00:26:58.740> more 00:26:59.090 --> 00:26:59.100 align:start position:0% and it's going to pull down a bunch more 00:26:59.100 --> 00:27:01.370 align:start position:0% and it's going to pull down a bunch more information<00:26:59.340> for<00:26:59.820> you<00:26:59.940> within<00:27:00.779> the<00:27:01.140> entire 00:27:01.370 --> 00:27:01.380 align:start position:0% information for you within the entire 00:27:01.380 --> 00:27:03.350 align:start position:0% information for you within the entire range<00:27:01.740> it'll<00:27:02.039> give<00:27:02.159> you<00:27:02.279> all<00:27:02.640> of<00:27:02.880> the<00:27:03.059> ports 00:27:03.350 --> 00:27:03.360 align:start position:0% range it'll give you all of the ports 00:27:03.360 --> 00:27:06.769 align:start position:0% range it'll give you all of the ports that<00:27:03.419> are<00:27:03.600> open<00:27:03.679> within<00:27:04.679> with<00:27:05.460> the<00:27:05.760> IPS<00:27:06.120> and<00:27:06.600> so 00:27:06.769 --> 00:27:06.779 align:start position:0% that are open within with the IPS and so 00:27:06.779 --> 00:27:08.149 align:start position:0% that are open within with the IPS and so the<00:27:06.900> difference<00:27:07.020> here<00:27:07.320> between<00:27:07.679> what<00:27:08.039> we're 00:27:08.149 --> 00:27:08.159 align:start position:0% the difference here between what we're 00:27:08.159 --> 00:27:10.010 align:start position:0% the difference here between what we're able<00:27:08.340> to<00:27:08.520> find<00:27:08.700> between<00:27:09.000> Google<00:27:09.299> and<00:27:09.539> showdan 00:27:10.010 --> 00:27:10.020 align:start position:0% able to find between Google and showdan 00:27:10.020 --> 00:27:12.470 align:start position:0% able to find between Google and showdan is<00:27:10.440> Google<00:27:10.620> goes<00:27:11.100> out<00:27:11.159> and<00:27:11.400> crawls<00:27:11.880> the<00:27:12.120> pages 00:27:12.470 --> 00:27:12.480 align:start position:0% is Google goes out and crawls the pages 00:27:12.480 --> 00:27:15.169 align:start position:0% is Google goes out and crawls the pages to<00:27:13.080> see<00:27:13.260> what<00:27:13.559> is<00:27:13.740> reachable<00:27:14.220> but<00:27:14.700> Showdown 00:27:15.169 --> 00:27:15.179 align:start position:0% to see what is reachable but Showdown 00:27:15.179 --> 00:27:16.970 align:start position:0% to see what is reachable but Showdown across<00:27:15.779> all<00:27:16.020> of<00:27:16.140> the<00:27:16.260> Internet<00:27:16.500> connected 00:27:16.970 --> 00:27:16.980 align:start position:0% across all of the Internet connected 00:27:16.980 --> 00:27:19.370 align:start position:0% across all of the Internet connected devices<00:27:17.400> and<00:27:17.760> this<00:27:17.940> is<00:27:18.000> why<00:27:18.240> you<00:27:18.480> would<00:27:18.600> find<00:27:18.900> a 00:27:19.370 --> 00:27:19.380 align:start position:0% devices and this is why you would find a 00:27:19.380 --> 00:27:21.169 align:start position:0% devices and this is why you would find a refrigerator<00:27:19.860> that<00:27:20.279> might<00:27:20.400> be<00:27:20.520> connected<00:27:20.880> or 00:27:21.169 --> 00:27:21.179 align:start position:0% refrigerator that might be connected or 00:27:21.179 --> 00:27:23.510 align:start position:0% refrigerator that might be connected or a<00:27:21.419> webcam<00:27:21.720> or<00:27:22.080> somebody's<00:27:22.799> property<00:27:23.100> cameras 00:27:23.510 --> 00:27:23.520 align:start position:0% a webcam or somebody's property cameras 00:27:23.520 --> 00:27:25.549 align:start position:0% a webcam or somebody's property cameras or<00:27:23.880> literally<00:27:24.240> anything<00:27:24.539> that<00:27:25.020> is<00:27:25.200> connected 00:27:25.549 --> 00:27:25.559 align:start position:0% or literally anything that is connected 00:27:25.559 --> 00:27:28.310 align:start position:0% or literally anything that is connected to<00:27:25.679> the<00:27:25.860> internet<00:27:25.980> like<00:27:26.700> a<00:27:27.179> thermostat<00:27:27.480> and 00:27:28.310 --> 00:27:28.320 align:start position:0% to the internet like a thermostat and 00:27:28.320 --> 00:27:30.049 align:start position:0% to the internet like a thermostat and Showdown<00:27:28.799> actually<00:27:29.100> crawls<00:27:29.580> everything<00:27:29.760> that 00:27:30.049 --> 00:27:30.059 align:start position:0% Showdown actually crawls everything that 00:27:30.059 --> 00:27:31.909 align:start position:0% Showdown actually crawls everything that is<00:27:30.179> connected<00:27:30.539> to<00:27:30.779> the<00:27:31.080> internet<00:27:31.320> and<00:27:31.679> stores 00:27:31.909 --> 00:27:31.919 align:start position:0% is connected to the internet and stores 00:27:31.919 --> 00:27:33.950 align:start position:0% is connected to the internet and stores the<00:27:32.220> data<00:27:32.520> so<00:27:32.820> one<00:27:33.000> of<00:27:33.120> the<00:27:33.179> good<00:27:33.299> things<00:27:33.480> about 00:27:33.950 --> 00:27:33.960 align:start position:0% the data so one of the good things about 00:27:33.960 --> 00:27:37.010 align:start position:0% the data so one of the good things about running<00:27:34.380> showdan<00:27:35.159> like<00:27:35.580> this<00:27:35.880> is<00:27:36.299> sometimes 00:27:37.010 --> 00:27:37.020 align:start position:0% running showdan like this is sometimes 00:27:37.020 --> 00:27:39.409 align:start position:0% running showdan like this is sometimes you<00:27:37.620> are<00:27:37.980> going<00:27:38.159> to<00:27:38.340> come<00:27:38.760> across<00:27:39.120> a<00:27:39.299> bug 00:27:39.409 --> 00:27:39.419 align:start position:0% you are going to come across a bug 00:27:39.419 --> 00:27:41.149 align:start position:0% you are going to come across a bug mounting<00:27:39.900> programs<00:27:40.260> they're<00:27:40.740> going<00:27:40.919> to<00:27:41.039> tell 00:27:41.149 --> 00:27:41.159 align:start position:0% mounting programs they're going to tell 00:27:41.159 --> 00:27:43.730 align:start position:0% mounting programs they're going to tell you<00:27:41.279> that<00:27:41.520> you're<00:27:41.760> not<00:27:42.000> allowed<00:27:42.360> to<00:27:42.720> scan<00:27:43.320> a 00:27:43.730 --> 00:27:43.740 align:start position:0% you that you're not allowed to scan a 00:27:43.740 --> 00:27:46.010 align:start position:0% you that you're not allowed to scan a specific<00:27:44.159> Network<00:27:44.400> and<00:27:44.880> as<00:27:45.179> new<00:27:45.360> bug<00:27:45.539> bounty 00:27:46.010 --> 00:27:46.020 align:start position:0% specific Network and as new bug bounty 00:27:46.020 --> 00:27:48.110 align:start position:0% specific Network and as new bug bounty hunters<00:27:46.260> I<00:27:46.860> know<00:27:47.039> there<00:27:47.279> is<00:27:47.460> a<00:27:47.700> lot<00:27:47.820> of 00:27:48.110 --> 00:27:48.120 align:start position:0% hunters I know there is a lot of 00:27:48.120 --> 00:27:49.610 align:start position:0% hunters I know there is a lot of questions<00:27:48.539> about<00:27:48.840> what<00:27:49.140> you're<00:27:49.260> allowed<00:27:49.559> to 00:27:49.610 --> 00:27:49.620 align:start position:0% questions about what you're allowed to 00:27:49.620 --> 00:27:51.529 align:start position:0% questions about what you're allowed to do<00:27:49.740> and<00:27:49.919> what<00:27:50.100> you're<00:27:50.220> not<00:27:50.400> allowed<00:27:50.700> to<00:27:50.760> do<00:27:50.940> and 00:27:51.529 --> 00:27:51.539 align:start position:0% do and what you're not allowed to do and 00:27:51.539 --> 00:27:53.690 align:start position:0% do and what you're not allowed to do and so<00:27:51.720> Showdown<00:27:52.260> is<00:27:52.500> a<00:27:52.620> great<00:27:52.740> way<00:27:52.919> to<00:27:53.220> scan<00:27:53.580> a 00:27:53.690 --> 00:27:53.700 align:start position:0% so Showdown is a great way to scan a 00:27:53.700 --> 00:27:55.610 align:start position:0% so Showdown is a great way to scan a network<00:27:53.880> without<00:27:54.240> actually<00:27:54.720> scanning<00:27:55.440> a 00:27:55.610 --> 00:27:55.620 align:start position:0% network without actually scanning a 00:27:55.620 --> 00:27:57.590 align:start position:0% network without actually scanning a network<00:27:55.799> because<00:27:56.100> showdan<00:27:56.760> already<00:27:57.059> has 00:27:57.590 --> 00:27:57.600 align:start position:0% network because showdan already has 00:27:57.600 --> 00:27:59.149 align:start position:0% network because showdan already has stored<00:27:58.200> all<00:27:58.440> of<00:27:58.500> the<00:27:58.620> information<00:27:58.799> that 00:27:59.149 --> 00:27:59.159 align:start position:0% stored all of the information that 00:27:59.159 --> 00:28:00.289 align:start position:0% stored all of the information that you're<00:27:59.220> going<00:27:59.340> to<00:27:59.460> be<00:27:59.520> looking<00:27:59.700> for<00:27:59.880> and<00:28:00.120> you 00:28:00.289 --> 00:28:00.299 align:start position:0% you're going to be looking for and you 00:28:00.299 --> 00:28:01.909 align:start position:0% you're going to be looking for and you just<00:28:00.419> have<00:28:00.480> to<00:28:00.600> go<00:28:00.779> out<00:28:00.900> and<00:28:01.140> find<00:28:01.500> it<00:28:01.679> you<00:28:01.799> have 00:28:01.909 --> 00:28:01.919 align:start position:0% just have to go out and find it you have 00:28:01.919 --> 00:28:03.710 align:start position:0% just have to go out and find it you have to<00:28:01.980> know<00:28:02.100> what<00:28:02.340> commands<00:28:02.820> to<00:28:02.940> give<00:28:03.120> such<00:28:03.600> as 00:28:03.710 --> 00:28:03.720 align:start position:0% to know what commands to give such as 00:28:03.720 --> 00:28:05.570 align:start position:0% to know what commands to give such as this<00:28:03.900> one<00:28:04.020> right<00:28:04.200> here<00:28:04.380> if<00:28:05.039> you're<00:28:05.220> looking 00:28:05.570 --> 00:28:05.580 align:start position:0% this one right here if you're looking 00:28:05.580 --> 00:28:08.330 align:start position:0% this one right here if you're looking for<00:28:05.940> open<00:28:06.240> ports<00:28:06.840> I<00:28:07.320> personally<00:28:07.799> would<00:28:08.159> rather 00:28:08.330 --> 00:28:08.340 align:start position:0% for open ports I personally would rather 00:28:08.340 --> 00:28:11.870 align:start position:0% for open ports I personally would rather just<00:28:08.640> run<00:28:08.760> nmap<00:28:09.299> with<00:28:09.600> the<00:28:09.840> ports<00:28:10.440> that<00:28:10.980> I<00:28:11.400> want 00:28:11.870 --> 00:28:11.880 align:start position:0% just run nmap with the ports that I want 00:28:11.880 --> 00:28:16.269 align:start position:0% just run nmap with the ports that I want to<00:28:12.299> find<00:28:12.659> such<00:28:13.020> as<00:28:13.200> Port<00:28:13.500> 22<00:28:13.980> Port<00:28:14.220> 80<00:28:14.520> 443 00:28:16.269 --> 00:28:16.279 align:start position:0% to find such as Port 22 Port 80 443 00:28:16.279 --> 00:28:18.890 align:start position:0% to find such as Port 22 Port 80 443 1443-3389<00:28:17.279> or<00:28:17.580> whatever<00:28:17.820> other<00:28:18.120> ports<00:28:18.600> you 00:28:18.890 --> 00:28:18.900 align:start position:0% 1443-3389 or whatever other ports you 00:28:18.900 --> 00:28:20.870 align:start position:0% 1443-3389 or whatever other ports you might<00:28:19.080> come<00:28:19.320> across<00:28:19.679> but<00:28:20.100> I<00:28:20.340> would<00:28:20.400> rather<00:28:20.580> run 00:28:20.870 --> 00:28:20.880 align:start position:0% might come across but I would rather run 00:28:20.880 --> 00:28:22.730 align:start position:0% might come across but I would rather run in<00:28:21.059> map<00:28:21.240> with<00:28:21.480> specific<00:28:21.720> ports<00:28:21.960> on<00:28:22.020> but<00:28:22.440> I<00:28:22.620> know 00:28:22.730 --> 00:28:22.740 align:start position:0% in map with specific ports on but I know 00:28:22.740 --> 00:28:24.110 align:start position:0% in map with specific ports on but I know there<00:28:22.919> are<00:28:23.039> some<00:28:23.159> people<00:28:23.340> who<00:28:23.640> really<00:28:23.880> worry 00:28:24.110 --> 00:28:24.120 align:start position:0% there are some people who really worry 00:28:24.120 --> 00:28:25.909 align:start position:0% there are some people who really worry about<00:28:24.360> this<00:28:24.600> and<00:28:24.840> show<00:28:25.080> Dan<00:28:25.320> is<00:28:25.620> a<00:28:25.799> great 00:28:25.909 --> 00:28:25.919 align:start position:0% about this and show Dan is a great 00:28:25.919 --> 00:28:27.649 align:start position:0% about this and show Dan is a great option<00:28:26.220> such<00:28:26.460> as<00:28:26.580> this<00:28:26.760> showdown<00:28:27.120> host<00:28:27.360> right 00:28:27.649 --> 00:28:27.659 align:start position:0% option such as this showdown host right 00:28:27.659 --> 00:28:30.110 align:start position:0% option such as this showdown host right here<00:28:27.840> to<00:28:28.380> grab<00:28:28.799> other<00:28:29.039> domains<00:28:29.640> you<00:28:29.820> can<00:28:29.880> grab 00:28:30.110 --> 00:28:30.120 align:start position:0% here to grab other domains you can grab 00:28:30.120 --> 00:28:32.990 align:start position:0% here to grab other domains you can grab subdomains<00:28:30.840> and<00:28:31.380> you<00:28:31.559> can<00:28:31.679> scan<00:28:32.039> for<00:28:32.520> ports 00:28:32.990 --> 00:28:33.000 align:start position:0% subdomains and you can scan for ports 00:28:33.000 --> 00:28:35.510 align:start position:0% subdomains and you can scan for ports and<00:28:33.299> IP<00:28:33.659> ranges<00:28:34.140> and<00:28:34.380> so<00:28:34.559> this<00:28:34.799> is<00:28:34.980> an<00:28:35.279> option 00:28:35.510 --> 00:28:35.520 align:start position:0% and IP ranges and so this is an option 00:28:35.520 --> 00:28:38.210 align:start position:0% and IP ranges and so this is an option if<00:28:35.820> you're<00:28:36.000> worried<00:28:36.299> about<00:28:36.419> scanning<00:28:37.260> a 00:28:38.210 --> 00:28:38.220 align:start position:0% if you're worried about scanning a 00:28:38.220 --> 00:28:40.730 align:start position:0% if you're worried about scanning a Target<00:28:38.640> in<00:28:39.299> order<00:28:39.360> to<00:28:39.600> grab<00:28:39.840> subdomains<00:28:40.500> and 00:28:40.730 --> 00:28:40.740 align:start position:0% Target in order to grab subdomains and 00:28:40.740 --> 00:28:42.350 align:start position:0% Target in order to grab subdomains and open<00:28:40.919> ports<00:28:41.400> and<00:28:41.580> what<00:28:41.760> I<00:28:41.820> like<00:28:41.940> to<00:28:42.059> use<00:28:42.179> for 00:28:42.350 --> 00:28:42.360 align:start position:0% open ports and what I like to use for 00:28:42.360 --> 00:28:44.450 align:start position:0% open ports and what I like to use for running<00:28:42.539> subdomains<00:28:43.260> is<00:28:43.500> amass<00:28:44.039> and<00:28:44.220> I'll<00:28:44.340> go 00:28:44.450 --> 00:28:44.460 align:start position:0% running subdomains is amass and I'll go 00:28:44.460 --> 00:28:47.149 align:start position:0% running subdomains is amass and I'll go ahead<00:28:44.520> and<00:28:44.640> Link<00:28:44.760> My<00:28:45.059> amass<00:28:45.539> video<00:28:45.779> in<00:28:46.620> the 00:28:47.149 --> 00:28:47.159 align:start position:0% ahead and Link My amass video in the 00:28:47.159 --> 00:28:49.010 align:start position:0% ahead and Link My amass video in the description<00:28:47.700> if<00:28:48.179> you<00:28:48.299> would<00:28:48.419> like<00:28:48.600> to<00:28:48.779> learn 00:28:49.010 --> 00:28:49.020 align:start position:0% description if you would like to learn 00:28:49.020 --> 00:28:50.510 align:start position:0% description if you would like to learn more<00:28:49.200> about<00:28:49.380> that<00:28:49.620> so<00:28:49.980> let's<00:28:50.100> go<00:28:50.279> ahead<00:28:50.400> and 00:28:50.510 --> 00:28:50.520 align:start position:0% more about that so let's go ahead and 00:28:50.520 --> 00:28:52.610 align:start position:0% more about that so let's go ahead and look<00:28:50.760> at<00:28:50.940> scanning<00:28:51.480> a<00:28:51.659> host<00:28:51.900> instead<00:28:52.320> of<00:28:52.440> just 00:28:52.610 --> 00:28:52.620 align:start position:0% look at scanning a host instead of just 00:28:52.620 --> 00:28:54.350 align:start position:0% look at scanning a host instead of just looking<00:28:52.799> at<00:28:53.100> this<00:28:53.340> right<00:28:53.580> here<00:28:53.760> The<00:28:53.940> Showdown 00:28:54.350 --> 00:28:54.360 align:start position:0% looking at this right here The Showdown 00:28:54.360 --> 00:28:56.570 align:start position:0% looking at this right here The Showdown host<00:28:54.600> so<00:28:55.200> with<00:28:55.500> showdan<00:28:56.159> you<00:28:56.340> can<00:28:56.460> actually 00:28:56.570 --> 00:28:56.580 align:start position:0% host so with showdan you can actually 00:28:56.580 --> 00:29:00.350 align:start position:0% host so with showdan you can actually just<00:28:56.880> type<00:28:57.120> in<00:28:57.419> showdan<00:28:58.260> we'll<00:28:58.679> go<00:28:59.039> scan<00:28:59.880> Dash 00:29:00.350 --> 00:29:00.360 align:start position:0% just type in showdan we'll go scan Dash 00:29:00.360 --> 00:29:02.450 align:start position:0% just type in showdan we'll go scan Dash H<00:29:00.539> and<00:29:01.200> we<00:29:01.320> can<00:29:01.440> look<00:29:01.620> to<00:29:01.799> see<00:29:02.039> what<00:29:02.340> our 00:29:02.450 --> 00:29:02.460 align:start position:0% H and we can look to see what our 00:29:02.460 --> 00:29:06.409 align:start position:0% H and we can look to see what our options<00:29:02.820> are<00:29:03.120> for<00:29:04.020> scanning<00:29:04.799> a<00:29:05.039> IP<00:29:05.760> and<00:29:06.179> so<00:29:06.299> it 00:29:06.409 --> 00:29:06.419 align:start position:0% options are for scanning a IP and so it 00:29:06.419 --> 00:29:08.390 align:start position:0% options are for scanning a IP and so it tells<00:29:06.659> us<00:29:06.720> right<00:29:06.900> here<00:29:07.080> we<00:29:07.380> can<00:29:07.500> scan<00:29:07.860> an<00:29:08.039> IP 00:29:08.390 --> 00:29:08.400 align:start position:0% tells us right here we can scan an IP 00:29:08.400 --> 00:29:13.250 align:start position:0% tells us right here we can scan an IP and<00:29:09.120> we<00:29:09.360> can<00:29:09.480> say<00:29:09.860> showdan<00:29:10.860> scan<00:29:11.760> and<00:29:12.539> then<00:29:12.720> we 00:29:13.250 --> 00:29:13.260 align:start position:0% and we can say showdan scan and then we 00:29:13.260 --> 00:29:15.830 align:start position:0% and we can say showdan scan and then we can<00:29:13.500> give<00:29:14.100> it<00:29:14.279> the<00:29:14.520> IP<00:29:14.880> that<00:29:15.120> we<00:29:15.299> want<00:29:15.480> and 00:29:15.830 --> 00:29:15.840 align:start position:0% can give it the IP that we want and 00:29:15.840 --> 00:29:17.450 align:start position:0% can give it the IP that we want and we'll<00:29:15.960> just<00:29:16.200> run<00:29:16.440> this<00:29:16.799> same<00:29:17.039> IP<00:29:17.340> address 00:29:17.450 --> 00:29:17.460 align:start position:0% we'll just run this same IP address 00:29:17.460 --> 00:29:19.850 align:start position:0% we'll just run this same IP address right<00:29:17.820> here<00:29:18.000> and<00:29:18.240> see<00:29:18.480> what<00:29:18.720> information<00:29:19.020> it 00:29:19.850 --> 00:29:19.860 align:start position:0% right here and see what information it 00:29:19.860 --> 00:29:21.710 align:start position:0% right here and see what information it gives<00:29:20.100> back<00:29:20.279> to<00:29:20.399> us<00:29:20.460> it<00:29:20.700> tells<00:29:20.940> us<00:29:21.059> we<00:29:21.299> need<00:29:21.600> to 00:29:21.710 --> 00:29:21.720 align:start position:0% gives back to us it tells us we need to 00:29:21.720 --> 00:29:25.010 align:start position:0% gives back to us it tells us we need to give<00:29:21.840> it<00:29:21.960> a<00:29:22.620> command<00:29:23.100> so<00:29:23.340> we<00:29:23.640> can<00:29:23.820> say<00:29:24.120> submit 00:29:25.010 --> 00:29:25.020 align:start position:0% give it a command so we can say submit 00:29:25.020 --> 00:29:26.450 align:start position:0% give it a command so we can say submit right<00:29:25.260> here<00:29:25.380> because<00:29:25.500> we're<00:29:25.740> going<00:29:25.919> to<00:29:25.980> submit 00:29:26.450 --> 00:29:26.460 align:start position:0% right here because we're going to submit 00:29:26.460 --> 00:29:31.430 align:start position:0% right here because we're going to submit an<00:29:26.640> IP<00:29:27.000> address 00:29:31.430 --> 00:29:31.440 align:start position:0% 00:29:31.440 --> 00:29:33.889 align:start position:0% it<00:29:31.980> tells<00:29:32.279> us<00:29:32.340> that<00:29:32.820> I<00:29:33.179> don't<00:29:33.659> have<00:29:33.779> any 00:29:33.889 --> 00:29:33.899 align:start position:0% it tells us that I don't have any 00:29:33.899 --> 00:29:36.649 align:start position:0% it tells us that I don't have any credits<00:29:34.320> to<00:29:34.440> actually<00:29:34.620> run<00:29:34.919> this<00:29:35.220> scan<00:29:35.700> submit 00:29:36.649 --> 00:29:36.659 align:start position:0% credits to actually run this scan submit 00:29:36.659 --> 00:29:38.510 align:start position:0% credits to actually run this scan submit so<00:29:36.840> I<00:29:37.020> would<00:29:37.140> need<00:29:37.320> to<00:29:37.440> actually<00:29:37.620> go<00:29:37.980> and<00:29:38.340> pay 00:29:38.510 --> 00:29:38.520 align:start position:0% so I would need to actually go and pay 00:29:38.520 --> 00:29:41.630 align:start position:0% so I would need to actually go and pay in<00:29:38.820> order<00:29:38.880> to<00:29:39.120> make<00:29:39.299> get<00:29:39.539> my<00:29:39.840> I<00:29:40.200> my<00:29:40.799> API<00:29:41.399> key 00:29:41.630 --> 00:29:41.640 align:start position:0% in order to make get my I my API key 00:29:41.640 --> 00:29:44.330 align:start position:0% in order to make get my I my API key right<00:29:41.880> here<00:29:42.120> some<00:29:42.419> credits<00:29:42.899> but<00:29:43.620> I<00:29:43.919> am<00:29:44.100> not 00:29:44.330 --> 00:29:44.340 align:start position:0% right here some credits but I am not 00:29:44.340 --> 00:29:45.950 align:start position:0% right here some credits but I am not going<00:29:44.520> to<00:29:44.640> do<00:29:44.760> that<00:29:44.940> so<00:29:45.179> this<00:29:45.419> is<00:29:45.539> another<00:29:45.720> way 00:29:45.950 --> 00:29:45.960 align:start position:0% going to do that so this is another way 00:29:45.960 --> 00:29:49.250 align:start position:0% going to do that so this is another way to<00:29:46.140> go<00:29:46.380> ahead<00:29:46.559> and<00:29:47.279> scan<00:29:47.760> a<00:29:48.299> network<00:29:48.539> or<00:29:48.899> an<00:29:49.020> IP 00:29:49.250 --> 00:29:49.260 align:start position:0% to go ahead and scan a network or an IP 00:29:49.260 --> 00:29:51.470 align:start position:0% to go ahead and scan a network or an IP address<00:29:49.440> to<00:29:49.860> find<00:29:50.039> what<00:29:50.340> is<00:29:50.520> open<00:29:50.700> and<00:29:51.120> do<00:29:51.299> a 00:29:51.470 --> 00:29:51.480 align:start position:0% address to find what is open and do a 00:29:51.480 --> 00:29:53.870 align:start position:0% address to find what is open and do a little<00:29:51.600> more<00:29:51.720> Recon<00:29:52.200> with<00:29:52.559> this<00:29:52.740> you<00:29:53.340> can<00:29:53.460> also 00:29:53.870 --> 00:29:53.880 align:start position:0% little more Recon with this you can also 00:29:53.880 --> 00:29:56.690 align:start position:0% little more Recon with this you can also go<00:29:54.299> out<00:29:54.539> to<00:29:54.840> I've<00:29:55.559> I<00:29:55.860> cannot<00:29:56.100> remember<00:29:56.279> what<00:29:56.580> is 00:29:56.690 --> 00:29:56.700 align:start position:0% go out to I've I cannot remember what is 00:29:56.700 --> 00:29:59.529 align:start position:0% go out to I've I cannot remember what is called<00:29:56.820> Hurricane<00:29:57.240> Electric<00:29:57.659> I<00:29:58.080> think<00:29:58.200> it's 00:29:59.529 --> 00:29:59.539 align:start position:0% called Hurricane Electric I think it's 00:29:59.539 --> 00:30:02.750 align:start position:0% called Hurricane Electric I think it's vgp.h<00:30:00.559> e.net<00:30:01.559> all<00:30:01.740> right<00:30:01.919> so<00:30:02.039> here<00:30:02.279> we<00:30:02.399> are<00:30:02.520> we 00:30:02.750 --> 00:30:02.760 align:start position:0% vgp.h e.net all right so here we are we 00:30:02.760 --> 00:30:05.630 align:start position:0% vgp.h e.net all right so here we are we can<00:30:02.880> just<00:30:03.000> type<00:30:03.179> in<00:30:03.419> yahoo.com 00:30:05.630 --> 00:30:05.640 align:start position:0% can just type in yahoo.com 00:30:05.640 --> 00:30:08.330 align:start position:0% can just type in yahoo.com and<00:30:06.059> I've<00:30:06.240> shown<00:30:06.480> this<00:30:06.659> before<00:30:07.039> in<00:30:08.039> another 00:30:08.330 --> 00:30:08.340 align:start position:0% and I've shown this before in another 00:30:08.340 --> 00:30:10.490 align:start position:0% and I've shown this before in another video<00:30:08.880> so<00:30:09.240> we'll<00:30:09.419> just<00:30:09.539> go<00:30:09.659> Yahoo<00:30:09.899> and<00:30:10.440> this 00:30:10.490 --> 00:30:10.500 align:start position:0% video so we'll just go Yahoo and this 00:30:10.500 --> 00:30:11.990 align:start position:0% video so we'll just go Yahoo and this website<00:30:10.799> seems<00:30:11.100> to<00:30:11.159> be<00:30:11.279> running<00:30:11.399> really<00:30:11.700> slow 00:30:11.990 --> 00:30:12.000 align:start position:0% website seems to be running really slow 00:30:12.000 --> 00:30:14.330 align:start position:0% website seems to be running really slow but<00:30:12.419> you<00:30:12.659> would<00:30:12.840> just<00:30:13.020> run<00:30:13.320> the<00:30:13.620> search<00:30:13.799> up<00:30:14.100> and 00:30:14.330 --> 00:30:14.340 align:start position:0% but you would just run the search up and 00:30:14.340 --> 00:30:16.010 align:start position:0% but you would just run the search up and it<00:30:14.520> has<00:30:14.640> come<00:30:14.820> back<00:30:14.940> so<00:30:15.179> you<00:30:15.299> can<00:30:15.360> grab<00:30:15.600> these 00:30:16.010 --> 00:30:16.020 align:start position:0% it has come back so you can grab these 00:30:16.020 --> 00:30:19.190 align:start position:0% it has come back so you can grab these as<00:30:16.679> numbers<00:30:17.039> right<00:30:17.340> here<00:30:17.520> or<00:30:17.820> these<00:30:18.299> asns<00:30:18.960> is 00:30:19.190 --> 00:30:19.200 align:start position:0% as numbers right here or these asns is 00:30:19.200 --> 00:30:21.529 align:start position:0% as numbers right here or these asns is the<00:30:19.380> easier<00:30:19.620> way<00:30:19.740> to<00:30:19.860> say<00:30:19.980> it<00:30:20.159> and<00:30:20.820> I<00:30:21.179> would<00:30:21.299> run 00:30:21.529 --> 00:30:21.539 align:start position:0% the easier way to say it and I would run 00:30:21.539 --> 00:30:23.330 align:start position:0% the easier way to say it and I would run these<00:30:21.840> through<00:30:22.080> a<00:30:22.380> mass<00:30:22.620> personally<00:30:23.159> because 00:30:23.330 --> 00:30:23.340 align:start position:0% these through a mass personally because 00:30:23.340 --> 00:30:25.490 align:start position:0% these through a mass personally because it<00:30:23.580> would<00:30:23.700> be<00:30:23.820> easier<00:30:24.120> but<00:30:24.720> you<00:30:24.960> can<00:30:25.020> run<00:30:25.200> these 00:30:25.490 --> 00:30:25.500 align:start position:0% it would be easier but you can run these 00:30:25.500 --> 00:30:27.409 align:start position:0% it would be easier but you can run these through<00:30:25.799> showdan<00:30:26.580> as<00:30:26.760> well<00:30:26.820> Showdown<00:30:27.299> is 00:30:27.409 --> 00:30:27.419 align:start position:0% through showdan as well Showdown is 00:30:27.419 --> 00:30:28.730 align:start position:0% through showdan as well Showdown is going<00:30:27.600> to<00:30:27.659> be<00:30:27.720> a<00:30:27.779> lot<00:30:27.840> faster<00:30:28.020> because<00:30:28.380> all<00:30:28.620> it 00:30:28.730 --> 00:30:28.740 align:start position:0% going to be a lot faster because all it 00:30:28.740 --> 00:30:30.730 align:start position:0% going to be a lot faster because all it has<00:30:28.799> to<00:30:28.919> do<00:30:28.980> is<00:30:29.100> query<00:30:29.399> back<00:30:29.640> to<00:30:29.820> the<00:30:30.179> database 00:30:30.730 --> 00:30:30.740 align:start position:0% has to do is query back to the database 00:30:30.740 --> 00:30:34.250 align:start position:0% has to do is query back to the database whereas<00:30:31.740> amass<00:30:32.700> seems<00:30:33.179> to<00:30:33.299> take<00:30:33.720> quite<00:30:34.020> a<00:30:34.140> bit 00:30:34.250 --> 00:30:34.260 align:start position:0% whereas amass seems to take quite a bit 00:30:34.260 --> 00:30:36.470 align:start position:0% whereas amass seems to take quite a bit longer<00:30:34.679> in<00:30:35.159> getting<00:30:35.700> you<00:30:35.880> the<00:30:36.299> information 00:30:36.470 --> 00:30:36.480 align:start position:0% longer in getting you the information 00:30:36.480 --> 00:30:39.409 align:start position:0% longer in getting you the information back<00:30:37.320> but<00:30:37.799> you<00:30:37.980> can<00:30:38.100> come<00:30:38.220> out<00:30:38.399> here<00:30:38.640> and<00:30:39.120> grab 00:30:39.409 --> 00:30:39.419 align:start position:0% back but you can come out here and grab 00:30:39.419 --> 00:30:41.930 align:start position:0% back but you can come out here and grab a<00:30:39.659> network<00:30:39.840> rage<00:30:40.320> scan<00:30:40.860> a<00:30:41.100> network<00:30:41.279> range<00:30:41.700> you 00:30:41.930 --> 00:30:41.940 align:start position:0% a network rage scan a network range you 00:30:41.940 --> 00:30:44.870 align:start position:0% a network rage scan a network range you can<00:30:42.000> look<00:30:42.179> through<00:30:42.480> these<00:30:43.080> asns<00:30:44.039> and<00:30:44.399> see<00:30:44.580> what 00:30:44.870 --> 00:30:44.880 align:start position:0% can look through these asns and see what 00:30:44.880 --> 00:30:46.549 align:start position:0% can look through these asns and see what you<00:30:45.000> can<00:30:45.120> find<00:30:45.360> right<00:30:45.720> here<00:30:45.899> I've<00:30:46.320> already 00:30:46.549 --> 00:30:46.559 align:start position:0% you can find right here I've already 00:30:46.559 --> 00:30:47.870 align:start position:0% you can find right here I've already made<00:30:46.740> a<00:30:46.860> video<00:30:46.980> about<00:30:47.159> that<00:30:47.340> so<00:30:47.520> I'm<00:30:47.640> not<00:30:47.760> going 00:30:47.870 --> 00:30:47.880 align:start position:0% made a video about that so I'm not going 00:30:47.880 --> 00:30:50.389 align:start position:0% made a video about that so I'm not going to<00:30:48.000> go<00:30:48.120> into<00:30:48.360> too<00:30:48.779> much<00:30:48.960> detail<00:30:49.500> about<00:30:50.100> that 00:30:50.389 --> 00:30:50.399 align:start position:0% to go into too much detail about that 00:30:50.399 --> 00:30:53.630 align:start position:0% to go into too much detail about that but<00:30:50.760> like<00:30:51.059> I<00:30:51.240> said<00:30:51.360> I<00:30:51.899> personally<00:30:52.200> would<00:30:52.799> go 00:30:53.630 --> 00:30:53.640 align:start position:0% but like I said I personally would go 00:30:53.640 --> 00:30:56.330 align:start position:0% but like I said I personally would go with<00:30:54.419> nmap<00:30:55.080> if<00:30:55.260> I<00:30:55.440> was<00:30:55.500> going<00:30:55.679> to<00:30:55.799> scan<00:30:56.039> any 00:30:56.330 --> 00:30:56.340 align:start position:0% with nmap if I was going to scan any 00:30:56.340 --> 00:30:57.889 align:start position:0% with nmap if I was going to scan any kind<00:30:56.520> of<00:30:56.640> network<00:30:56.880> or<00:30:57.179> anything<00:30:57.360> like<00:30:57.720> that 00:30:57.889 --> 00:30:57.899 align:start position:0% kind of network or anything like that 00:30:57.899 --> 00:31:00.230 align:start position:0% kind of network or anything like that now<00:30:58.559> we're<00:30:58.740> going<00:30:58.860> to<00:30:58.980> move<00:30:59.100> on<00:30:59.279> to<00:30:59.520> the<00:31:00.059> web 00:31:00.230 --> 00:31:00.240 align:start position:0% now we're going to move on to the web 00:31:00.240 --> 00:31:01.549 align:start position:0% now we're going to move on to the web browser<00:31:00.659> so<00:31:00.960> what's<00:31:01.080> really<00:31:01.260> cool<00:31:01.440> about 00:31:01.549 --> 00:31:01.559 align:start position:0% browser so what's really cool about 00:31:01.559 --> 00:31:03.649 align:start position:0% browser so what's really cool about running<00:31:01.799> Showdown<00:31:02.340> in<00:31:02.580> the<00:31:02.700> browser<00:31:03.000> is<00:31:03.419> they 00:31:03.649 --> 00:31:03.659 align:start position:0% running Showdown in the browser is they 00:31:03.659 --> 00:31:05.450 align:start position:0% running Showdown in the browser is they give<00:31:03.840> you<00:31:03.960> this<00:31:04.140> filters<00:31:04.559> cheat<00:31:04.860> sheet<00:31:05.220> so<00:31:05.340> if 00:31:05.450 --> 00:31:05.460 align:start position:0% give you this filters cheat sheet so if 00:31:05.460 --> 00:31:08.269 align:start position:0% give you this filters cheat sheet so if you<00:31:05.580> you<00:31:06.000> wanted<00:31:06.240> to<00:31:06.480> look<00:31:06.840> for<00:31:07.200> a<00:31:07.860> specific 00:31:08.269 --> 00:31:08.279 align:start position:0% you you wanted to look for a specific 00:31:08.279 --> 00:31:11.149 align:start position:0% you you wanted to look for a specific Network<00:31:08.580> or<00:31:09.000> a<00:31:09.120> range<00:31:09.419> or<00:31:09.779> a<00:31:10.140> cider<00:31:10.620> range<00:31:10.860> you 00:31:11.149 --> 00:31:11.159 align:start position:0% Network or a range or a cider range you 00:31:11.159 --> 00:31:13.130 align:start position:0% Network or a range or a cider range you can<00:31:11.220> do<00:31:11.399> that<00:31:11.580> right<00:31:11.940> here<00:31:12.179> through<00:31:12.659> the 00:31:13.130 --> 00:31:13.140 align:start position:0% can do that right here through the 00:31:13.140 --> 00:31:15.610 align:start position:0% can do that right here through the search<00:31:13.380> filter<00:31:13.740> and<00:31:14.340> the<00:31:14.700> way<00:31:14.820> you<00:31:15.120> would<00:31:15.299> do 00:31:15.610 --> 00:31:15.620 align:start position:0% search filter and the way you would do 00:31:15.620 --> 00:31:18.950 align:start position:0% search filter and the way you would do these<00:31:16.620> commands<00:31:17.220> is<00:31:17.580> by<00:31:17.880> typing<00:31:18.179> in<00:31:18.360> say<00:31:18.720> we 00:31:18.950 --> 00:31:18.960 align:start position:0% these commands is by typing in say we 00:31:18.960 --> 00:31:21.350 align:start position:0% these commands is by typing in say we wanted<00:31:19.140> to<00:31:19.500> find<00:31:20.100> the<00:31:20.340> organization<00:31:20.880> Yahoo 00:31:21.350 --> 00:31:21.360 align:start position:0% wanted to find the organization Yahoo 00:31:21.360 --> 00:31:23.510 align:start position:0% wanted to find the organization Yahoo like<00:31:21.840> this<00:31:22.020> we<00:31:22.380> can<00:31:22.559> search<00:31:22.919> it<00:31:23.100> and<00:31:23.340> it's 00:31:23.510 --> 00:31:23.520 align:start position:0% like this we can search it and it's 00:31:23.520 --> 00:31:25.490 align:start position:0% like this we can search it and it's going<00:31:23.700> to<00:31:23.700> pull<00:31:23.880> it<00:31:24.059> down<00:31:24.240> for<00:31:24.600> us<00:31:24.779> let's<00:31:25.260> see 00:31:25.490 --> 00:31:25.500 align:start position:0% going to pull it down for us let's see 00:31:25.500 --> 00:31:28.370 align:start position:0% going to pull it down for us let's see what<00:31:25.620> else<00:31:25.740> I've<00:31:25.980> ran<00:31:26.220> up<00:31:26.520> here 00:31:28.370 --> 00:31:28.380 align:start position:0% what else I've ran up here 00:31:28.380 --> 00:31:30.529 align:start position:0% what else I've ran up here if<00:31:28.620> we<00:31:28.799> delete<00:31:29.100> this 00:31:30.529 --> 00:31:30.539 align:start position:0% if we delete this 00:31:30.539 --> 00:31:34.130 align:start position:0% if we delete this we<00:31:31.260> can<00:31:31.500> run<00:31:31.799> an<00:31:32.220> IP<00:31:32.520> address<00:31:32.840> and<00:31:33.840> we<00:31:34.020> already 00:31:34.130 --> 00:31:34.140 align:start position:0% we can run an IP address and we already 00:31:34.140 --> 00:31:36.110 align:start position:0% we can run an IP address and we already ran<00:31:34.440> this<00:31:34.620> one<00:31:34.799> and<00:31:35.220> it'll<00:31:35.460> pull<00:31:35.640> down<00:31:35.880> the 00:31:36.110 --> 00:31:36.120 align:start position:0% ran this one and it'll pull down the 00:31:36.120 --> 00:31:38.210 align:start position:0% ran this one and it'll pull down the information<00:31:36.419> here's<00:31:37.140> that<00:31:37.320> Port<00:31:37.559> 80<00:31:37.799> that<00:31:38.100> it 00:31:38.210 --> 00:31:38.220 align:start position:0% information here's that Port 80 that it 00:31:38.220 --> 00:31:41.269 align:start position:0% information here's that Port 80 that it said<00:31:38.340> was<00:31:38.520> open<00:31:38.700> here's<00:31:39.419> Port<00:31:39.659> 443<00:31:40.559> and<00:31:40.919> it<00:31:41.100> has 00:31:41.269 --> 00:31:41.279 align:start position:0% said was open here's Port 443 and it has 00:31:41.279 --> 00:31:44.090 align:start position:0% said was open here's Port 443 and it has grabbed<00:31:41.820> us<00:31:42.059> all<00:31:42.720> of<00:31:42.960> the<00:31:43.260> banners<00:31:43.740> right<00:31:43.980> here 00:31:44.090 --> 00:31:44.100 align:start position:0% grabbed us all of the banners right here 00:31:44.100 --> 00:31:45.830 align:start position:0% grabbed us all of the banners right here and<00:31:44.279> we<00:31:44.460> can<00:31:44.580> read<00:31:44.880> through<00:31:45.120> them<00:31:45.299> and<00:31:45.600> see 00:31:45.830 --> 00:31:45.840 align:start position:0% and we can read through them and see 00:31:45.840 --> 00:31:48.230 align:start position:0% and we can read through them and see what<00:31:46.200> is<00:31:46.380> running<00:31:47.100> you<00:31:47.700> can<00:31:47.760> also<00:31:48.000> download 00:31:48.230 --> 00:31:48.240 align:start position:0% what is running you can also download 00:31:48.240 --> 00:31:50.990 align:start position:0% what is running you can also download the<00:31:48.840> reports<00:31:49.440> from<00:31:49.799> here<00:31:50.100> as<00:31:50.340> well<00:31:50.460> one<00:31:50.880> of<00:31:50.940> the 00:31:50.990 --> 00:31:51.000 align:start position:0% the reports from here as well one of the 00:31:51.000 --> 00:31:53.630 align:start position:0% the reports from here as well one of the cool<00:31:51.179> things<00:31:51.480> about<00:31:52.159> one<00:31:53.159> of<00:31:53.279> the<00:31:53.340> cool<00:31:53.460> things 00:31:53.630 --> 00:31:53.640 align:start position:0% cool things about one of the cool things 00:31:53.640 --> 00:31:56.510 align:start position:0% cool things about one of the cool things about<00:31:53.940> running<00:31:54.299> through<00:31:54.960> the<00:31:55.559> browser<00:31:56.100> is<00:31:56.220> you 00:31:56.510 --> 00:31:56.520 align:start position:0% about running through the browser is you 00:31:56.520 --> 00:31:58.070 align:start position:0% about running through the browser is you can<00:31:56.580> actually<00:31:56.700> look<00:31:57.179> for<00:31:57.480> sensitive 00:31:58.070 --> 00:31:58.080 align:start position:0% can actually look for sensitive 00:31:58.080 --> 00:32:00.110 align:start position:0% can actually look for sensitive information<00:31:58.580> disclosures<00:31:59.580> if<00:31:59.880> you<00:32:00.000> just 00:32:00.110 --> 00:32:00.120 align:start position:0% information disclosures if you just 00:32:00.120 --> 00:32:02.570 align:start position:0% information disclosures if you just continue<00:32:00.299> to<00:32:00.659> look<00:32:01.020> through<00:32:01.260> here<00:32:01.559> and<00:32:02.279> you'll 00:32:02.570 --> 00:32:02.580 align:start position:0% continue to look through here and you'll 00:32:02.580 --> 00:32:04.789 align:start position:0% continue to look through here and you'll need<00:32:02.700> to<00:32:02.880> read<00:32:03.120> through<00:32:03.539> the<00:32:04.080> cheat<00:32:04.260> sheet<00:32:04.679> and 00:32:04.789 --> 00:32:04.799 align:start position:0% need to read through the cheat sheet and 00:32:04.799 --> 00:32:06.529 align:start position:0% need to read through the cheat sheet and I<00:32:04.919> would<00:32:05.039> also<00:32:05.279> recommend<00:32:05.820> reading<00:32:06.299> through 00:32:06.529 --> 00:32:06.539 align:start position:0% I would also recommend reading through 00:32:06.539 --> 00:32:09.110 align:start position:0% I would also recommend reading through like<00:32:06.899> their<00:32:07.080> documentation<00:32:07.679> because<00:32:08.520> there's 00:32:09.110 --> 00:32:09.120 align:start position:0% like their documentation because there's 00:32:09.120 --> 00:32:10.909 align:start position:0% like their documentation because there's way<00:32:09.539> more<00:32:09.720> examples<00:32:10.200> that<00:32:10.559> you're<00:32:10.740> going<00:32:10.860> to 00:32:10.909 --> 00:32:10.919 align:start position:0% way more examples that you're going to 00:32:10.919 --> 00:32:12.889 align:start position:0% way more examples that you're going to be<00:32:11.039> able<00:32:11.159> to<00:32:11.340> use<00:32:11.820> so<00:32:12.120> if<00:32:12.299> we<00:32:12.419> wanted<00:32:12.600> to<00:32:12.779> look 00:32:12.889 --> 00:32:12.899 align:start position:0% be able to use so if we wanted to look 00:32:12.899 --> 00:32:14.930 align:start position:0% be able to use so if we wanted to look for<00:32:13.080> something<00:32:13.260> that's<00:32:13.500> running<00:32:13.679> Apache<00:32:14.399> with 00:32:14.930 --> 00:32:14.940 align:start position:0% for something that's running Apache with 00:32:14.940 --> 00:32:17.269 align:start position:0% for something that's running Apache with a<00:32:15.299> specific<00:32:15.600> Apache<00:32:16.260> version<00:32:16.620> you<00:32:17.039> could<00:32:17.100> look 00:32:17.269 --> 00:32:17.279 align:start position:0% a specific Apache version you could look 00:32:17.279 --> 00:32:20.990 align:start position:0% a specific Apache version you could look to<00:32:17.460> see<00:32:17.700> if<00:32:18.360> you're<00:32:18.480> able<00:32:18.840> to<00:32:19.200> run<00:32:19.799> maybe<00:32:20.279> there 00:32:20.990 --> 00:32:21.000 align:start position:0% to see if you're able to run maybe there 00:32:21.000 --> 00:32:23.409 align:start position:0% to see if you're able to run maybe there is<00:32:21.240> a<00:32:21.960> Apache 00:32:23.409 --> 00:32:23.419 align:start position:0% is a Apache 00:32:23.419 --> 00:32:25.850 align:start position:0% is a Apache 1.7.4<00:32:24.419> that<00:32:24.779> actually<00:32:24.899> has<00:32:25.140> a<00:32:25.320> vulnerability 00:32:25.850 --> 00:32:25.860 align:start position:0% 1.7.4 that actually has a vulnerability 00:32:25.860 --> 00:32:27.289 align:start position:0% 1.7.4 that actually has a vulnerability you<00:32:26.220> can<00:32:26.279> come<00:32:26.399> up<00:32:26.580> here<00:32:26.640> and<00:32:26.880> you<00:32:27.059> can<00:32:27.120> just 00:32:27.289 --> 00:32:27.299 align:start position:0% you can come up here and you can just 00:32:27.299 --> 00:32:29.389 align:start position:0% you can come up here and you can just type<00:32:27.480> in<00:32:27.659> the<00:32:27.899> product<00:32:28.020> Apache<00:32:28.679> with<00:32:29.279> the 00:32:29.389 --> 00:32:29.399 align:start position:0% type in the product Apache with the 00:32:29.399 --> 00:32:31.850 align:start position:0% type in the product Apache with the version<00:32:29.580> number<00:32:29.940> and<00:32:30.480> and<00:32:31.020> see<00:32:31.440> if<00:32:31.679> you're 00:32:31.850 --> 00:32:31.860 align:start position:0% version number and and see if you're 00:32:31.860 --> 00:32:35.570 align:start position:0% version number and and see if you're able<00:32:32.220> to<00:32:32.340> find<00:32:33.059> any<00:32:34.020> vulnerabilities<00:32:34.980> for 00:32:35.570 --> 00:32:35.580 align:start position:0% able to find any vulnerabilities for 00:32:35.580 --> 00:32:38.210 align:start position:0% able to find any vulnerabilities for that<00:32:35.940> Apache<00:32:36.539> version<00:32:36.960> just<00:32:37.440> like<00:32:37.620> this<00:32:37.799> and 00:32:38.210 --> 00:32:38.220 align:start position:0% that Apache version just like this and 00:32:38.220 --> 00:32:39.289 align:start position:0% that Apache version just like this and you<00:32:38.340> would<00:32:38.460> run<00:32:38.580> through<00:32:38.760> here<00:32:38.880> and<00:32:39.000> say<00:32:39.179> okay 00:32:39.289 --> 00:32:39.299 align:start position:0% you would run through here and say okay 00:32:39.299 --> 00:32:41.389 align:start position:0% you would run through here and say okay these<00:32:39.840> people<00:32:40.020> might<00:32:40.620> be<00:32:40.799> vulnerable<00:32:41.100> to<00:32:41.220> this 00:32:41.389 --> 00:32:41.399 align:start position:0% these people might be vulnerable to this 00:32:41.399 --> 00:32:42.889 align:start position:0% these people might be vulnerable to this do<00:32:41.580> they<00:32:41.760> have<00:32:41.820> a<00:32:41.940> bug<00:32:42.059> banning<00:32:42.480> program<00:32:42.659> okay 00:32:42.889 --> 00:32:42.899 align:start position:0% do they have a bug banning program okay 00:32:42.899 --> 00:32:45.830 align:start position:0% do they have a bug banning program okay these<00:32:43.320> people<00:32:43.500> are<00:32:44.100> running<00:32:44.340> this<00:32:44.940> version<00:32:45.179> do 00:32:45.830 --> 00:32:45.840 align:start position:0% these people are running this version do 00:32:45.840 --> 00:32:47.810 align:start position:0% these people are running this version do they<00:32:46.020> have<00:32:46.200> a<00:32:46.320> bug<00:32:46.440> burning<00:32:46.919> program<00:32:47.039> and<00:32:47.640> so 00:32:47.810 --> 00:32:47.820 align:start position:0% they have a bug burning program and so 00:32:47.820 --> 00:32:49.190 align:start position:0% they have a bug burning program and so there's<00:32:48.000> a<00:32:48.179> lot<00:32:48.299> of<00:32:48.419> different<00:32:48.539> ways<00:32:48.899> you<00:32:49.080> can 00:32:49.190 --> 00:32:49.200 align:start position:0% there's a lot of different ways you can 00:32:49.200 --> 00:32:52.190 align:start position:0% there's a lot of different ways you can be<00:32:49.440> creative<00:32:49.980> with<00:32:50.640> looking<00:32:51.000> for<00:32:51.539> known 00:32:52.190 --> 00:32:52.200 align:start position:0% be creative with looking for known 00:32:52.200 --> 00:32:55.070 align:start position:0% be creative with looking for known vulnerabilities<00:32:52.860> new<00:32:53.399> cves<00:32:53.940> looking<00:32:54.600> for<00:32:54.779> bug 00:32:55.070 --> 00:32:55.080 align:start position:0% vulnerabilities new cves looking for bug 00:32:55.080 --> 00:32:57.110 align:start position:0% vulnerabilities new cves looking for bug Bounty<00:32:55.500> programs<00:32:55.919> that<00:32:56.100> are<00:32:56.340> vulnerable<00:32:56.820> and 00:32:57.110 --> 00:32:57.120 align:start position:0% Bounty programs that are vulnerable and 00:32:57.120 --> 00:32:58.730 align:start position:0% Bounty programs that are vulnerable and then<00:32:57.240> you<00:32:57.419> can<00:32:57.600> look<00:32:57.779> for<00:32:58.080> sensitive 00:32:58.730 --> 00:32:58.740 align:start position:0% then you can look for sensitive 00:32:58.740 --> 00:33:01.190 align:start position:0% then you can look for sensitive information<00:32:59.100> with<00:33:00.000> showdan<00:33:00.600> because<00:33:00.840> it 00:33:01.190 --> 00:33:01.200 align:start position:0% information with showdan because it 00:33:01.200 --> 00:33:02.570 align:start position:0% information with showdan because it doesn't<00:33:01.320> know<00:33:01.679> what<00:33:02.039> is<00:33:02.220> going<00:33:02.340> to<00:33:02.460> be 00:33:02.570 --> 00:33:02.580 align:start position:0% doesn't know what is going to be 00:33:02.580 --> 00:33:04.789 align:start position:0% doesn't know what is going to be sensitive<00:33:02.940> or<00:33:03.120> not<00:33:03.240> it's<00:33:03.539> just<00:33:03.779> going<00:33:04.020> to<00:33:04.200> grab 00:33:04.789 --> 00:33:04.799 align:start position:0% sensitive or not it's just going to grab 00:33:04.799 --> 00:33:06.409 align:start position:0% sensitive or not it's just going to grab all<00:33:05.039> of<00:33:05.159> the<00:33:05.279> information<00:33:05.460> and<00:33:05.880> stored<00:33:06.179> in<00:33:06.299> the 00:33:06.409 --> 00:33:06.419 align:start position:0% all of the information and stored in the 00:33:06.419 --> 00:33:08.570 align:start position:0% all of the information and stored in the database<00:33:06.779> and<00:33:07.020> it's<00:33:07.140> up<00:33:07.320> to<00:33:07.500> you<00:33:07.740> as<00:33:08.100> the<00:33:08.340> bug 00:33:08.570 --> 00:33:08.580 align:start position:0% database and it's up to you as the bug 00:33:08.580 --> 00:33:10.250 align:start position:0% database and it's up to you as the bug Bounty<00:33:09.059> Hunter<00:33:09.179> to<00:33:09.539> look<00:33:09.659> at<00:33:09.779> that<00:33:09.960> specific 00:33:10.250 --> 00:33:10.260 align:start position:0% Bounty Hunter to look at that specific 00:33:10.260 --> 00:33:11.990 align:start position:0% Bounty Hunter to look at that specific Target<00:33:10.500> and<00:33:10.860> see<00:33:10.980> if<00:33:11.100> there's<00:33:11.279> any<00:33:11.520> sensitive 00:33:11.990 --> 00:33:12.000 align:start position:0% Target and see if there's any sensitive 00:33:12.000 --> 00:33:14.509 align:start position:0% Target and see if there's any sensitive information<00:33:12.299> being<00:33:13.200> disclosed<00:33:13.799> on<00:33:13.980> Showdown 00:33:14.509 --> 00:33:14.519 align:start position:0% information being disclosed on Showdown 00:33:14.519 --> 00:33:16.909 align:start position:0% information being disclosed on Showdown and<00:33:14.700> then<00:33:14.880> you<00:33:15.120> can<00:33:15.360> report<00:33:15.840> it<00:33:16.140> okay<00:33:16.440> and<00:33:16.740> one 00:33:16.909 --> 00:33:16.919 align:start position:0% and then you can report it okay and one 00:33:16.919 --> 00:33:18.470 align:start position:0% and then you can report it okay and one of<00:33:17.039> the<00:33:17.100> last<00:33:17.279> things<00:33:17.519> I<00:33:17.760> want<00:33:17.880> to<00:33:18.000> cover<00:33:18.120> is 00:33:18.470 --> 00:33:18.480 align:start position:0% of the last things I want to cover is 00:33:18.480 --> 00:33:20.210 align:start position:0% of the last things I want to cover is the<00:33:18.779> monitor<00:33:19.260> function<00:33:19.559> and<00:33:19.860> you<00:33:19.980> have<00:33:20.100> to 00:33:20.210 --> 00:33:20.220 align:start position:0% the monitor function and you have to 00:33:20.220 --> 00:33:22.610 align:start position:0% the monitor function and you have to have<00:33:20.340> an<00:33:20.519> account<00:33:20.640> in<00:33:20.940> order<00:33:21.059> to<00:33:21.360> use<00:33:21.720> this<00:33:21.960> but 00:33:22.610 --> 00:33:22.620 align:start position:0% have an account in order to use this but 00:33:22.620 --> 00:33:24.350 align:start position:0% have an account in order to use this but this<00:33:22.860> is<00:33:22.980> something<00:33:23.220> that<00:33:23.640> you<00:33:23.940> might<00:33:24.240> be 00:33:24.350 --> 00:33:24.360 align:start position:0% this is something that you might be 00:33:24.360 --> 00:33:26.630 align:start position:0% this is something that you might be interested<00:33:24.720> in<00:33:24.840> the<00:33:25.380> monitoring<00:33:25.980> is<00:33:26.279> you<00:33:26.519> can 00:33:26.630 --> 00:33:26.640 align:start position:0% interested in the monitoring is you can 00:33:26.640 --> 00:33:29.389 align:start position:0% interested in the monitoring is you can enter<00:33:26.880> in<00:33:27.120> a<00:33:27.539> specific<00:33:27.899> Target<00:33:28.140> such<00:33:29.039> as 00:33:29.389 --> 00:33:29.399 align:start position:0% enter in a specific Target such as 00:33:29.399 --> 00:33:32.509 align:start position:0% enter in a specific Target such as yahoo.com<00:33:30.600> and<00:33:31.320> it<00:33:31.679> will<00:33:31.799> update<00:33:32.279> you 00:33:32.509 --> 00:33:32.519 align:start position:0% yahoo.com and it will update you 00:33:32.519 --> 00:33:34.789 align:start position:0% yahoo.com and it will update you whenever<00:33:33.240> a<00:33:33.720> new<00:33:33.840> software<00:33:34.200> comes<00:33:34.500> out<00:33:34.620> or 00:33:34.789 --> 00:33:34.799 align:start position:0% whenever a new software comes out or 00:33:34.799 --> 00:33:37.190 align:start position:0% whenever a new software comes out or whenever<00:33:35.039> there's<00:33:35.279> an<00:33:35.460> update<00:33:35.760> made<00:33:36.240> to<00:33:36.720> the 00:33:37.190 --> 00:33:37.200 align:start position:0% whenever there's an update made to the 00:33:37.200 --> 00:33:38.990 align:start position:0% whenever there's an update made to the program<00:33:37.500> that<00:33:37.980> you<00:33:38.100> are<00:33:38.220> trying<00:33:38.399> to<00:33:38.640> monitor 00:33:38.990 --> 00:33:39.000 align:start position:0% program that you are trying to monitor 00:33:39.000 --> 00:33:41.029 align:start position:0% program that you are trying to monitor it'll<00:33:39.600> let<00:33:39.779> you<00:33:39.960> know<00:33:40.140> and<00:33:40.440> you<00:33:40.559> can<00:33:40.620> be<00:33:40.740> one<00:33:40.919> of 00:33:41.029 --> 00:33:41.039 align:start position:0% it'll let you know and you can be one of 00:33:41.039 --> 00:33:42.710 align:start position:0% it'll let you know and you can be one of the<00:33:41.100> first<00:33:41.220> ones<00:33:41.580> to<00:33:41.700> go<00:33:41.820> and<00:33:42.059> check<00:33:42.240> out<00:33:42.419> that 00:33:42.710 --> 00:33:42.720 align:start position:0% the first ones to go and check out that 00:33:42.720 --> 00:33:45.470 align:start position:0% the first ones to go and check out that new<00:33:42.899> subdomain<00:33:43.620> or<00:33:44.100> domain<00:33:44.580> if<00:33:44.880> it<00:33:45.000> is<00:33:45.179> in 00:33:45.470 --> 00:33:45.480 align:start position:0% new subdomain or domain if it is in 00:33:45.480 --> 00:33:47.930 align:start position:0% new subdomain or domain if it is in scope<00:33:45.840> or<00:33:46.500> if<00:33:46.799> they<00:33:46.919> update<00:33:47.279> a<00:33:47.399> software<00:33:47.700> you 00:33:47.930 --> 00:33:47.940 align:start position:0% scope or if they update a software you 00:33:47.940 --> 00:33:49.370 align:start position:0% scope or if they update a software you can<00:33:48.059> be<00:33:48.179> one<00:33:48.360> of<00:33:48.480> the<00:33:48.539> first<00:33:48.659> ones<00:33:48.960> to<00:33:49.080> go<00:33:49.200> see 00:33:49.370 --> 00:33:49.380 align:start position:0% can be one of the first ones to go see 00:33:49.380 --> 00:33:51.590 align:start position:0% can be one of the first ones to go see if<00:33:49.559> there<00:33:49.679> are<00:33:49.799> any<00:33:49.860> cves<00:33:50.340> out<00:33:51.000> for<00:33:51.299> that 00:33:51.590 --> 00:33:51.600 align:start position:0% if there are any cves out for that 00:33:51.600 --> 00:33:54.049 align:start position:0% if there are any cves out for that specific<00:33:52.019> software<00:33:52.860> that<00:33:53.159> they<00:33:53.340> have<00:33:53.580> updated 00:33:54.049 --> 00:33:54.059 align:start position:0% specific software that they have updated 00:33:54.059 --> 00:33:56.690 align:start position:0% specific software that they have updated so<00:33:54.600> the<00:33:55.019> monitor<00:33:55.440> is<00:33:55.740> one<00:33:55.980> that<00:33:56.100> bug<00:33:56.279> mounting 00:33:56.690 --> 00:33:56.700 align:start position:0% so the monitor is one that bug mounting 00:33:56.700 --> 00:33:58.549 align:start position:0% so the monitor is one that bug mounting Hunters<00:33:57.000> really<00:33:57.360> like<00:33:57.480> to<00:33:57.659> use<00:33:57.779> because<00:33:58.140> you 00:33:58.549 --> 00:33:58.559 align:start position:0% Hunters really like to use because you 00:33:58.559 --> 00:34:00.769 align:start position:0% Hunters really like to use because you are<00:33:58.679> able<00:33:58.980> to<00:33:59.220> get<00:33:59.580> notifications<00:34:00.179> of<00:34:00.539> when 00:34:00.769 --> 00:34:00.779 align:start position:0% are able to get notifications of when 00:34:00.779 --> 00:34:02.930 align:start position:0% are able to get notifications of when things<00:34:01.019> change<00:34:01.380> on<00:34:01.740> a<00:34:01.860> specific<00:34:02.100> Target<00:34:02.340> and 00:34:02.930 --> 00:34:02.940 align:start position:0% things change on a specific Target and 00:34:02.940 --> 00:34:04.250 align:start position:0% things change on a specific Target and you'll<00:34:03.120> be<00:34:03.240> one<00:34:03.419> of<00:34:03.539> the<00:34:03.539> first<00:34:03.720> ones<00:34:03.960> to<00:34:04.140> know 00:34:04.250 --> 00:34:04.260 align:start position:0% you'll be one of the first ones to know 00:34:04.260 --> 00:34:06.470 align:start position:0% you'll be one of the first ones to know one<00:34:04.679> of<00:34:04.799> the<00:34:04.860> first<00:34:04.980> ones<00:34:05.220> to<00:34:05.340> be<00:34:05.519> able<00:34:05.640> to<00:34:05.820> go 00:34:06.470 --> 00:34:06.480 align:start position:0% one of the first ones to be able to go 00:34:06.480 --> 00:34:09.349 align:start position:0% one of the first ones to be able to go out<00:34:06.659> and<00:34:06.899> test<00:34:07.260> it<00:34:07.500> but<00:34:07.919> you<00:34:08.159> will<00:34:08.339> need<00:34:08.580> to<00:34:08.940> be 00:34:09.349 --> 00:34:09.359 align:start position:0% out and test it but you will need to be 00:34:09.359 --> 00:34:11.810 align:start position:0% out and test it but you will need to be willing<00:34:09.659> to<00:34:09.780> pay<00:34:09.960> seventy<00:34:10.679> dollars<00:34:10.980> a<00:34:11.280> month<00:34:11.399> I 00:34:11.810 --> 00:34:11.820 align:start position:0% willing to pay seventy dollars a month I 00:34:11.820 --> 00:34:14.030 align:start position:0% willing to pay seventy dollars a month I personally<00:34:12.179> don't<00:34:12.839> think<00:34:13.020> it's<00:34:13.200> worth<00:34:13.379> it<00:34:13.560> but 00:34:14.030 --> 00:34:14.040 align:start position:0% personally don't think it's worth it but 00:34:14.040 --> 00:34:15.829 align:start position:0% personally don't think it's worth it but I<00:34:14.220> know<00:34:14.399> there<00:34:14.760> are<00:34:14.879> a<00:34:15.060> lot<00:34:15.119> of<00:34:15.240> bug<00:34:15.359> mounting 00:34:15.829 --> 00:34:15.839 align:start position:0% I know there are a lot of bug mounting 00:34:15.839 --> 00:34:18.349 align:start position:0% I know there are a lot of bug mounting Hunters<00:34:16.139> who<00:34:16.740> do<00:34:17.040> think<00:34:17.220> it's<00:34:17.339> worth<00:34:17.580> it<00:34:17.700> so<00:34:18.000> it 00:34:18.349 --> 00:34:18.359 align:start position:0% Hunters who do think it's worth it so it 00:34:18.359 --> 00:34:21.349 align:start position:0% Hunters who do think it's worth it so it might<00:34:18.480> be<00:34:18.659> worth<00:34:18.899> it<00:34:19.139> to<00:34:19.560> you<00:34:19.800> to<00:34:20.520> Monitor<00:34:21.060> and 00:34:21.349 --> 00:34:21.359 align:start position:0% might be worth it to you to Monitor and 00:34:21.359 --> 00:34:23.510 align:start position:0% might be worth it to you to Monitor and just<00:34:21.540> pay<00:34:21.720> the<00:34:22.080> 70<00:34:22.320> a<00:34:22.740> month<00:34:22.859> so<00:34:23.099> that<00:34:23.220> you<00:34:23.399> can 00:34:23.510 --> 00:34:23.520 align:start position:0% just pay the 70 a month so that you can 00:34:23.520 --> 00:34:25.550 align:start position:0% just pay the 70 a month so that you can follow<00:34:23.760> specific<00:34:24.240> targets<00:34:24.659> and<00:34:25.080> be<00:34:25.260> one<00:34:25.440> of 00:34:25.550 --> 00:34:25.560 align:start position:0% follow specific targets and be one of 00:34:25.560 --> 00:34:28.190 align:start position:0% follow specific targets and be one of the<00:34:25.679> first<00:34:25.859> ones<00:34:26.339> to<00:34:26.760> go<00:34:27.060> out<00:34:27.240> and<00:34:27.659> check<00:34:27.960> those 00:34:28.190 --> 00:34:28.200 align:start position:0% the first ones to go out and check those 00:34:28.200 --> 00:34:30.290 align:start position:0% the first ones to go out and check those targets<00:34:28.679> for<00:34:28.919> vulnerabilities<00:34:29.639> so<00:34:30.060> that 00:34:30.290 --> 00:34:30.300 align:start position:0% targets for vulnerabilities so that 00:34:30.300 --> 00:34:32.690 align:start position:0% targets for vulnerabilities so that cones<00:34:30.540> includes<00:34:31.080> our<00:34:31.260> video<00:34:31.560> on<00:34:31.859> Showdown<00:34:32.399> one 00:34:32.690 --> 00:34:32.700 align:start position:0% cones includes our video on Showdown one 00:34:32.700 --> 00:34:34.250 align:start position:0% cones includes our video on Showdown one of<00:34:32.820> the<00:34:32.879> things<00:34:33.000> I<00:34:33.240> want<00:34:33.359> to<00:34:33.540> make<00:34:33.960> sure<00:34:34.139> you 00:34:34.250 --> 00:34:34.260 align:start position:0% of the things I want to make sure you 00:34:34.260 --> 00:34:36.050 align:start position:0% of the things I want to make sure you understand<00:34:34.440> is<00:34:34.980> that<00:34:35.159> when<00:34:35.399> you<00:34:35.580> run<00:34:35.820> a 00:34:36.050 --> 00:34:36.060 align:start position:0% understand is that when you run a 00:34:36.060 --> 00:34:37.310 align:start position:0% understand is that when you run a showdown<00:34:36.419> scan<00:34:36.720> and<00:34:36.839> you're<00:34:36.960> thinking<00:34:37.200> about 00:34:37.310 --> 00:34:37.320 align:start position:0% showdown scan and you're thinking about 00:34:37.320 --> 00:34:40.010 align:start position:0% showdown scan and you're thinking about trying<00:34:37.740> to<00:34:38.159> exploit<00:34:38.940> something<00:34:39.300> you<00:34:39.780> need<00:34:39.899> to 00:34:40.010 --> 00:34:40.020 align:start position:0% trying to exploit something you need to 00:34:40.020 --> 00:34:41.510 align:start position:0% trying to exploit something you need to make<00:34:40.200> sure<00:34:40.379> that<00:34:40.619> it's<00:34:40.740> in<00:34:40.859> scope<00:34:41.099> and<00:34:41.280> has<00:34:41.460> a 00:34:41.510 --> 00:34:41.520 align:start position:0% make sure that it's in scope and has a 00:34:41.520 --> 00:34:43.129 align:start position:0% make sure that it's in scope and has a bug<00:34:41.639> Bounty<00:34:42.060> program<00:34:42.179> otherwise<00:34:42.720> you<00:34:43.020> could 00:34:43.129 --> 00:34:43.139 align:start position:0% bug Bounty program otherwise you could 00:34:43.139 --> 00:34:45.409 align:start position:0% bug Bounty program otherwise you could be<00:34:43.320> getting<00:34:43.740> yourself<00:34:43.980> into<00:34:44.460> some<00:34:45.000> illegal 00:34:45.409 --> 00:34:45.419 align:start position:0% be getting yourself into some illegal 00:34:45.419 --> 00:34:47.030 align:start position:0% be getting yourself into some illegal trouble<00:34:45.780> and<00:34:46.200> make<00:34:46.379> sure<00:34:46.500> before<00:34:46.679> you<00:34:46.919> go 00:34:47.030 --> 00:34:47.040 align:start position:0% trouble and make sure before you go 00:34:47.040 --> 00:34:48.230 align:start position:0% trouble and make sure before you go ahead<00:34:47.159> and<00:34:47.280> start<00:34:47.460> looking<00:34:47.700> at<00:34:47.879> a<00:34:48.000> specific 00:34:48.230 --> 00:34:48.240 align:start position:0% ahead and start looking at a specific 00:34:48.240 --> 00:34:50.450 align:start position:0% ahead and start looking at a specific Target<00:34:48.480> to<00:34:49.020> see<00:34:49.379> if<00:34:49.500> it<00:34:49.619> has<00:34:49.740> a<00:34:49.919> bug<00:34:50.040> Bounty 00:34:50.450 --> 00:34:50.460 align:start position:0% Target to see if it has a bug Bounty 00:34:50.460 --> 00:34:52.190 align:start position:0% Target to see if it has a bug Bounty program<00:34:50.580> so<00:34:51.000> if<00:34:51.179> you<00:34:51.300> have<00:34:51.419> any<00:34:51.599> comments<00:34:51.960> or 00:34:52.190 --> 00:34:52.200 align:start position:0% program so if you have any comments or 00:34:52.200 --> 00:34:53.629 align:start position:0% program so if you have any comments or questions<00:34:52.440> please<00:34:52.800> let<00:34:52.980> me<00:34:53.099> know<00:34:53.159> down<00:34:53.460> below 00:34:53.629 --> 00:34:53.639 align:start position:0% questions please let me know down below 00:34:53.639 --> 00:34:55.609 align:start position:0% questions please let me know down below and<00:34:54.000> I'll<00:34:54.179> try<00:34:54.300> to<00:34:54.419> get<00:34:54.540> to<00:34:54.659> those<00:34:54.839> as<00:34:55.320> soon<00:34:55.500> as 00:34:55.609 --> 00:34:55.619 align:start position:0% and I'll try to get to those as soon as 00:34:55.619 --> 00:34:57.410 align:start position:0% and I'll try to get to those as soon as I<00:34:55.740> can<00:34:55.859> thanks<00:34:56.220> for<00:34:56.399> watching<00:34:56.700> we<00:34:57.060> are<00:34:57.240> going 00:34:57.410 --> 00:34:57.420 align:start position:0% I can thanks for watching we are going 00:34:57.420 --> 00:35:00.230 align:start position:0% I can thanks for watching we are going to<00:34:57.599> be<00:34:57.900> covering<00:34:58.260> how<00:34:58.560> to<00:34:58.680> take<00:34:59.040> notes<00:34:59.460> for<00:34:59.760> the 00:35:00.230 --> 00:35:00.240 align:start position:0% to be covering how to take notes for the 00:35:00.240 --> 00:35:02.150 align:start position:0% to be covering how to take notes for the world<00:35:00.420> of<00:35:00.660> bug<00:35:00.780> bounty<00:35:01.260> hunting<00:35:01.500> or<00:35:01.680> maybe<00:35:01.859> you 00:35:02.150 --> 00:35:02.160 align:start position:0% world of bug bounty hunting or maybe you 00:35:02.160 --> 00:35:03.530 align:start position:0% world of bug bounty hunting or maybe you are<00:35:02.280> wanting<00:35:02.580> to<00:35:02.640> become<00:35:02.880> a<00:35:03.060> penetration 00:35:03.530 --> 00:35:03.540 align:start position:0% are wanting to become a penetration 00:35:03.540 --> 00:35:05.210 align:start position:0% are wanting to become a penetration tester<00:35:03.900> note<00:35:04.140> taking<00:35:04.380> is<00:35:04.619> going<00:35:04.740> to<00:35:04.859> be<00:35:04.920> really 00:35:05.210 --> 00:35:05.220 align:start position:0% tester note taking is going to be really 00:35:05.220 --> 00:35:07.250 align:start position:0% tester note taking is going to be really important<00:35:05.640> to<00:35:05.760> you<00:35:05.880> and<00:35:06.240> your<00:35:06.780> method<00:35:07.080> of 00:35:07.250 --> 00:35:07.260 align:start position:0% important to you and your method of 00:35:07.260 --> 00:35:08.870 align:start position:0% important to you and your method of note-taking<00:35:07.680> and<00:35:08.040> actually<00:35:08.220> being<00:35:08.520> able<00:35:08.760> to 00:35:08.870 --> 00:35:08.880 align:start position:0% note-taking and actually being able to 00:35:08.880 --> 00:35:10.849 align:start position:0% note-taking and actually being able to go<00:35:09.180> back<00:35:09.359> and<00:35:09.599> overview<00:35:09.960> what<00:35:10.500> you<00:35:10.680> have 00:35:10.849 --> 00:35:10.859 align:start position:0% go back and overview what you have 00:35:10.859 --> 00:35:12.770 align:start position:0% go back and overview what you have already<00:35:11.160> done<00:35:11.820> and<00:35:12.180> gone<00:35:12.420> through<00:35:12.660> your 00:35:12.770 --> 00:35:12.780 align:start position:0% already done and gone through your 00:35:12.780 --> 00:35:13.730 align:start position:0% already done and gone through your checklist<00:35:13.079> is<00:35:13.320> going<00:35:13.440> to<00:35:13.500> be<00:35:13.560> really 00:35:13.730 --> 00:35:13.740 align:start position:0% checklist is going to be really 00:35:13.740 --> 00:35:15.050 align:start position:0% checklist is going to be really important<00:35:14.040> so<00:35:14.280> in<00:35:14.400> this<00:35:14.579> video<00:35:14.640> I'm<00:35:14.880> going<00:35:15.000> to 00:35:15.050 --> 00:35:15.060 align:start position:0% important so in this video I'm going to 00:35:15.060 --> 00:35:16.310 align:start position:0% important so in this video I'm going to show<00:35:15.180> you<00:35:15.240> how<00:35:15.420> I<00:35:15.599> take<00:35:15.720> notes<00:35:16.079> and<00:35:16.200> we're 00:35:16.310 --> 00:35:16.320 align:start position:0% show you how I take notes and we're 00:35:16.320 --> 00:35:18.290 align:start position:0% show you how I take notes and we're going<00:35:16.440> to<00:35:16.500> use<00:35:16.680> cherry<00:35:17.040> tree<00:35:17.280> within<00:35:17.820> Linux 00:35:18.290 --> 00:35:18.300 align:start position:0% going to use cherry tree within Linux 00:35:18.300 --> 00:35:19.790 align:start position:0% going to use cherry tree within Linux because<00:35:18.540> everybody's<00:35:19.140> going<00:35:19.320> to<00:35:19.440> have<00:35:19.500> access 00:35:19.790 --> 00:35:19.800 align:start position:0% because everybody's going to have access 00:35:19.800 --> 00:35:22.670 align:start position:0% because everybody's going to have access to<00:35:20.339> this<00:35:20.520> I<00:35:20.940> personally<00:35:21.420> use<00:35:21.960> OneNote<00:35:22.500> but 00:35:22.670 --> 00:35:22.680 align:start position:0% to this I personally use OneNote but 00:35:22.680 --> 00:35:23.870 align:start position:0% to this I personally use OneNote but it's<00:35:22.800> going<00:35:22.980> to<00:35:23.040> be<00:35:23.099> really<00:35:23.280> similar<00:35:23.579> to<00:35:23.760> what 00:35:23.870 --> 00:35:23.880 align:start position:0% it's going to be really similar to what 00:35:23.880 --> 00:35:25.609 align:start position:0% it's going to be really similar to what I'm<00:35:24.000> going<00:35:24.119> to<00:35:24.180> show<00:35:24.300> you<00:35:24.420> in<00:35:24.720> this<00:35:24.900> video<00:35:25.260> some 00:35:25.609 --> 00:35:25.619 align:start position:0% I'm going to show you in this video some 00:35:25.619 --> 00:35:27.349 align:start position:0% I'm going to show you in this video some of<00:35:25.740> the<00:35:25.859> benefits<00:35:26.280> of<00:35:26.579> taking<00:35:26.940> really<00:35:27.240> good 00:35:27.349 --> 00:35:27.359 align:start position:0% of the benefits of taking really good 00:35:27.359 --> 00:35:29.630 align:start position:0% of the benefits of taking really good notes<00:35:27.720> is<00:35:27.900> going<00:35:28.200> to<00:35:28.320> be<00:35:28.740> having<00:35:29.040> organized 00:35:29.630 --> 00:35:29.640 align:start position:0% notes is going to be having organized 00:35:29.640 --> 00:35:31.370 align:start position:0% notes is going to be having organized thoughts<00:35:29.940> and<00:35:30.060> being<00:35:30.180> able<00:35:30.300> to<00:35:30.480> write<00:35:31.140> a 00:35:31.370 --> 00:35:31.380 align:start position:0% thoughts and being able to write a 00:35:31.380 --> 00:35:33.170 align:start position:0% thoughts and being able to write a really<00:35:31.560> simple<00:35:31.800> proof<00:35:32.339> of<00:35:32.400> concept<00:35:32.760> you'll<00:35:33.060> be 00:35:33.170 --> 00:35:33.180 align:start position:0% really simple proof of concept you'll be 00:35:33.180 --> 00:35:34.670 align:start position:0% really simple proof of concept you'll be able<00:35:33.240> to<00:35:33.359> have<00:35:33.540> a<00:35:33.720> screenshots<00:35:34.140> and<00:35:34.380> be<00:35:34.560> able 00:35:34.670 --> 00:35:34.680 align:start position:0% able to have a screenshots and be able 00:35:34.680 --> 00:35:37.069 align:start position:0% able to have a screenshots and be able to<00:35:34.800> see<00:35:35.220> what<00:35:35.460> you<00:35:35.640> have<00:35:35.820> previously<00:35:36.480> done<00:35:36.720> and 00:35:37.069 --> 00:35:37.079 align:start position:0% to see what you have previously done and 00:35:37.079 --> 00:35:38.569 align:start position:0% to see what you have previously done and you're<00:35:37.200> not<00:35:37.320> going<00:35:37.440> to<00:35:37.560> waste<00:35:37.920> a<00:35:38.099> lot<00:35:38.280> of<00:35:38.460> time 00:35:38.569 --> 00:35:38.579 align:start position:0% you're not going to waste a lot of time 00:35:38.579 --> 00:35:40.550 align:start position:0% you're not going to waste a lot of time going<00:35:39.000> back<00:35:39.240> to<00:35:39.480> subdomains<00:35:40.260> that<00:35:40.380> you've 00:35:40.550 --> 00:35:40.560 align:start position:0% going back to subdomains that you've 00:35:40.560 --> 00:35:42.050 align:start position:0% going back to subdomains that you've already<00:35:40.680> enumerated<00:35:41.220> and<00:35:41.460> looked<00:35:41.760> at<00:35:41.820> because 00:35:42.050 --> 00:35:42.060 align:start position:0% already enumerated and looked at because 00:35:42.060 --> 00:35:43.670 align:start position:0% already enumerated and looked at because you<00:35:42.300> already<00:35:42.480> have<00:35:42.720> all<00:35:42.960> of<00:35:43.079> your<00:35:43.200> notes<00:35:43.500> there 00:35:43.670 --> 00:35:43.680 align:start position:0% you already have all of your notes there 00:35:43.680 --> 00:35:44.750 align:start position:0% you already have all of your notes there for<00:35:43.920> you<00:35:44.040> and<00:35:44.160> know<00:35:44.339> that<00:35:44.460> you've<00:35:44.640> already 00:35:44.750 --> 00:35:44.760 align:start position:0% for you and know that you've already 00:35:44.760 --> 00:35:46.670 align:start position:0% for you and know that you've already looked<00:35:45.000> at<00:35:45.119> it<00:35:45.240> and<00:35:45.540> if<00:35:45.780> a<00:35:45.960> new<00:35:46.140> vulnerability 00:35:46.670 --> 00:35:46.680 align:start position:0% looked at it and if a new vulnerability 00:35:46.680 --> 00:35:48.710 align:start position:0% looked at it and if a new vulnerability comes<00:35:47.099> out<00:35:47.160> you<00:35:47.460> can<00:35:47.520> go<00:35:47.760> and<00:35:48.060> see<00:35:48.300> when<00:35:48.540> the 00:35:48.710 --> 00:35:48.720 align:start position:0% comes out you can go and see when the 00:35:48.720 --> 00:35:51.290 align:start position:0% comes out you can go and see when the last<00:35:48.900> time<00:35:49.079> you<00:35:49.500> enumerated<00:35:50.160> looked<00:35:50.820> at<00:35:50.940> this 00:35:51.290 --> 00:35:51.300 align:start position:0% last time you enumerated looked at this 00:35:51.300 --> 00:35:53.810 align:start position:0% last time you enumerated looked at this specific<00:35:51.720> subdomain<00:35:52.320> and<00:35:52.800> know<00:35:52.980> if<00:35:53.280> the<00:35:53.579> new 00:35:53.810 --> 00:35:53.820 align:start position:0% specific subdomain and know if the new 00:35:53.820 --> 00:35:57.230 align:start position:0% specific subdomain and know if the new cve<00:35:54.240> is<00:35:54.780> going<00:35:54.960> to<00:35:55.079> be<00:35:55.440> applicable<00:35:55.920> to<00:35:56.700> this 00:35:57.230 --> 00:35:57.240 align:start position:0% cve is going to be applicable to this 00:35:57.240 --> 00:35:58.970 align:start position:0% cve is going to be applicable to this specific<00:35:57.660> domain<00:35:58.200> and<00:35:58.440> the<00:35:58.619> software<00:35:58.859> that's 00:35:58.970 --> 00:35:58.980 align:start position:0% specific domain and the software that's 00:35:58.980 --> 00:36:00.290 align:start position:0% specific domain and the software that's running<00:35:59.220> on<00:35:59.460> it<00:35:59.520> so<00:35:59.700> with<00:35:59.820> that<00:36:00.000> let's<00:36:00.119> go 00:36:00.290 --> 00:36:00.300 align:start position:0% running on it so with that let's go 00:36:00.300 --> 00:36:02.630 align:start position:0% running on it so with that let's go ahead<00:36:00.480> and<00:36:00.780> jump<00:36:01.079> into<00:36:01.260> it<00:36:01.500> so<00:36:01.680> here<00:36:01.920> we<00:36:02.099> are<00:36:02.220> on 00:36:02.630 --> 00:36:02.640 align:start position:0% ahead and jump into it so here we are on 00:36:02.640 --> 00:36:05.390 align:start position:0% ahead and jump into it so here we are on our<00:36:02.940> Kali<00:36:03.359> Linux<00:36:03.780> machine<00:36:04.020> we<00:36:04.500> can<00:36:04.740> come<00:36:04.980> up<00:36:05.160> to 00:36:05.390 --> 00:36:05.400 align:start position:0% our Kali Linux machine we can come up to 00:36:05.400 --> 00:36:08.569 align:start position:0% our Kali Linux machine we can come up to the<00:36:06.000> little<00:36:06.240> drop<00:36:06.960> down<00:36:07.200> menu<00:36:07.800> and<00:36:08.280> we<00:36:08.460> can 00:36:08.569 --> 00:36:08.579 align:start position:0% the little drop down menu and we can 00:36:08.579 --> 00:36:10.670 align:start position:0% the little drop down menu and we can type<00:36:08.760> in<00:36:09.000> cherry<00:36:09.480> tree<00:36:09.720> and<00:36:10.200> it<00:36:10.320> will<00:36:10.500> be 00:36:10.670 --> 00:36:10.680 align:start position:0% type in cherry tree and it will be 00:36:10.680 --> 00:36:12.050 align:start position:0% type in cherry tree and it will be automatically<00:36:11.280> installed<00:36:11.760> if<00:36:11.940> you're 00:36:12.050 --> 00:36:12.060 align:start position:0% automatically installed if you're 00:36:12.060 --> 00:36:14.690 align:start position:0% automatically installed if you're running<00:36:12.300> at<00:36:12.540> Kali<00:36:12.839> Linux<00:36:13.200> so<00:36:13.740> using<00:36:14.339> cherry 00:36:14.690 --> 00:36:14.700 align:start position:0% running at Kali Linux so using cherry 00:36:14.700 --> 00:36:16.790 align:start position:0% running at Kali Linux so using cherry tree<00:36:14.940> is<00:36:15.240> going<00:36:15.420> to<00:36:15.540> be<00:36:15.599> really<00:36:16.140> pretty<00:36:16.500> simple 00:36:16.790 --> 00:36:16.800 align:start position:0% tree is going to be really pretty simple 00:36:16.800 --> 00:36:18.170 align:start position:0% tree is going to be really pretty simple the<00:36:17.220> first<00:36:17.280> thing<00:36:17.520> you're<00:36:17.760> going<00:36:17.940> to<00:36:18.000> want<00:36:18.119> to 00:36:18.170 --> 00:36:18.180 align:start position:0% the first thing you're going to want to 00:36:18.180 --> 00:36:20.150 align:start position:0% the first thing you're going to want to do<00:36:18.300> in<00:36:18.599> your<00:36:18.780> notes<00:36:19.079> is<00:36:19.500> you're<00:36:19.680> going<00:36:19.859> to<00:36:19.980> have 00:36:20.150 --> 00:36:20.160 align:start position:0% do in your notes is you're going to have 00:36:20.160 --> 00:36:22.010 align:start position:0% do in your notes is you're going to have the<00:36:20.700> main<00:36:20.940> domain<00:36:21.420> and<00:36:21.660> all<00:36:21.839> of<00:36:21.900> the 00:36:22.010 --> 00:36:22.020 align:start position:0% the main domain and all of the 00:36:22.020 --> 00:36:23.750 align:start position:0% the main domain and all of the information<00:36:22.200> that<00:36:22.560> you<00:36:22.740> found<00:36:22.920> on<00:36:23.280> it<00:36:23.400> so<00:36:23.579> you 00:36:23.750 --> 00:36:23.760 align:start position:0% information that you found on it so you 00:36:23.760 --> 00:36:26.630 align:start position:0% information that you found on it so you can<00:36:23.820> type<00:36:24.000> in<00:36:24.240> the<00:36:24.960> domain.com<00:36:25.800> and<00:36:26.400> this<00:36:26.520> is 00:36:26.630 --> 00:36:26.640 align:start position:0% can type in the domain.com and this is 00:36:26.640 --> 00:36:28.550 align:start position:0% can type in the domain.com and this is going<00:36:26.700> to<00:36:26.820> give<00:36:26.940> you<00:36:27.060> this<00:36:27.480> parent<00:36:27.720> node<00:36:28.200> right 00:36:28.550 --> 00:36:28.560 align:start position:0% going to give you this parent node right 00:36:28.560 --> 00:36:30.410 align:start position:0% going to give you this parent node right here<00:36:28.740> and<00:36:29.280> you<00:36:29.400> can<00:36:29.520> also<00:36:29.700> change<00:36:29.940> up<00:36:30.119> your 00:36:30.410 --> 00:36:30.420 align:start position:0% here and you can also change up your 00:36:30.420 --> 00:36:32.390 align:start position:0% here and you can also change up your note-taking<00:36:31.140> method<00:36:31.619> and<00:36:31.859> maybe<00:36:31.980> you<00:36:32.220> want<00:36:32.280> to 00:36:32.390 --> 00:36:32.400 align:start position:0% note-taking method and maybe you want to 00:36:32.400 --> 00:36:34.010 align:start position:0% note-taking method and maybe you want to have<00:36:32.520> the<00:36:32.700> main<00:36:32.820> domain<00:36:33.240> and<00:36:33.420> you<00:36:33.599> have<00:36:33.720> each 00:36:34.010 --> 00:36:34.020 align:start position:0% have the main domain and you have each 00:36:34.020 --> 00:36:36.650 align:start position:0% have the main domain and you have each subdomain<00:36:34.619> right<00:36:34.859> here<00:36:35.040> like<00:36:35.940> this<00:36:36.300> you<00:36:36.540> could 00:36:36.650 --> 00:36:36.660 align:start position:0% subdomain right here like this you could 00:36:36.660 --> 00:36:39.349 align:start position:0% subdomain right here like this you could have<00:36:36.960> a<00:36:37.320> subdomain<00:36:37.859> one<00:36:38.220> only<00:36:38.940> it<00:36:39.180> would 00:36:39.349 --> 00:36:39.359 align:start position:0% have a subdomain one only it would 00:36:39.359 --> 00:36:41.630 align:start position:0% have a subdomain one only it would actually<00:36:39.480> be<00:36:39.660> the<00:36:39.900> subdomain<00:36:40.380> name<00:36:40.740> right 00:36:41.630 --> 00:36:41.640 align:start position:0% actually be the subdomain name right 00:36:41.640 --> 00:36:42.950 align:start position:0% actually be the subdomain name right here<00:36:41.880> and<00:36:42.180> then<00:36:42.300> you'll<00:36:42.480> have<00:36:42.599> all<00:36:42.780> of<00:36:42.900> your 00:36:42.950 --> 00:36:42.960 align:start position:0% here and then you'll have all of your 00:36:42.960 --> 00:36:44.630 align:start position:0% here and then you'll have all of your nodes<00:36:43.140> from<00:36:43.380> that<00:36:43.500> subdomain<00:36:44.040> but<00:36:44.220> if<00:36:44.400> you<00:36:44.520> do 00:36:44.630 --> 00:36:44.640 align:start position:0% nodes from that subdomain but if you do 00:36:44.640 --> 00:36:47.030 align:start position:0% nodes from that subdomain but if you do this<00:36:44.820> there<00:36:45.240> are<00:36:45.420> some<00:36:45.900> programs<00:36:46.619> that<00:36:46.859> have 00:36:47.030 --> 00:36:47.040 align:start position:0% this there are some programs that have 00:36:47.040 --> 00:36:49.370 align:start position:0% this there are some programs that have like<00:36:47.280> 800<00:36:47.940> subdomains<00:36:48.720> and<00:36:48.839> this<00:36:49.020> would<00:36:49.200> take 00:36:49.370 --> 00:36:49.380 align:start position:0% like 800 subdomains and this would take 00:36:49.380 --> 00:36:51.530 align:start position:0% like 800 subdomains and this would take forever<00:36:50.160> to<00:36:50.460> do<00:36:50.579> but<00:36:50.760> you<00:36:50.940> can<00:36:51.060> come<00:36:51.240> in<00:36:51.420> here 00:36:51.530 --> 00:36:51.540 align:start position:0% forever to do but you can come in here 00:36:51.540 --> 00:36:53.690 align:start position:0% forever to do but you can come in here and<00:36:51.780> do<00:36:51.900> every<00:36:52.200> single<00:36:52.560> subdomain<00:36:53.220> like<00:36:53.579> this 00:36:53.690 --> 00:36:53.700 align:start position:0% and do every single subdomain like this 00:36:53.700 --> 00:36:57.069 align:start position:0% and do every single subdomain like this and<00:36:53.940> so<00:36:54.060> it'd<00:36:54.300> be<00:36:54.420> if<00:36:55.380> we<00:36:55.619> could<00:36:55.740> just<00:36:55.859> say<00:36:56.099> a 00:36:57.069 --> 00:36:57.079 align:start position:0% and so it'd be if we could just say a 00:36:57.079 --> 00:36:59.510 align:start position:0% and so it'd be if we could just say a sub.domain.com<00:36:58.079> spelled<00:36:58.859> that<00:36:58.980> wrong<00:36:59.099> like 00:36:59.510 --> 00:36:59.520 align:start position:0% sub.domain.com spelled that wrong like 00:36:59.520 --> 00:37:01.250 align:start position:0% sub.domain.com spelled that wrong like this<00:36:59.760> and<00:37:00.300> then<00:37:00.420> you<00:37:00.540> would<00:37:00.720> have<00:37:00.839> all<00:37:01.020> of<00:37:01.140> your 00:37:01.250 --> 00:37:01.260 align:start position:0% this and then you would have all of your 00:37:01.260 --> 00:37:04.010 align:start position:0% this and then you would have all of your notes<00:37:01.619> within<00:37:02.220> this<00:37:02.880> specific<00:37:03.240> subdomain<00:37:03.839> so 00:37:04.010 --> 00:37:04.020 align:start position:0% notes within this specific subdomain so 00:37:04.020 --> 00:37:06.290 align:start position:0% notes within this specific subdomain so if<00:37:04.200> you<00:37:04.320> decided<00:37:04.680> to<00:37:04.859> go<00:37:05.220> this<00:37:05.400> way<00:37:05.579> one<00:37:06.119> of<00:37:06.240> the 00:37:06.290 --> 00:37:06.300 align:start position:0% if you decided to go this way one of the 00:37:06.300 --> 00:37:08.510 align:start position:0% if you decided to go this way one of the things<00:37:06.480> I<00:37:06.960> would<00:37:07.079> suggest<00:37:07.440> doing<00:37:07.740> right<00:37:08.339> out 00:37:08.510 --> 00:37:08.520 align:start position:0% things I would suggest doing right out 00:37:08.520 --> 00:37:10.370 align:start position:0% things I would suggest doing right out of<00:37:08.640> the<00:37:08.760> beginning<00:37:08.940> is<00:37:09.300> when<00:37:09.480> you<00:37:09.599> put<00:37:09.780> in<00:37:10.020> your 00:37:10.370 --> 00:37:10.380 align:start position:0% of the beginning is when you put in your 00:37:10.380 --> 00:37:13.370 align:start position:0% of the beginning is when you put in your first<00:37:10.859> sub<00:37:11.520> node<00:37:11.880> is<00:37:12.240> maybe<00:37:12.480> just<00:37:12.780> called<00:37:13.020> this 00:37:13.370 --> 00:37:13.380 align:start position:0% first sub node is maybe just called this 00:37:13.380 --> 00:37:15.410 align:start position:0% first sub node is maybe just called this the<00:37:13.980> software 00:37:15.410 --> 00:37:15.420 align:start position:0% the software 00:37:15.420 --> 00:37:17.990 align:start position:0% the software right<00:37:16.020> here<00:37:16.320> and<00:37:16.740> you<00:37:16.980> can<00:37:17.099> run<00:37:17.339> you<00:37:17.760> can<00:37:17.820> say 00:37:17.990 --> 00:37:18.000 align:start position:0% right here and you can run you can say 00:37:18.000 --> 00:37:20.690 align:start position:0% right here and you can run you can say that<00:37:18.180> it's<00:37:18.359> running<00:37:18.540> some<00:37:19.020> kind<00:37:19.260> of<00:37:19.440> CMS<00:37:20.099> maybe 00:37:20.690 --> 00:37:20.700 align:start position:0% that it's running some kind of CMS maybe 00:37:20.700 --> 00:37:22.910 align:start position:0% that it's running some kind of CMS maybe it's<00:37:21.000> running<00:37:21.300> WordPress<00:37:22.260> and<00:37:22.680> then<00:37:22.740> you 00:37:22.910 --> 00:37:22.920 align:start position:0% it's running WordPress and then you 00:37:22.920 --> 00:37:26.470 align:start position:0% it's running WordPress and then you would<00:37:23.099> have<00:37:23.220> the<00:37:23.400> version<00:37:23.839> of 00:37:26.470 --> 00:37:26.480 align:start position:0% would have the version of 00:37:26.480 --> 00:37:29.930 align:start position:0% would have the version of 4.2.4<00:37:27.480> and<00:37:28.079> then<00:37:28.260> you<00:37:28.859> can<00:37:29.040> know<00:37:29.460> that<00:37:29.700> this<00:37:29.820> is 00:37:29.930 --> 00:37:29.940 align:start position:0% 4.2.4 and then you can know that this is 00:37:29.940 --> 00:37:31.550 align:start position:0% 4.2.4 and then you can know that this is what's<00:37:30.060> running<00:37:30.300> Subway<00:37:30.540> in<00:37:30.960> the<00:37:31.079> future<00:37:31.200> if 00:37:31.550 --> 00:37:31.560 align:start position:0% what's running Subway in the future if 00:37:31.560 --> 00:37:34.010 align:start position:0% what's running Subway in the future if there's<00:37:31.740> any<00:37:32.040> kind<00:37:32.280> of<00:37:32.460> cve<00:37:33.240> that<00:37:33.660> comes<00:37:33.900> out 00:37:34.010 --> 00:37:34.020 align:start position:0% there's any kind of cve that comes out 00:37:34.020 --> 00:37:35.690 align:start position:0% there's any kind of cve that comes out for<00:37:34.320> the<00:37:34.619> WordPress<00:37:34.980> version<00:37:35.280> that's<00:37:35.520> running 00:37:35.690 --> 00:37:35.700 align:start position:0% for the WordPress version that's running 00:37:35.700 --> 00:37:37.849 align:start position:0% for the WordPress version that's running you<00:37:36.060> can<00:37:36.119> come<00:37:36.240> back<00:37:36.420> to<00:37:36.660> this<00:37:36.960> subdomain<00:37:37.500> and 00:37:37.849 --> 00:37:37.859 align:start position:0% you can come back to this subdomain and 00:37:37.859 --> 00:37:39.770 align:start position:0% you can come back to this subdomain and see<00:37:37.980> if<00:37:38.099> it's<00:37:38.220> vulnerable<00:37:38.579> to<00:37:38.880> that<00:37:39.119> new<00:37:39.300> cve 00:37:39.770 --> 00:37:39.780 align:start position:0% see if it's vulnerable to that new cve 00:37:39.780 --> 00:37:41.690 align:start position:0% see if it's vulnerable to that new cve another<00:37:40.560> reason<00:37:40.920> you're<00:37:41.160> going<00:37:41.339> to<00:37:41.460> want<00:37:41.579> to 00:37:41.690 --> 00:37:41.700 align:start position:0% another reason you're going to want to 00:37:41.700 --> 00:37:44.810 align:start position:0% another reason you're going to want to have<00:37:42.180> some<00:37:42.480> kind<00:37:42.660> of<00:37:42.839> list<00:37:43.200> of<00:37:43.680> the<00:37:44.040> subdomains 00:37:44.810 --> 00:37:44.820 align:start position:0% have some kind of list of the subdomains 00:37:44.820 --> 00:37:46.970 align:start position:0% have some kind of list of the subdomains so<00:37:45.240> let's<00:37:45.359> go<00:37:45.540> ahead<00:37:45.720> and<00:37:46.140> delete<00:37:46.500> this<00:37:46.859> one 00:37:46.970 --> 00:37:46.980 align:start position:0% so let's go ahead and delete this one 00:37:46.980 --> 00:37:48.230 align:start position:0% so let's go ahead and delete this one right<00:37:47.160> here<00:37:47.280> so<00:37:47.520> it<00:37:47.640> looks<00:37:47.880> a<00:37:48.000> little<00:37:48.060> better 00:37:48.230 --> 00:37:48.240 align:start position:0% right here so it looks a little better 00:37:48.240 --> 00:37:50.690 align:start position:0% right here so it looks a little better if<00:37:48.839> you<00:37:48.960> decided<00:37:49.380> to<00:37:49.619> run<00:37:50.040> a<00:37:50.400> bunch<00:37:50.520> of 00:37:50.690 --> 00:37:50.700 align:start position:0% if you decided to run a bunch of 00:37:50.700 --> 00:37:53.450 align:start position:0% if you decided to run a bunch of subdomains<00:37:51.480> in<00:37:51.599> here<00:37:51.780> so<00:37:52.079> we<00:37:52.260> can<00:37:52.380> type<00:37:52.619> in<00:37:52.920> sub 00:37:53.450 --> 00:37:53.460 align:start position:0% subdomains in here so we can type in sub 00:37:53.460 --> 00:37:58.010 align:start position:0% subdomains in here so we can type in sub 1<00:37:53.700> dot<00:37:54.300> domain<00:37:54.780> Dot<00:37:56.040> com<00:37:56.760> and<00:37:57.480> in<00:37:57.599> here<00:37:57.839> you 00:37:58.010 --> 00:37:58.020 align:start position:0% 1 dot domain Dot com and in here you 00:37:58.020 --> 00:38:00.050 align:start position:0% 1 dot domain Dot com and in here you have<00:37:58.260> a<00:37:58.500> list<00:37:58.680> of<00:37:58.859> all<00:37:59.099> of<00:37:59.220> your<00:37:59.400> sub<00:37:59.520> domains 00:38:00.050 --> 00:38:00.060 align:start position:0% have a list of all of your sub domains 00:38:00.060 --> 00:38:02.890 align:start position:0% have a list of all of your sub domains you<00:38:00.599> can<00:38:00.720> have<00:38:00.900> actually<00:38:01.520> subdomains<00:38:02.520> in<00:38:02.700> here 00:38:02.890 --> 00:38:02.900 align:start position:0% you can have actually subdomains in here 00:38:02.900 --> 00:38:04.970 align:start position:0% you can have actually subdomains in here within<00:38:03.900> this<00:38:04.260> specific<00:38:04.500> thing<00:38:04.740> that<00:38:04.859> you're 00:38:04.970 --> 00:38:04.980 align:start position:0% within this specific thing that you're 00:38:04.980 --> 00:38:06.290 align:start position:0% within this specific thing that you're looking<00:38:05.099> at<00:38:05.280> so<00:38:05.400> in<00:38:05.579> here<00:38:05.700> we<00:38:05.940> could<00:38:06.060> say 00:38:06.290 --> 00:38:06.300 align:start position:0% looking at so in here we could say 00:38:06.300 --> 00:38:08.810 align:start position:0% looking at so in here we could say software<00:38:07.079> and<00:38:07.680> you<00:38:07.859> can<00:38:07.980> see<00:38:08.160> how<00:38:08.400> this<00:38:08.640> is 00:38:08.810 --> 00:38:08.820 align:start position:0% software and you can see how this is 00:38:08.820 --> 00:38:11.930 align:start position:0% software and you can see how this is going<00:38:09.000> to<00:38:09.119> organize<00:38:09.859> our<00:38:10.859> research<00:38:11.460> for<00:38:11.700> us 00:38:11.930 --> 00:38:11.940 align:start position:0% going to organize our research for us 00:38:11.940 --> 00:38:13.790 align:start position:0% going to organize our research for us and<00:38:12.180> inside<00:38:12.359> of<00:38:12.780> the<00:38:12.900> software<00:38:13.200> in<00:38:13.440> here<00:38:13.619> you 00:38:13.790 --> 00:38:13.800 align:start position:0% and inside of the software in here you 00:38:13.800 --> 00:38:17.150 align:start position:0% and inside of the software in here you would<00:38:13.980> put<00:38:14.160> your<00:38:14.480> WordPress<00:38:15.480> and<00:38:16.260> then<00:38:16.440> the 00:38:17.150 --> 00:38:17.160 align:start position:0% would put your WordPress and then the 00:38:17.160 --> 00:38:19.670 align:start position:0% would put your WordPress and then the version<00:38:17.700> that<00:38:18.240> it<00:38:18.420> is<00:38:18.599> running<00:38:19.020> so<00:38:19.440> these<00:38:19.619> are 00:38:19.670 --> 00:38:19.680 align:start position:0% version that it is running so these are 00:38:19.680 --> 00:38:20.930 align:start position:0% version that it is running so these are a<00:38:19.800> couple<00:38:19.920> different<00:38:20.099> ways<00:38:20.460> to<00:38:20.640> kind<00:38:20.820> of 00:38:20.930 --> 00:38:20.940 align:start position:0% a couple different ways to kind of 00:38:20.940 --> 00:38:23.390 align:start position:0% a couple different ways to kind of organize<00:38:21.359> your<00:38:21.900> notes<00:38:22.320> and<00:38:22.619> another<00:38:22.740> way<00:38:23.040> to 00:38:23.390 --> 00:38:23.400 align:start position:0% organize your notes and another way to 00:38:23.400 --> 00:38:25.490 align:start position:0% organize your notes and another way to save<00:38:23.760> time<00:38:24.060> instead<00:38:24.599> of<00:38:24.660> actually<00:38:24.960> going 00:38:25.490 --> 00:38:25.500 align:start position:0% save time instead of actually going 00:38:25.500 --> 00:38:27.589 align:start position:0% save time instead of actually going through<00:38:25.680> and<00:38:25.920> typing<00:38:26.280> all<00:38:26.400> this<00:38:26.640> out<00:38:26.820> is<00:38:27.300> on 00:38:27.589 --> 00:38:27.599 align:start position:0% through and typing all this out is on 00:38:27.599 --> 00:38:29.270 align:start position:0% through and typing all this out is on this<00:38:27.720> box<00:38:27.900> I<00:38:28.140> already<00:38:28.260> have<00:38:28.440> lapalyzer 00:38:29.270 --> 00:38:29.280 align:start position:0% this box I already have lapalyzer 00:38:29.280 --> 00:38:31.190 align:start position:0% this box I already have lapalyzer installed<00:38:29.820> so<00:38:30.060> I<00:38:30.180> could<00:38:30.300> just<00:38:30.480> come<00:38:30.660> we<00:38:31.020> can 00:38:31.190 --> 00:38:31.200 align:start position:0% installed so I could just come we can 00:38:31.200 --> 00:38:33.170 align:start position:0% installed so I could just come we can come<00:38:31.320> to<00:38:31.500> the<00:38:31.680> browser<00:38:32.099> and<00:38:32.579> type<00:38:32.820> in<00:38:33.000> like 00:38:33.170 --> 00:38:33.180 align:start position:0% come to the browser and type in like 00:38:33.180 --> 00:38:35.750 align:start position:0% come to the browser and type in like google.com<00:38:33.720> and<00:38:34.200> open<00:38:34.380> up<00:38:34.500> wapalyzer<00:38:35.220> to<00:38:35.579> see 00:38:35.750 --> 00:38:35.760 align:start position:0% google.com and open up wapalyzer to see 00:38:35.760 --> 00:38:38.030 align:start position:0% google.com and open up wapalyzer to see what<00:38:36.000> information<00:38:36.240> is<00:38:36.900> there<00:38:37.260> and<00:38:37.680> now<00:38:37.800> we 00:38:38.030 --> 00:38:38.040 align:start position:0% what information is there and now we 00:38:38.040 --> 00:38:40.250 align:start position:0% what information is there and now we could<00:38:38.160> open<00:38:38.400> this<00:38:38.700> up<00:38:39.000> right<00:38:39.420> here<00:38:39.660> and<00:38:40.020> I 00:38:40.250 --> 00:38:40.260 align:start position:0% could open this up right here and I 00:38:40.260 --> 00:38:42.829 align:start position:0% could open this up right here and I could<00:38:40.380> just<00:38:40.619> screenshot<00:38:41.280> this<00:38:41.640> and<00:38:42.240> pull<00:38:42.540> that 00:38:42.829 --> 00:38:42.839 align:start position:0% could just screenshot this and pull that 00:38:42.839 --> 00:38:46.550 align:start position:0% could just screenshot this and pull that screenshot<00:38:43.320> over<00:38:43.740> to<00:38:44.579> my<00:38:45.119> Cali<00:38:45.540> machine<00:38:45.720> and 00:38:46.550 --> 00:38:46.560 align:start position:0% screenshot over to my Cali machine and 00:38:46.560 --> 00:38:49.010 align:start position:0% screenshot over to my Cali machine and then<00:38:46.680> I<00:38:47.099> can<00:38:47.220> put<00:38:47.640> it<00:38:47.760> into<00:38:48.000> a<00:38:48.359> cherry<00:38:48.540> tree<00:38:48.780> so 00:38:49.010 --> 00:38:49.020 align:start position:0% then I can put it into a cherry tree so 00:38:49.020 --> 00:38:51.290 align:start position:0% then I can put it into a cherry tree so I<00:38:49.140> could<00:38:49.260> grab<00:38:49.500> this<00:38:49.740> and<00:38:50.099> pull<00:38:50.339> it<00:38:50.460> over<00:38:50.640> and 00:38:51.290 --> 00:38:51.300 align:start position:0% I could grab this and pull it over and 00:38:51.300 --> 00:38:53.150 align:start position:0% I could grab this and pull it over and put<00:38:51.599> it<00:38:51.720> into<00:38:51.960> a<00:38:52.200> cherry<00:38:52.440> tree<00:38:52.619> I<00:38:53.040> actually 00:38:53.150 --> 00:38:53.160 align:start position:0% put it into a cherry tree I actually 00:38:53.160 --> 00:38:55.849 align:start position:0% put it into a cherry tree I actually don't<00:38:53.520> have<00:38:53.820> this<00:38:54.420> specific<00:38:54.960> Cali<00:38:55.440> box<00:38:55.560> set<00:38:55.740> up 00:38:55.849 --> 00:38:55.859 align:start position:0% don't have this specific Cali box set up 00:38:55.859 --> 00:38:57.530 align:start position:0% don't have this specific Cali box set up to<00:38:55.980> do<00:38:56.400> that<00:38:56.579> so<00:38:56.760> it's<00:38:56.940> not<00:38:57.119> going<00:38:57.240> to<00:38:57.240> work<00:38:57.420> for 00:38:57.530 --> 00:38:57.540 align:start position:0% to do that so it's not going to work for 00:38:57.540 --> 00:39:00.650 align:start position:0% to do that so it's not going to work for this<00:38:57.660> one<00:38:57.839> but<00:38:58.380> on<00:38:58.680> my<00:38:58.920> actual<00:38:59.339> personal<00:39:00.000> Kali 00:39:00.650 --> 00:39:00.660 align:start position:0% this one but on my actual personal Kali 00:39:00.660 --> 00:39:03.230 align:start position:0% this one but on my actual personal Kali Linux<00:39:01.020> machine<00:39:01.260> that<00:39:01.560> I<00:39:01.740> use<00:39:01.859> I<00:39:02.579> can<00:39:02.760> just<00:39:02.940> pull 00:39:03.230 --> 00:39:03.240 align:start position:0% Linux machine that I use I can just pull 00:39:03.240 --> 00:39:05.510 align:start position:0% Linux machine that I use I can just pull screenshots<00:39:03.839> back<00:39:04.200> and<00:39:04.380> forth<00:39:04.560> over<00:39:04.859> to<00:39:05.220> my 00:39:05.510 --> 00:39:05.520 align:start position:0% screenshots back and forth over to my 00:39:05.520 --> 00:39:07.069 align:start position:0% screenshots back and forth over to my Cali<00:39:05.880> machine<00:39:06.060> and<00:39:06.359> save<00:39:06.480> them<00:39:06.720> inside<00:39:06.839> of 00:39:07.069 --> 00:39:07.079 align:start position:0% Cali machine and save them inside of 00:39:07.079 --> 00:39:09.290 align:start position:0% Cali machine and save them inside of cherry<00:39:07.260> tree<00:39:07.440> but<00:39:07.980> I<00:39:08.160> use<00:39:08.280> OneNote<00:39:08.760> so<00:39:09.000> I<00:39:09.180> don't 00:39:09.290 --> 00:39:09.300 align:start position:0% cherry tree but I use OneNote so I don't 00:39:09.300 --> 00:39:10.970 align:start position:0% cherry tree but I use OneNote so I don't really<00:39:09.420> have<00:39:09.660> to<00:39:09.839> worry<00:39:10.200> about<00:39:10.380> that<00:39:10.619> too<00:39:10.800> much 00:39:10.970 --> 00:39:10.980 align:start position:0% really have to worry about that too much 00:39:10.980 --> 00:39:12.950 align:start position:0% really have to worry about that too much so<00:39:11.640> screenshotting<00:39:12.300> and<00:39:12.540> adding<00:39:12.780> information 00:39:12.950 --> 00:39:12.960 align:start position:0% so screenshotting and adding information 00:39:12.960 --> 00:39:15.010 align:start position:0% so screenshotting and adding information in<00:39:13.440> here<00:39:13.619> is<00:39:13.800> going<00:39:13.980> to<00:39:14.099> be<00:39:14.220> helpful<00:39:14.520> as<00:39:14.820> well 00:39:15.010 --> 00:39:15.020 align:start position:0% in here is going to be helpful as well 00:39:15.020 --> 00:39:17.690 align:start position:0% in here is going to be helpful as well if<00:39:16.020> you<00:39:16.200> have<00:39:16.380> that<00:39:16.560> capability<00:39:16.980> and<00:39:17.400> one<00:39:17.579> of 00:39:17.690 --> 00:39:17.700 align:start position:0% if you have that capability and one of 00:39:17.700 --> 00:39:19.670 align:start position:0% if you have that capability and one of the things<00:39:17.820> I<00:39:17.940> like<00:39:18.060> to<00:39:18.180> do<00:39:18.359> is<00:39:18.780> at<00:39:19.200> the<00:39:19.320> end<00:39:19.440> of 00:39:19.670 --> 00:39:19.680 align:start position:0% the things I like to do is at the end of 00:39:19.680 --> 00:39:23.270 align:start position:0% the things I like to do is at the end of a<00:39:19.920> Recon<00:39:20.220> session<00:39:20.520> is<00:39:20.880> make<00:39:21.180> a<00:39:21.540> node<00:39:21.900> like<00:39:22.859> this 00:39:23.270 --> 00:39:23.280 align:start position:0% a Recon session is make a node like this 00:39:23.280 --> 00:39:26.510 align:start position:0% a Recon session is make a node like this and<00:39:23.640> we'll<00:39:23.760> just<00:39:24.000> call<00:39:24.180> it<00:39:24.420> a<00:39:24.839> Recon<00:39:25.500> node<00:39:26.280> and 00:39:26.510 --> 00:39:26.520 align:start position:0% and we'll just call it a Recon node and 00:39:26.520 --> 00:39:28.130 align:start position:0% and we'll just call it a Recon node and then<00:39:26.640> in<00:39:26.820> here<00:39:26.940> I<00:39:27.119> write<00:39:27.300> down<00:39:27.480> all<00:39:27.780> the<00:39:27.900> tools 00:39:28.130 --> 00:39:28.140 align:start position:0% then in here I write down all the tools 00:39:28.140 --> 00:39:29.930 align:start position:0% then in here I write down all the tools I<00:39:28.320> ran<00:39:28.500> and<00:39:28.740> the<00:39:28.859> way<00:39:28.980> that<00:39:29.099> I<00:39:29.280> collected<00:39:29.700> all 00:39:29.930 --> 00:39:29.940 align:start position:0% I ran and the way that I collected all 00:39:29.940 --> 00:39:32.390 align:start position:0% I ran and the way that I collected all of<00:39:30.060> the<00:39:30.180> information<00:39:30.420> so<00:39:31.200> that<00:39:31.380> way<00:39:31.560> I<00:39:31.920> have<00:39:32.099> a 00:39:32.390 --> 00:39:32.400 align:start position:0% of the information so that way I have a 00:39:32.400 --> 00:39:33.829 align:start position:0% of the information so that way I have a clear<00:39:32.520> set<00:39:32.880> of<00:39:33.000> notes<00:39:33.240> and<00:39:33.359> that<00:39:33.480> way<00:39:33.660> if<00:39:33.780> I 00:39:33.829 --> 00:39:33.839 align:start position:0% clear set of notes and that way if I 00:39:33.839 --> 00:39:35.750 align:start position:0% clear set of notes and that way if I ever<00:39:33.960> come<00:39:34.140> back<00:39:34.320> to<00:39:34.560> this<00:39:34.800> specific<00:39:35.099> Target<00:39:35.339> I 00:39:35.750 --> 00:39:35.760 align:start position:0% ever come back to this specific Target I 00:39:35.760 --> 00:39:37.310 align:start position:0% ever come back to this specific Target I can<00:39:35.880> see<00:39:36.119> if<00:39:36.420> maybe<00:39:36.660> I've<00:39:36.960> missed<00:39:37.260> something 00:39:37.310 --> 00:39:37.320 align:start position:0% can see if maybe I've missed something 00:39:37.320 --> 00:39:39.290 align:start position:0% can see if maybe I've missed something or<00:39:37.680> maybe<00:39:37.800> I've<00:39:38.099> learned<00:39:38.400> some<00:39:38.640> kind<00:39:38.820> of<00:39:38.940> new 00:39:39.290 --> 00:39:39.300 align:start position:0% or maybe I've learned some kind of new 00:39:39.300 --> 00:39:41.390 align:start position:0% or maybe I've learned some kind of new Recon<00:39:40.020> technique<00:39:40.440> that<00:39:40.680> I<00:39:40.800> can<00:39:40.859> try<00:39:40.980> out<00:39:41.160> on 00:39:41.390 --> 00:39:41.400 align:start position:0% Recon technique that I can try out on 00:39:41.400 --> 00:39:43.250 align:start position:0% Recon technique that I can try out on this<00:39:41.520> specific<00:39:41.820> Target<00:39:42.060> and<00:39:42.660> I'll<00:39:42.780> know<00:39:42.960> what 00:39:43.250 --> 00:39:43.260 align:start position:0% this specific Target and I'll know what 00:39:43.260 --> 00:39:44.990 align:start position:0% this specific Target and I'll know what exactly<00:39:43.680> I<00:39:43.800> have<00:39:43.980> done<00:39:44.160> on<00:39:44.339> this<00:39:44.460> Target<00:39:44.640> and 00:39:44.990 --> 00:39:45.000 align:start position:0% exactly I have done on this Target and 00:39:45.000 --> 00:39:47.630 align:start position:0% exactly I have done on this Target and what<00:39:45.180> I<00:39:45.300> can<00:39:45.359> do<00:39:45.480> in<00:39:45.839> the<00:39:45.960> future<00:39:46.140> to<00:39:47.099> further 00:39:47.630 --> 00:39:47.640 align:start position:0% what I can do in the future to further 00:39:47.640 --> 00:39:49.970 align:start position:0% what I can do in the future to further analyze<00:39:48.359> the<00:39:48.599> information<00:39:48.780> on<00:39:49.380> my<00:39:49.560> specific 00:39:49.970 --> 00:39:49.980 align:start position:0% analyze the information on my specific 00:39:49.980 --> 00:39:52.370 align:start position:0% analyze the information on my specific Target<00:39:50.460> so<00:39:50.940> make<00:39:51.180> sure<00:39:51.300> to<00:39:51.540> write<00:39:51.839> down<00:39:52.079> your 00:39:52.370 --> 00:39:52.380 align:start position:0% Target so make sure to write down your 00:39:52.380 --> 00:39:54.170 align:start position:0% Target so make sure to write down your methodology<00:39:52.920> of<00:39:53.280> your<00:39:53.400> recon<00:39:53.760> and<00:39:54.060> attack 00:39:54.170 --> 00:39:54.180 align:start position:0% methodology of your recon and attack 00:39:54.180 --> 00:39:56.390 align:start position:0% methodology of your recon and attack because<00:39:54.599> it<00:39:54.900> may<00:39:55.020> change<00:39:55.260> in<00:39:55.500> the<00:39:55.619> future<00:39:55.859> and 00:39:56.390 --> 00:39:56.400 align:start position:0% because it may change in the future and 00:39:56.400 --> 00:39:58.370 align:start position:0% because it may change in the future and you<00:39:56.579> might<00:39:56.700> be<00:39:56.880> able<00:39:57.000> to<00:39:57.119> go<00:39:57.540> back<00:39:57.720> to<00:39:58.020> Old 00:39:58.370 --> 00:39:58.380 align:start position:0% you might be able to go back to Old 00:39:58.380 --> 00:40:00.530 align:start position:0% you might be able to go back to Old notes<00:39:58.800> and<00:39:58.980> old<00:39:59.160> targets<00:39:59.640> and<00:40:00.000> further<00:40:00.359> do 00:40:00.530 --> 00:40:00.540 align:start position:0% notes and old targets and further do 00:40:00.540 --> 00:40:03.470 align:start position:0% notes and old targets and further do enumeration<00:40:01.200> and<00:40:01.619> testing<00:40:02.160> and<00:40:02.700> lastly<00:40:03.180> one 00:40:03.470 --> 00:40:03.480 align:start position:0% enumeration and testing and lastly one 00:40:03.480 --> 00:40:04.490 align:start position:0% enumeration and testing and lastly one of<00:40:03.599> the<00:40:03.660> things<00:40:03.780> that<00:40:03.960> is<00:40:04.140> going<00:40:04.260> to<00:40:04.320> be<00:40:04.380> really 00:40:04.490 --> 00:40:04.500 align:start position:0% of the things that is going to be really 00:40:04.500 --> 00:40:06.829 align:start position:0% of the things that is going to be really helpful<00:40:04.800> for<00:40:05.099> you<00:40:05.220> in<00:40:06.000> your<00:40:06.359> note-taking 00:40:06.829 --> 00:40:06.839 align:start position:0% helpful for you in your note-taking 00:40:06.839 --> 00:40:08.750 align:start position:0% helpful for you in your note-taking process<00:40:07.500> is<00:40:07.740> to<00:40:07.920> have<00:40:08.099> some<00:40:08.339> kind<00:40:08.460> of<00:40:08.579> a 00:40:08.750 --> 00:40:08.760 align:start position:0% process is to have some kind of a 00:40:08.760 --> 00:40:10.190 align:start position:0% process is to have some kind of a checklist<00:40:09.060> and<00:40:09.300> so<00:40:09.420> one<00:40:09.599> of<00:40:09.720> the<00:40:09.839> last<00:40:09.960> things 00:40:10.190 --> 00:40:10.200 align:start position:0% checklist and so one of the last things 00:40:10.200 --> 00:40:12.170 align:start position:0% checklist and so one of the last things you're<00:40:10.440> going<00:40:10.560> to<00:40:10.680> want<00:40:10.740> to<00:40:10.859> have<00:40:11.040> is<00:40:11.579> a<00:40:11.940> good 00:40:12.170 --> 00:40:12.180 align:start position:0% you're going to want to have is a good 00:40:12.180 --> 00:40:14.450 align:start position:0% you're going to want to have is a good checklist<00:40:12.720> of<00:40:13.079> vulnerabilities<00:40:13.619> and<00:40:13.980> Recon 00:40:14.450 --> 00:40:14.460 align:start position:0% checklist of vulnerabilities and Recon 00:40:14.460 --> 00:40:16.250 align:start position:0% checklist of vulnerabilities and Recon and<00:40:14.940> you<00:40:15.060> can<00:40:15.119> just<00:40:15.240> go<00:40:15.359> out<00:40:15.480> to<00:40:15.660> Google<00:40:15.780> and 00:40:16.250 --> 00:40:16.260 align:start position:0% and you can just go out to Google and 00:40:16.260 --> 00:40:17.870 align:start position:0% and you can just go out to Google and look<00:40:16.560> for<00:40:16.740> a<00:40:16.980> bunch<00:40:17.099> of<00:40:17.220> different<00:40:17.400> checklists 00:40:17.870 --> 00:40:17.880 align:start position:0% look for a bunch of different checklists 00:40:17.880 --> 00:40:19.250 align:start position:0% look for a bunch of different checklists and<00:40:18.000> find<00:40:18.180> whichever<00:40:18.540> one<00:40:18.660> works<00:40:18.960> best<00:40:19.079> for 00:40:19.250 --> 00:40:19.260 align:start position:0% and find whichever one works best for 00:40:19.260 --> 00:40:21.410 align:start position:0% and find whichever one works best for you<00:40:19.440> maybe<00:40:19.920> copy<00:40:20.460> paste<00:40:20.820> it<00:40:20.880> and<00:40:21.000> put<00:40:21.180> it<00:40:21.300> into 00:40:21.410 --> 00:40:21.420 align:start position:0% you maybe copy paste it and put it into 00:40:21.420 --> 00:40:23.870 align:start position:0% you maybe copy paste it and put it into a<00:40:21.720> Word<00:40:21.900> document<00:40:22.320> and<00:40:22.859> modify<00:40:23.400> it<00:40:23.520> and<00:40:23.700> make 00:40:23.870 --> 00:40:23.880 align:start position:0% a Word document and modify it and make 00:40:23.880 --> 00:40:25.849 align:start position:0% a Word document and modify it and make your<00:40:24.060> own<00:40:24.180> but<00:40:24.720> in<00:40:25.079> the<00:40:25.200> meantime<00:40:25.560> you<00:40:25.800> can 00:40:25.849 --> 00:40:25.859 align:start position:0% your own but in the meantime you can 00:40:25.859 --> 00:40:27.470 align:start position:0% your own but in the meantime you can just<00:40:25.980> Google<00:40:26.160> bug<00:40:26.460> Bounty<00:40:26.940> checklist<00:40:27.240> and 00:40:27.470 --> 00:40:27.480 align:start position:0% just Google bug Bounty checklist and 00:40:27.480 --> 00:40:29.630 align:start position:0% just Google bug Bounty checklist and click<00:40:27.839> on<00:40:28.020> one<00:40:28.380> of<00:40:28.500> the<00:40:28.619> checklists<00:40:29.220> and<00:40:29.460> then 00:40:29.630 --> 00:40:29.640 align:start position:0% click on one of the checklists and then 00:40:29.640 --> 00:40:31.490 align:start position:0% click on one of the checklists and then look<00:40:29.940> to<00:40:30.180> see<00:40:30.359> what<00:40:30.599> is<00:40:30.720> in<00:40:30.900> here<00:40:31.020> and<00:40:31.260> you<00:40:31.380> can 00:40:31.490 --> 00:40:31.500 align:start position:0% look to see what is in here and you can 00:40:31.500 --> 00:40:32.930 align:start position:0% look to see what is in here and you can follow<00:40:31.680> their<00:40:32.040> Recon<00:40:32.460> maybe<00:40:32.700> there's 00:40:32.930 --> 00:40:32.940 align:start position:0% follow their Recon maybe there's 00:40:32.940 --> 00:40:34.609 align:start position:0% follow their Recon maybe there's something<00:40:33.119> in<00:40:33.359> here<00:40:33.480> you<00:40:33.599> don't<00:40:33.780> like<00:40:33.900> I<00:40:34.500> used 00:40:34.609 --> 00:40:34.619 align:start position:0% something in here you don't like I used 00:40:34.619 --> 00:40:37.190 align:start position:0% something in here you don't like I used to<00:40:34.800> use<00:40:34.920> HTTP<00:40:35.640> probe<00:40:36.060> but<00:40:36.359> I<00:40:36.540> decided<00:40:36.900> I 00:40:37.190 --> 00:40:37.200 align:start position:0% to use HTTP probe but I decided I 00:40:37.200 --> 00:40:38.450 align:start position:0% to use HTTP probe but I decided I actually<00:40:37.320> like<00:40:37.560> going<00:40:37.800> out<00:40:37.980> and<00:40:38.099> checking 00:40:38.450 --> 00:40:38.460 align:start position:0% actually like going out and checking 00:40:38.460 --> 00:40:40.490 align:start position:0% actually like going out and checking things<00:40:38.640> manually<00:40:39.540> so<00:40:39.839> I<00:40:40.079> don't<00:40:40.140> use<00:40:40.320> this 00:40:40.490 --> 00:40:40.500 align:start position:0% things manually so I don't use this 00:40:40.500 --> 00:40:42.470 align:start position:0% things manually so I don't use this anymore<00:40:40.740> but<00:40:41.520> it<00:40:41.700> would<00:40:41.820> be<00:40:41.940> helpful<00:40:42.180> for<00:40:42.359> you 00:40:42.470 --> 00:40:42.480 align:start position:0% anymore but it would be helpful for you 00:40:42.480 --> 00:40:44.270 align:start position:0% anymore but it would be helpful for you to<00:40:42.720> have<00:40:43.020> something<00:40:43.320> like<00:40:43.619> this<00:40:43.800> some<00:40:44.040> kind<00:40:44.220> of 00:40:44.270 --> 00:40:44.280 align:start position:0% to have something like this some kind of 00:40:44.280 --> 00:40:46.609 align:start position:0% to have something like this some kind of checklist<00:40:44.640> so<00:40:44.880> that<00:40:45.000> way<00:40:45.180> you<00:40:45.359> don't<00:40:45.540> miss<00:40:45.900> any 00:40:46.609 --> 00:40:46.619 align:start position:0% checklist so that way you don't miss any 00:40:46.619 --> 00:40:49.790 align:start position:0% checklist so that way you don't miss any bugs<00:40:47.160> or<00:40:47.579> vulnerabilities<00:40:48.359> or<00:40:49.020> maybe<00:40:49.260> hidden 00:40:49.790 --> 00:40:49.800 align:start position:0% bugs or vulnerabilities or maybe hidden 00:40:49.800 --> 00:40:52.130 align:start position:0% bugs or vulnerabilities or maybe hidden subdomains<00:40:50.520> that<00:40:50.760> you<00:40:51.180> would<00:40:51.720> have<00:40:51.839> otherwise 00:40:52.130 --> 00:40:52.140 align:start position:0% subdomains that you would have otherwise 00:40:52.140 --> 00:40:54.530 align:start position:0% subdomains that you would have otherwise missed<00:40:52.560> without<00:40:52.920> a<00:40:53.400> checklist<00:40:53.880> so<00:40:54.300> this<00:40:54.420> will 00:40:54.530 --> 00:40:54.540 align:start position:0% missed without a checklist so this will 00:40:54.540 --> 00:40:55.550 align:start position:0% missed without a checklist so this will be<00:40:54.660> really<00:40:54.780> helpful<00:40:55.020> for<00:40:55.200> you<00:40:55.320> as<00:40:55.440> you're 00:40:55.550 --> 00:40:55.560 align:start position:0% be really helpful for you as you're 00:40:55.560 --> 00:40:57.710 align:start position:0% be really helpful for you as you're working<00:40:55.680> on<00:40:55.859> on<00:40:56.220> your<00:40:56.400> recon<00:40:56.760> skills<00:40:57.420> in<00:40:57.599> the 00:40:57.710 --> 00:40:57.720 align:start position:0% working on on your recon skills in the 00:40:57.720 --> 00:40:59.630 align:start position:0% working on on your recon skills in the future<00:40:57.839> and<00:40:58.260> developing<00:40:58.800> them<00:40:58.980> so<00:40:59.280> there's<00:40:59.460> a 00:40:59.630 --> 00:40:59.640 align:start position:0% future and developing them so there's a 00:40:59.640 --> 00:41:01.310 align:start position:0% future and developing them so there's a lot<00:40:59.700> of<00:40:59.820> ways<00:41:00.060> to<00:41:00.240> take<00:41:00.540> notes<00:41:00.780> I<00:41:01.020> showed<00:41:01.260> you 00:41:01.310 --> 00:41:01.320 align:start position:0% lot of ways to take notes I showed you 00:41:01.320 --> 00:41:03.109 align:start position:0% lot of ways to take notes I showed you Cherry<00:41:01.560> Tree<00:41:01.800> only<00:41:02.099> because<00:41:02.339> it's<00:41:02.579> in<00:41:02.760> Kali 00:41:03.109 --> 00:41:03.119 align:start position:0% Cherry Tree only because it's in Kali 00:41:03.119 --> 00:41:05.210 align:start position:0% Cherry Tree only because it's in Kali Linux<00:41:03.420> and<00:41:03.599> everybody<00:41:03.780> who<00:41:04.440> is<00:41:04.619> going<00:41:04.800> to<00:41:04.920> be 00:41:05.210 --> 00:41:05.220 align:start position:0% Linux and everybody who is going to be 00:41:05.220 --> 00:41:06.710 align:start position:0% Linux and everybody who is going to be running<00:41:05.579> a<00:41:05.880> virtual<00:41:06.180> machine<00:41:06.300> is<00:41:06.540> going<00:41:06.660> to 00:41:06.710 --> 00:41:06.720 align:start position:0% running a virtual machine is going to 00:41:06.720 --> 00:41:08.390 align:start position:0% running a virtual machine is going to have<00:41:06.839> access<00:41:07.140> to<00:41:07.500> Kali<00:41:07.859> Linux<00:41:08.099> and<00:41:08.280> they're 00:41:08.390 --> 00:41:08.400 align:start position:0% have access to Kali Linux and they're 00:41:08.400 --> 00:41:10.310 align:start position:0% have access to Kali Linux and they're going<00:41:08.520> to<00:41:08.640> have<00:41:08.700> access<00:41:08.880> to<00:41:09.300> Cherry<00:41:09.660> Tree<00:41:09.900> but 00:41:10.310 --> 00:41:10.320 align:start position:0% going to have access to Cherry Tree but 00:41:10.320 --> 00:41:11.630 align:start position:0% going to have access to Cherry Tree but I<00:41:10.500> personally<00:41:10.740> use<00:41:10.920> OneNote<00:41:11.280> and<00:41:11.520> maybe 00:41:11.630 --> 00:41:11.640 align:start position:0% I personally use OneNote and maybe 00:41:11.640 --> 00:41:12.890 align:start position:0% I personally use OneNote and maybe there's<00:41:11.820> something<00:41:12.060> else<00:41:12.300> out<00:41:12.480> there<00:41:12.599> that 00:41:12.890 --> 00:41:12.900 align:start position:0% there's something else out there that 00:41:12.900 --> 00:41:14.750 align:start position:0% there's something else out there that you<00:41:13.020> like<00:41:13.140> to<00:41:13.320> use<00:41:13.440> all<00:41:13.800> right<00:41:13.980> we<00:41:14.280> are<00:41:14.460> going 00:41:14.750 --> 00:41:14.760 align:start position:0% you like to use all right we are going 00:41:14.760 --> 00:41:17.810 align:start position:0% you like to use all right we are going to<00:41:15.000> look<00:41:15.359> at<00:41:15.540> a<00:41:15.720> URL<00:41:16.260> real<00:41:16.500> quick<00:41:16.680> and<00:41:17.400> look<00:41:17.640> at 00:41:17.810 --> 00:41:17.820 align:start position:0% to look at a URL real quick and look at 00:41:17.820 --> 00:41:20.329 align:start position:0% to look at a URL real quick and look at the<00:41:18.000> different<00:41:18.180> parts<00:41:18.480> of<00:41:19.020> the<00:41:19.320> URL<00:41:19.740> just<00:41:20.160> so 00:41:20.329 --> 00:41:20.339 align:start position:0% the different parts of the URL just so 00:41:20.339 --> 00:41:22.069 align:start position:0% the different parts of the URL just so you<00:41:20.520> can<00:41:20.640> get<00:41:20.760> an<00:41:20.940> understanding<00:41:21.359> of<00:41:21.599> what<00:41:21.900> is 00:41:22.069 --> 00:41:22.079 align:start position:0% you can get an understanding of what is 00:41:22.079 --> 00:41:23.690 align:start position:0% you can get an understanding of what is going<00:41:22.500> on<00:41:22.740> when<00:41:22.920> you<00:41:23.040> look<00:41:23.220> at<00:41:23.339> these<00:41:23.520> it's 00:41:23.690 --> 00:41:23.700 align:start position:0% going on when you look at these it's 00:41:23.700 --> 00:41:25.670 align:start position:0% going on when you look at these it's really<00:41:23.880> important<00:41:24.240> in<00:41:24.480> your<00:41:24.599> recon<00:41:24.960> phase<00:41:25.260> to 00:41:25.670 --> 00:41:25.680 align:start position:0% really important in your recon phase to 00:41:25.680 --> 00:41:27.349 align:start position:0% really important in your recon phase to be<00:41:25.800> able<00:41:25.859> to<00:41:25.980> know<00:41:26.160> what<00:41:26.460> URLs<00:41:27.060> look 00:41:27.349 --> 00:41:27.359 align:start position:0% be able to know what URLs look 00:41:27.359 --> 00:41:29.390 align:start position:0% be able to know what URLs look interesting<00:41:27.839> that<00:41:28.140> you<00:41:28.320> can<00:41:28.440> copy<00:41:28.859> and<00:41:29.040> paste 00:41:29.390 --> 00:41:29.400 align:start position:0% interesting that you can copy and paste 00:41:29.400 --> 00:41:31.130 align:start position:0% interesting that you can copy and paste into<00:41:29.520> your<00:41:29.760> notes<00:41:30.060> so<00:41:30.540> that<00:41:30.720> you<00:41:30.839> can<00:41:30.960> come 00:41:31.130 --> 00:41:31.140 align:start position:0% into your notes so that you can come 00:41:31.140 --> 00:41:33.230 align:start position:0% into your notes so that you can come back<00:41:31.320> once<00:41:31.800> you<00:41:31.859> have<00:41:32.040> finished<00:41:32.280> your<00:41:32.700> recon 00:41:33.230 --> 00:41:33.240 align:start position:0% back once you have finished your recon 00:41:33.240 --> 00:41:35.690 align:start position:0% back once you have finished your recon phase<00:41:33.839> and<00:41:34.260> actually<00:41:34.500> start<00:41:34.800> testing<00:41:35.280> so<00:41:35.579> I've 00:41:35.690 --> 00:41:35.700 align:start position:0% phase and actually start testing so I've 00:41:35.700 --> 00:41:37.790 align:start position:0% phase and actually start testing so I've gone<00:41:35.880> ahead<00:41:36.119> here<00:41:36.300> and<00:41:36.660> just<00:41:36.900> typed<00:41:37.200> out<00:41:37.320> a 00:41:37.790 --> 00:41:37.800 align:start position:0% gone ahead here and just typed out a 00:41:37.800 --> 00:41:40.130 align:start position:0% gone ahead here and just typed out a basic<00:41:38.160> example<00:41:38.640> and<00:41:39.420> you're<00:41:39.660> probably<00:41:39.839> all 00:41:40.130 --> 00:41:40.140 align:start position:0% basic example and you're probably all 00:41:40.140 --> 00:41:42.410 align:start position:0% basic example and you're probably all familiar<00:41:40.440> with<00:41:40.619> https<00:41:41.280> and<00:41:41.700> the<00:41:41.880> HTTP 00:41:42.410 --> 00:41:42.420 align:start position:0% familiar with https and the HTTP 00:41:42.420 --> 00:41:45.410 align:start position:0% familiar with https and the HTTP protocol<00:41:43.140> and<00:41:43.859> it<00:41:44.099> is<00:41:44.220> labeled<00:41:44.640> as<00:41:44.820> the<00:41:45.000> schema 00:41:45.410 --> 00:41:45.420 align:start position:0% protocol and it is labeled as the schema 00:41:45.420 --> 00:41:48.589 align:start position:0% protocol and it is labeled as the schema the<00:41:45.599> www<00:41:46.079> dot<00:41:46.859> is<00:41:46.980> not<00:41:47.220> always<00:41:47.339> there<00:41:47.700> this<00:41:48.300> is 00:41:48.589 --> 00:41:48.599 align:start position:0% the www dot is not always there this is 00:41:48.599 --> 00:41:50.329 align:start position:0% the www dot is not always there this is labeled<00:41:49.079> as<00:41:49.320> the<00:41:49.560> subdomain<00:41:50.099> because 00:41:50.329 --> 00:41:50.339 align:start position:0% labeled as the subdomain because 00:41:50.339 --> 00:41:52.370 align:start position:0% labeled as the subdomain because sometimes<00:41:50.880> this<00:41:51.180> could<00:41:51.300> be<00:41:51.420> a<00:41:51.599> this<00:41:52.140> could<00:41:52.260> be 00:41:52.370 --> 00:41:52.380 align:start position:0% sometimes this could be a this could be 00:41:52.380 --> 00:41:55.609 align:start position:0% sometimes this could be a this could be a<00:41:52.560> subdomain<00:41:53.040> listed<00:41:53.460> as<00:41:53.820> sub<00:41:54.480> dot<00:41:55.260> domain<00:41:55.500> and 00:41:55.609 --> 00:41:55.619 align:start position:0% a subdomain listed as sub dot domain and 00:41:55.619 --> 00:41:57.530 align:start position:0% a subdomain listed as sub dot domain and so<00:41:55.800> this<00:41:56.280> is<00:41:56.400> actually<00:41:56.520> a<00:41:56.700> subdomain<00:41:57.180> but<00:41:57.359> that 00:41:57.530 --> 00:41:57.540 align:start position:0% so this is actually a subdomain but that 00:41:57.540 --> 00:42:00.890 align:start position:0% so this is actually a subdomain but that is<00:41:57.660> the<00:41:57.839> same<00:41:58.020> thing<00:41:58.200> as<00:41:58.500> the<00:41:58.800> www<00:41:59.520> dot<00:42:00.240> and<00:42:00.720> so 00:42:00.890 --> 00:42:00.900 align:start position:0% is the same thing as the www dot and so 00:42:00.900 --> 00:42:02.870 align:start position:0% is the same thing as the www dot and so right<00:42:01.079> here<00:42:01.260> we<00:42:01.560> have<00:42:01.740> the<00:42:02.040> domain<00:42:02.460> name<00:42:02.579> which 00:42:02.870 --> 00:42:02.880 align:start position:0% right here we have the domain name which 00:42:02.880 --> 00:42:05.329 align:start position:0% right here we have the domain name which would<00:42:03.000> be<00:42:03.119> like<00:42:03.359> google.com<00:42:04.320> and<00:42:05.040> I'm<00:42:05.160> not 00:42:05.329 --> 00:42:05.339 align:start position:0% would be like google.com and I'm not 00:42:05.339 --> 00:42:08.390 align:start position:0% would be like google.com and I'm not really<00:42:05.460> sure<00:42:05.760> why<00:42:06.740> the.com<00:42:07.740> is<00:42:08.220> actually 00:42:08.390 --> 00:42:08.400 align:start position:0% really sure why the.com is actually 00:42:08.400 --> 00:42:11.150 align:start position:0% really sure why the.com is actually listed<00:42:08.820> as<00:42:09.060> the<00:42:09.480> top<00:42:09.780> domain<00:42:10.140> level<00:42:10.320> because 00:42:11.150 --> 00:42:11.160 align:start position:0% listed as the top domain level because 00:42:11.160 --> 00:42:14.109 align:start position:0% listed as the top domain level because you<00:42:11.520> can<00:42:11.640> use<00:42:11.760> in<00:42:11.940> here<00:42:12.119> like<00:42:12.359> dot<00:42:12.839> UK<00:42:13.140> dot<00:42:13.680> FR 00:42:14.109 --> 00:42:14.119 align:start position:0% you can use in here like dot UK dot FR 00:42:14.119 --> 00:42:16.270 align:start position:0% you can use in here like dot UK dot FR for<00:42:15.119> different 00:42:16.270 --> 00:42:16.280 align:start position:0% for different 00:42:16.280 --> 00:42:18.050 align:start position:0% for different countries.net.org<00:42:17.280> for<00:42:17.460> an<00:42:17.579> organization 00:42:18.050 --> 00:42:18.060 align:start position:0% countries.net.org for an organization 00:42:18.060 --> 00:42:20.510 align:start position:0% countries.net.org for an organization and<00:42:18.780> it's<00:42:18.900> still<00:42:19.140> called<00:42:19.440> the<00:42:19.800> top<00:42:20.099> domain 00:42:20.510 --> 00:42:20.520 align:start position:0% and it's still called the top domain 00:42:20.520 --> 00:42:22.790 align:start position:0% and it's still called the top domain level<00:42:20.700> but<00:42:21.119> that<00:42:21.300> is<00:42:21.599> this<00:42:22.079> portion<00:42:22.500> of<00:42:22.619> the 00:42:22.790 --> 00:42:22.800 align:start position:0% level but that is this portion of the 00:42:22.800 --> 00:42:25.010 align:start position:0% level but that is this portion of the URL<00:42:23.160> so<00:42:23.400> all<00:42:23.579> of<00:42:23.700> this<00:42:23.820> is<00:42:24.000> a<00:42:24.240> pretty<00:42:24.359> basic<00:42:24.720> you 00:42:25.010 --> 00:42:25.020 align:start position:0% URL so all of this is a pretty basic you 00:42:25.020 --> 00:42:27.170 align:start position:0% URL so all of this is a pretty basic you can<00:42:25.140> fuzz<00:42:25.619> this<00:42:25.920> right<00:42:26.280> here<00:42:26.460> the<00:42:26.640> subdomain 00:42:27.170 --> 00:42:27.180 align:start position:0% can fuzz this right here the subdomain 00:42:27.180 --> 00:42:29.569 align:start position:0% can fuzz this right here the subdomain and<00:42:27.599> the<00:42:27.900> most<00:42:28.020> popular<00:42:28.320> subdomain<00:42:29.160> fuzzer 00:42:29.569 --> 00:42:29.579 align:start position:0% and the most popular subdomain fuzzer 00:42:29.579 --> 00:42:31.970 align:start position:0% and the most popular subdomain fuzzer that<00:42:29.880> I<00:42:30.000> can<00:42:30.119> think<00:42:30.240> of<00:42:30.359> is<00:42:30.660> W<00:42:31.020> fuzz<00:42:31.560> I'm<00:42:31.800> sure 00:42:31.970 --> 00:42:31.980 align:start position:0% that I can think of is W fuzz I'm sure 00:42:31.980 --> 00:42:34.970 align:start position:0% that I can think of is W fuzz I'm sure you<00:42:32.160> can<00:42:32.220> use<00:42:32.339> other<00:42:32.520> fuzzers<00:42:33.060> but<00:42:33.780> W<00:42:34.140> fuzz<00:42:34.680> is 00:42:34.970 --> 00:42:34.980 align:start position:0% you can use other fuzzers but W fuzz is 00:42:34.980 --> 00:42:36.890 align:start position:0% you can use other fuzzers but W fuzz is one<00:42:35.339> that<00:42:35.520> seems<00:42:35.820> to<00:42:35.880> work<00:42:36.000> really<00:42:36.240> well<00:42:36.540> for 00:42:36.890 --> 00:42:36.900 align:start position:0% one that seems to work really well for 00:42:36.900 --> 00:42:39.470 align:start position:0% one that seems to work really well for me<00:42:37.079> when<00:42:37.619> I'm<00:42:37.800> doing<00:42:37.980> a<00:42:38.220> subdomain<00:42:38.880> fuzzing 00:42:39.470 --> 00:42:39.480 align:start position:0% me when I'm doing a subdomain fuzzing 00:42:39.480 --> 00:42:41.870 align:start position:0% me when I'm doing a subdomain fuzzing and<00:42:39.780> then<00:42:39.900> right<00:42:40.260> here<00:42:40.500> is<00:42:40.800> when<00:42:41.220> we<00:42:41.520> start<00:42:41.760> to 00:42:41.870 --> 00:42:41.880 align:start position:0% and then right here is when we start to 00:42:41.880 --> 00:42:44.390 align:start position:0% and then right here is when we start to run<00:42:42.240> into<00:42:42.599> the<00:42:42.960> the<00:42:43.079> path<00:42:43.440> or<00:42:43.680> the<00:42:43.859> location<00:42:44.040> to 00:42:44.390 --> 00:42:44.400 align:start position:0% run into the the path or the location to 00:42:44.400 --> 00:42:45.829 align:start position:0% run into the the path or the location to the<00:42:44.520> contents<00:42:44.940> is<00:42:45.060> how<00:42:45.240> I<00:42:45.300> have<00:42:45.420> it<00:42:45.540> labeled 00:42:45.829 --> 00:42:45.839 align:start position:0% the contents is how I have it labeled 00:42:45.839 --> 00:42:48.170 align:start position:0% the contents is how I have it labeled here<00:42:46.079> but<00:42:46.740> I<00:42:46.980> usually<00:42:47.160> think<00:42:47.400> of<00:42:47.579> this<00:42:47.820> as<00:42:48.000> a 00:42:48.170 --> 00:42:48.180 align:start position:0% here but I usually think of this as a 00:42:48.180 --> 00:42:49.970 align:start position:0% here but I usually think of this as a directory<00:42:48.599> this<00:42:48.960> is<00:42:49.079> a<00:42:49.260> directory<00:42:49.680> and<00:42:49.859> then 00:42:49.970 --> 00:42:49.980 align:start position:0% directory this is a directory and then 00:42:49.980 --> 00:42:52.670 align:start position:0% directory this is a directory and then eventually<00:42:50.339> you're<00:42:50.520> going<00:42:50.700> to<00:42:50.820> hit<00:42:51.079> a<00:42:52.079> actual 00:42:52.670 --> 00:42:52.680 align:start position:0% eventually you're going to hit a actual 00:42:52.680 --> 00:42:55.010 align:start position:0% eventually you're going to hit a actual page<00:42:53.160> and<00:42:53.640> you<00:42:53.820> can<00:42:53.940> actually<00:42:54.119> delete<00:42:54.480> some<00:42:54.900> of 00:42:55.010 --> 00:42:55.020 align:start position:0% page and you can actually delete some of 00:42:55.020 --> 00:42:56.870 align:start position:0% page and you can actually delete some of these<00:42:55.260> and<00:42:55.440> you<00:42:55.500> can<00:42:55.619> just<00:42:55.740> go<00:42:56.160> to<00:42:56.339> blog<00:42:56.700> and 00:42:56.870 --> 00:42:56.880 align:start position:0% these and you can just go to blog and 00:42:56.880 --> 00:42:59.030 align:start position:0% these and you can just go to blog and see<00:42:57.000> what's<00:42:57.180> there<00:42:57.480> but<00:42:57.960> this<00:42:58.200> is<00:42:58.380> the<00:42:58.680> path<00:42:58.800> or 00:42:59.030 --> 00:42:59.040 align:start position:0% see what's there but this is the path or 00:42:59.040 --> 00:43:01.130 align:start position:0% see what's there but this is the path or the<00:42:59.220> location<00:42:59.339> of<00:42:59.880> the<00:43:00.060> page<00:43:00.300> now<00:43:00.540> here<00:43:00.780> comes 00:43:01.130 --> 00:43:01.140 align:start position:0% the location of the page now here comes 00:43:01.140 --> 00:43:04.190 align:start position:0% the location of the page now here comes kind<00:43:01.740> of<00:43:01.859> the<00:43:02.460> good<00:43:02.700> part<00:43:03.000> for<00:43:03.420> us<00:43:03.540> to<00:43:03.780> look<00:43:04.020> at 00:43:04.190 --> 00:43:04.200 align:start position:0% kind of the good part for us to look at 00:43:04.200 --> 00:43:06.190 align:start position:0% kind of the good part for us to look at and<00:43:04.500> before<00:43:04.619> we<00:43:04.859> move<00:43:05.040> on<00:43:05.220> you<00:43:05.760> can<00:43:05.880> actually 00:43:06.190 --> 00:43:06.200 align:start position:0% and before we move on you can actually 00:43:06.200 --> 00:43:08.870 align:start position:0% and before we move on you can actually fuzz<00:43:07.200> for<00:43:07.680> different<00:43:07.980> directories<00:43:08.579> right 00:43:08.870 --> 00:43:08.880 align:start position:0% fuzz for different directories right 00:43:08.880 --> 00:43:10.870 align:start position:0% fuzz for different directories right here<00:43:09.000> the<00:43:09.240> same<00:43:09.359> way<00:43:09.540> you<00:43:09.720> would<00:43:09.839> fuzz<00:43:10.260> for 00:43:10.870 --> 00:43:10.880 align:start position:0% here the same way you would fuzz for 00:43:10.880 --> 00:43:13.069 align:start position:0% here the same way you would fuzz for subdomains<00:43:11.880> and<00:43:12.300> look<00:43:12.480> for<00:43:12.660> different 00:43:13.069 --> 00:43:13.079 align:start position:0% subdomains and look for different 00:43:13.079 --> 00:43:15.890 align:start position:0% subdomains and look for different directories<00:43:13.740> within<00:43:14.339> the<00:43:14.880> subdomain<00:43:15.599> or 00:43:15.890 --> 00:43:15.900 align:start position:0% directories within the subdomain or 00:43:15.900 --> 00:43:18.290 align:start position:0% directories within the subdomain or domain<00:43:16.440> and<00:43:16.859> now<00:43:17.040> when<00:43:17.280> we<00:43:17.460> move<00:43:17.640> on<00:43:17.760> to<00:43:17.940> right 00:43:18.290 --> 00:43:18.300 align:start position:0% domain and now when we move on to right 00:43:18.300 --> 00:43:19.790 align:start position:0% domain and now when we move on to right here<00:43:18.480> the<00:43:18.720> question<00:43:18.900> mark<00:43:19.140> what<00:43:19.440> you<00:43:19.560> need<00:43:19.680> to 00:43:19.790 --> 00:43:19.800 align:start position:0% here the question mark what you need to 00:43:19.800 --> 00:43:21.349 align:start position:0% here the question mark what you need to remember<00:43:19.920> about<00:43:20.280> the<00:43:20.520> question<00:43:20.700> mark<00:43:20.940> within 00:43:21.349 --> 00:43:21.359 align:start position:0% remember about the question mark within 00:43:21.359 --> 00:43:25.069 align:start position:0% remember about the question mark within the<00:43:21.540> URL<00:43:21.960> is<00:43:22.500> that<00:43:22.800> it<00:43:23.040> signifies<00:43:23.640> a<00:43:24.240> query<00:43:24.720> and 00:43:25.069 --> 00:43:25.079 align:start position:0% the URL is that it signifies a query and 00:43:25.079 --> 00:43:27.230 align:start position:0% the URL is that it signifies a query and a<00:43:25.260> parameter<00:43:25.740> is<00:43:25.920> about<00:43:26.099> to<00:43:26.339> be<00:43:26.520> dropped<00:43:27.119> in 00:43:27.230 --> 00:43:27.240 align:start position:0% a parameter is about to be dropped in 00:43:27.240 --> 00:43:29.569 align:start position:0% a parameter is about to be dropped in and<00:43:27.900> this<00:43:28.079> is<00:43:28.260> where<00:43:28.500> we<00:43:28.740> can<00:43:28.859> start<00:43:29.040> messing 00:43:29.569 --> 00:43:29.579 align:start position:0% and this is where we can start messing 00:43:29.579 --> 00:43:32.270 align:start position:0% and this is where we can start messing with<00:43:30.000> the<00:43:30.300> URL<00:43:30.720> to<00:43:30.900> see<00:43:31.140> what<00:43:31.619> information<00:43:31.859> we 00:43:32.270 --> 00:43:32.280 align:start position:0% with the URL to see what information we 00:43:32.280 --> 00:43:35.030 align:start position:0% with the URL to see what information we can<00:43:32.400> pull<00:43:32.520> back<00:43:32.760> from<00:43:33.240> the<00:43:33.599> server<00:43:33.960> so<00:43:34.619> you<00:43:34.920> can 00:43:35.030 --> 00:43:35.040 align:start position:0% can pull back from the server so you can 00:43:35.040 --> 00:43:37.849 align:start position:0% can pull back from the server so you can try<00:43:35.400> you<00:43:36.240> can<00:43:36.359> try<00:43:36.480> and<00:43:36.599> look<00:43:36.720> for<00:43:36.960> an<00:43:37.140> lfi<00:43:37.619> an 00:43:37.849 --> 00:43:37.859 align:start position:0% try you can try and look for an lfi an 00:43:37.859 --> 00:43:40.790 align:start position:0% try you can try and look for an lfi an RFI<00:43:38.339> and<00:43:38.579> ssrf<00:43:39.300> and<00:43:39.960> actually<00:43:40.200> right<00:43:40.560> back 00:43:40.790 --> 00:43:40.800 align:start position:0% RFI and ssrf and actually right back 00:43:40.800 --> 00:43:42.710 align:start position:0% RFI and ssrf and actually right back here<00:43:40.980> you<00:43:41.339> can<00:43:41.460> look<00:43:41.700> for<00:43:42.060> directory 00:43:42.710 --> 00:43:42.720 align:start position:0% here you can look for directory 00:43:42.720 --> 00:43:44.930 align:start position:0% here you can look for directory traversals<00:43:43.440> but<00:43:43.920> you<00:43:44.160> have<00:43:44.280> a<00:43:44.520> parameter 00:43:44.930 --> 00:43:44.940 align:start position:0% traversals but you have a parameter 00:43:44.940 --> 00:43:47.930 align:start position:0% traversals but you have a parameter usually<00:43:45.480> it'll<00:43:45.839> be<00:43:46.140> labeled<00:43:47.099> usually<00:43:47.700> it'll 00:43:47.930 --> 00:43:47.940 align:start position:0% usually it'll be labeled usually it'll 00:43:47.940 --> 00:43:49.250 align:start position:0% usually it'll be labeled usually it'll be<00:43:48.060> labeled<00:43:48.420> as<00:43:48.599> something<00:43:48.780> other<00:43:49.020> than 00:43:49.250 --> 00:43:49.260 align:start position:0% be labeled as something other than 00:43:49.260 --> 00:43:51.109 align:start position:0% be labeled as something other than parameter<00:43:49.800> one<00:43:50.280> of<00:43:50.400> the<00:43:50.460> ones<00:43:50.700> that 00:43:51.109 --> 00:43:51.119 align:start position:0% parameter one of the ones that 00:43:51.119 --> 00:43:53.089 align:start position:0% parameter one of the ones that automatically<00:43:51.599> throw<00:43:51.839> up<00:43:52.020> a<00:43:52.200> red<00:43:52.380> flag<00:43:52.619> for<00:43:52.980> me 00:43:53.089 --> 00:43:53.099 align:start position:0% automatically throw up a red flag for me 00:43:53.099 --> 00:43:55.670 align:start position:0% automatically throw up a red flag for me is<00:43:53.400> when<00:43:53.579> I<00:43:53.760> see<00:43:53.880> a<00:43:54.060> parameter<00:43:54.420> that<00:43:54.780> says<00:43:55.020> URL 00:43:55.670 --> 00:43:55.680 align:start position:0% is when I see a parameter that says URL 00:43:55.680 --> 00:43:57.710 align:start position:0% is when I see a parameter that says URL and<00:43:56.339> then<00:43:56.520> this<00:43:56.880> query<00:43:57.119> you're<00:43:57.420> going<00:43:57.540> to<00:43:57.599> look 00:43:57.710 --> 00:43:57.720 align:start position:0% and then this query you're going to look 00:43:57.720 --> 00:43:59.569 align:start position:0% and then this query you're going to look to<00:43:57.900> see<00:43:58.020> if<00:43:58.140> this<00:43:58.319> is<00:43:58.560> querying<00:43:59.040> the<00:43:59.339> actual 00:43:59.569 --> 00:43:59.579 align:start position:0% to see if this is querying the actual 00:43:59.579 --> 00:44:01.730 align:start position:0% to see if this is querying the actual server<00:44:00.000> itself<00:44:00.420> and<00:44:00.900> if<00:44:00.960> it<00:44:01.140> is<00:44:01.200> you<00:44:01.440> can<00:44:01.560> start 00:44:01.730 --> 00:44:01.740 align:start position:0% server itself and if it is you can start 00:44:01.740 --> 00:44:03.770 align:start position:0% server itself and if it is you can start to<00:44:01.920> look<00:44:02.099> for<00:44:02.520> a<00:44:02.880> server-side<00:44:03.359> request 00:44:03.770 --> 00:44:03.780 align:start position:0% to look for a server-side request 00:44:03.780 --> 00:44:05.630 align:start position:0% to look for a server-side request forgery<00:44:04.260> or<00:44:04.380> something<00:44:04.619> along<00:44:05.040> those<00:44:05.339> lines 00:44:05.630 --> 00:44:05.640 align:start position:0% forgery or something along those lines 00:44:05.640 --> 00:44:08.630 align:start position:0% forgery or something along those lines but<00:44:06.420> let's<00:44:06.660> say<00:44:06.839> this<00:44:07.319> just<00:44:07.560> has<00:44:07.859> like<00:44:08.099> an<00:44:08.400> ID 00:44:08.630 --> 00:44:08.640 align:start position:0% but let's say this just has like an ID 00:44:08.640 --> 00:44:12.349 align:start position:0% but let's say this just has like an ID right<00:44:09.180> here<00:44:09.359> of<00:44:09.900> 42<00:44:10.520> and<00:44:11.520> you<00:44:11.940> can<00:44:12.060> go<00:44:12.180> ahead 00:44:12.349 --> 00:44:12.359 align:start position:0% right here of 42 and you can go ahead 00:44:12.359 --> 00:44:14.750 align:start position:0% right here of 42 and you can go ahead and<00:44:12.599> start<00:44:12.839> changing<00:44:13.380> this<00:44:13.560> 42<00:44:14.040> to<00:44:14.579> other 00:44:14.750 --> 00:44:14.760 align:start position:0% and start changing this 42 to other 00:44:14.760 --> 00:44:16.490 align:start position:0% and start changing this 42 to other numbers<00:44:15.000> and<00:44:15.359> see<00:44:15.540> what<00:44:15.720> information<00:44:15.960> you<00:44:16.319> can 00:44:16.490 --> 00:44:16.500 align:start position:0% numbers and see what information you can 00:44:16.500 --> 00:44:17.690 align:start position:0% numbers and see what information you can come<00:44:16.619> back<00:44:16.800> and<00:44:16.980> maybe<00:44:17.099> see<00:44:17.339> if<00:44:17.460> you<00:44:17.579> can 00:44:17.690 --> 00:44:17.700 align:start position:0% come back and maybe see if you can 00:44:17.700 --> 00:44:19.910 align:start position:0% come back and maybe see if you can access<00:44:17.940> some<00:44:18.720> information<00:44:18.960> that<00:44:19.440> you're<00:44:19.740> not 00:44:19.910 --> 00:44:19.920 align:start position:0% access some information that you're not 00:44:19.920 --> 00:44:23.210 align:start position:0% access some information that you're not supposed<00:44:20.099> to<00:44:20.339> so<00:44:20.700> this<00:44:20.940> is<00:44:21.240> a<00:44:21.839> URL<00:44:22.380> and<00:44:22.920> one<00:44:23.099> of 00:44:23.210 --> 00:44:23.220 align:start position:0% supposed to so this is a URL and one of 00:44:23.220 --> 00:44:25.130 align:start position:0% supposed to so this is a URL and one of the<00:44:23.280> reasons<00:44:23.520> I<00:44:23.760> wanted<00:44:24.000> to<00:44:24.240> show<00:44:24.599> you<00:44:24.720> this<00:44:24.900> is 00:44:25.130 --> 00:44:25.140 align:start position:0% the reasons I wanted to show you this is 00:44:25.140 --> 00:44:26.990 align:start position:0% the reasons I wanted to show you this is because<00:44:25.319> when<00:44:25.920> you're<00:44:26.099> in<00:44:26.220> your<00:44:26.339> recon<00:44:26.700> phase 00:44:26.990 --> 00:44:27.000 align:start position:0% because when you're in your recon phase 00:44:27.000 --> 00:44:28.910 align:start position:0% because when you're in your recon phase and<00:44:27.119> you're<00:44:27.300> not<00:44:27.420> yet<00:44:27.540> testing<00:44:27.960> to<00:44:28.619> remember 00:44:28.910 --> 00:44:28.920 align:start position:0% and you're not yet testing to remember 00:44:28.920 --> 00:44:31.190 align:start position:0% and you're not yet testing to remember to<00:44:29.280> save<00:44:29.579> URLs<00:44:30.420> that<00:44:30.660> look<00:44:30.900> really 00:44:31.190 --> 00:44:31.200 align:start position:0% to save URLs that look really 00:44:31.200 --> 00:44:33.410 align:start position:0% to save URLs that look really interesting<00:44:31.619> to<00:44:31.920> you<00:44:32.040> with<00:44:32.760> different<00:44:33.119> parts 00:44:33.410 --> 00:44:33.420 align:start position:0% interesting to you with different parts 00:44:33.420 --> 00:44:35.569 align:start position:0% interesting to you with different parts that<00:44:33.780> you're<00:44:33.960> able<00:44:34.260> to<00:44:34.440> change<00:44:34.680> or<00:44:35.040> fuzz<00:44:35.400> that 00:44:35.569 --> 00:44:35.579 align:start position:0% that you're able to change or fuzz that 00:44:35.579 --> 00:44:37.010 align:start position:0% that you're able to change or fuzz that you<00:44:35.760> think<00:44:35.880> might<00:44:36.300> pull<00:44:36.599> back<00:44:36.780> some 00:44:37.010 --> 00:44:37.020 align:start position:0% you think might pull back some 00:44:37.020 --> 00:44:38.809 align:start position:0% you think might pull back some information<00:44:37.260> that<00:44:38.099> you<00:44:38.280> should<00:44:38.400> not<00:44:38.579> have 00:44:38.809 --> 00:44:38.819 align:start position:0% information that you should not have 00:44:38.819 --> 00:44:41.089 align:start position:0% information that you should not have access<00:44:39.119> to<00:44:39.420> in<00:44:40.140> this<00:44:40.380> video<00:44:40.560> we're<00:44:40.859> going<00:44:41.040> to 00:44:41.089 --> 00:44:41.099 align:start position:0% access to in this video we're going to 00:44:41.099 --> 00:44:44.569 align:start position:0% access to in this video we're going to talk<00:44:41.220> about<00:44:41.400> how<00:44:42.240> the<00:44:42.780> DNS<00:44:43.380> works<00:44:43.980> or<00:44:44.280> the 00:44:44.569 --> 00:44:44.579 align:start position:0% talk about how the DNS works or the 00:44:44.579 --> 00:44:47.690 align:start position:0% talk about how the DNS works or the domain<00:44:45.180> name<00:44:45.359> server<00:44:46.020> so<00:44:46.560> if<00:44:46.800> you<00:44:47.099> decide<00:44:47.520> you 00:44:47.690 --> 00:44:47.700 align:start position:0% domain name server so if you decide you 00:44:47.700 --> 00:44:49.370 align:start position:0% domain name server so if you decide you want<00:44:47.880> to<00:44:48.060> type<00:44:48.480> in<00:44:48.720> something<00:44:49.140> like 00:44:49.370 --> 00:44:49.380 align:start position:0% want to type in something like 00:44:49.380 --> 00:44:52.670 align:start position:0% want to type in something like google.com<00:44:50.119> how<00:44:51.119> does<00:44:51.540> your<00:44:51.900> browser<00:44:52.319> know 00:44:52.670 --> 00:44:52.680 align:start position:0% google.com how does your browser know 00:44:52.680 --> 00:44:55.430 align:start position:0% google.com how does your browser know where<00:44:52.859> to<00:44:52.980> go<00:44:53.160> and<00:44:53.520> find<00:44:53.880> the<00:44:54.540> Google<00:44:55.079> IP 00:44:55.430 --> 00:44:55.440 align:start position:0% where to go and find the Google IP 00:44:55.440 --> 00:44:57.890 align:start position:0% where to go and find the Google IP address<00:44:55.619> us<00:44:56.040> to<00:44:56.339> resolve<00:44:56.880> the<00:44:57.060> web<00:44:57.240> page<00:44:57.480> to 00:44:57.890 --> 00:44:57.900 align:start position:0% address us to resolve the web page to 00:44:57.900 --> 00:45:01.970 align:start position:0% address us to resolve the web page to you<00:44:58.079> so<00:44:58.680> I<00:44:59.099> Googled<00:44:59.579> how<00:44:59.760> DNS<00:45:00.359> works<00:45:01.140> and<00:45:01.680> had 00:45:01.970 --> 00:45:01.980 align:start position:0% you so I Googled how DNS works and had 00:45:01.980 --> 00:45:03.530 align:start position:0% you so I Googled how DNS works and had to<00:45:02.160> go<00:45:02.280> through<00:45:02.400> a<00:45:02.520> few<00:45:02.640> pages<00:45:02.880> before<00:45:03.180> I<00:45:03.420> found 00:45:03.530 --> 00:45:03.540 align:start position:0% to go through a few pages before I found 00:45:03.540 --> 00:45:05.089 align:start position:0% to go through a few pages before I found something<00:45:03.720> that<00:45:03.960> was<00:45:04.140> actually<00:45:04.319> good<00:45:04.680> for<00:45:04.980> an 00:45:05.089 --> 00:45:05.099 align:start position:0% something that was actually good for an 00:45:05.099 --> 00:45:06.349 align:start position:0% something that was actually good for an example<00:45:05.400> and<00:45:05.640> I<00:45:05.760> thought<00:45:05.880> this<00:45:06.000> was<00:45:06.119> a<00:45:06.240> really 00:45:06.349 --> 00:45:06.359 align:start position:0% example and I thought this was a really 00:45:06.359 --> 00:45:07.910 align:start position:0% example and I thought this was a really good<00:45:06.480> example<00:45:06.839> so<00:45:07.319> we're<00:45:07.440> going<00:45:07.560> to<00:45:07.680> go<00:45:07.800> ahead 00:45:07.910 --> 00:45:07.920 align:start position:0% good example so we're going to go ahead 00:45:07.920 --> 00:45:10.790 align:start position:0% good example so we're going to go ahead and<00:45:08.339> walk<00:45:08.640> through<00:45:08.880> it<00:45:09.119> so<00:45:09.480> you<00:45:09.900> have<00:45:10.200> a<00:45:10.440> person 00:45:10.790 --> 00:45:10.800 align:start position:0% and walk through it so you have a person 00:45:10.800 --> 00:45:13.370 align:start position:0% and walk through it so you have a person right<00:45:11.040> here<00:45:11.220> who<00:45:11.520> types<00:45:11.880> in<00:45:12.000> a<00:45:12.540> domain<00:45:13.079> right 00:45:13.370 --> 00:45:13.380 align:start position:0% right here who types in a domain right 00:45:13.380 --> 00:45:16.190 align:start position:0% right here who types in a domain right here<00:45:13.500> and<00:45:13.680> they<00:45:13.859> type<00:45:14.040> in<00:45:14.300> dnssimple.com<00:45:15.300> and 00:45:16.190 --> 00:45:16.200 align:start position:0% here and they type in dnssimple.com and 00:45:16.200 --> 00:45:18.589 align:start position:0% here and they type in dnssimple.com and it<00:45:16.380> will<00:45:16.560> check<00:45:16.859> the<00:45:17.339> web<00:45:17.579> browser's<00:45:18.240> cache 00:45:18.589 --> 00:45:18.599 align:start position:0% it will check the web browser's cache 00:45:18.599 --> 00:45:20.569 align:start position:0% it will check the web browser's cache which<00:45:18.780> you<00:45:18.900> will<00:45:19.079> see<00:45:19.260> right<00:45:19.680> here<00:45:19.859> on<00:45:20.339> your 00:45:20.569 --> 00:45:20.579 align:start position:0% which you will see right here on your 00:45:20.579 --> 00:45:22.970 align:start position:0% which you will see right here on your local<00:45:20.880> machine<00:45:21.180> to<00:45:21.420> see<00:45:21.599> if<00:45:21.720> you<00:45:21.900> have<00:45:22.140> visited 00:45:22.970 --> 00:45:22.980 align:start position:0% local machine to see if you have visited 00:45:22.980 --> 00:45:25.609 align:start position:0% local machine to see if you have visited this<00:45:23.400> page<00:45:23.700> before<00:45:24.119> so<00:45:24.480> if<00:45:24.780> you<00:45:24.900> ever<00:45:25.200> go<00:45:25.500> to 00:45:25.609 --> 00:45:25.619 align:start position:0% this page before so if you ever go to 00:45:25.619 --> 00:45:28.430 align:start position:0% this page before so if you ever go to facebook.com<00:45:26.339> and<00:45:26.760> you're<00:45:26.940> logged<00:45:27.300> in<00:45:27.420> in<00:45:28.200> the 00:45:28.430 --> 00:45:28.440 align:start position:0% facebook.com and you're logged in in the 00:45:28.440 --> 00:45:30.770 align:start position:0% facebook.com and you're logged in in the future<00:45:28.680> next<00:45:29.280> time<00:45:29.460> you<00:45:29.640> go<00:45:29.760> to<00:45:29.880> facebook.com 00:45:30.770 --> 00:45:30.780 align:start position:0% future next time you go to facebook.com 00:45:30.780 --> 00:45:33.530 align:start position:0% future next time you go to facebook.com it<00:45:31.560> automatically<00:45:32.040> logs<00:45:32.700> you<00:45:32.760> in<00:45:32.880> because<00:45:33.119> you 00:45:33.530 --> 00:45:33.540 align:start position:0% it automatically logs you in because you 00:45:33.540 --> 00:45:37.069 align:start position:0% it automatically logs you in because you have<00:45:33.900> stored<00:45:34.560> your<00:45:35.160> session<00:45:35.640> and<00:45:36.060> cookies<00:45:36.359> in 00:45:37.069 --> 00:45:37.079 align:start position:0% have stored your session and cookies in 00:45:37.079 --> 00:45:40.190 align:start position:0% have stored your session and cookies in your<00:45:37.500> cache<00:45:38.160> on<00:45:38.400> your<00:45:38.640> actual<00:45:38.940> browser<00:45:39.359> so<00:45:39.960> it 00:45:40.190 --> 00:45:40.200 align:start position:0% your cache on your actual browser so it 00:45:40.200 --> 00:45:42.170 align:start position:0% your cache on your actual browser so it will<00:45:40.319> automatically<00:45:40.800> log<00:45:40.980> you<00:45:41.220> in<00:45:41.339> but<00:45:41.700> if<00:45:41.940> you 00:45:42.170 --> 00:45:42.180 align:start position:0% will automatically log you in but if you 00:45:42.180 --> 00:45:45.230 align:start position:0% will automatically log you in but if you log<00:45:42.420> into<00:45:42.599> facebook.com<00:45:43.319> using<00:45:43.980> Firefox<00:45:44.460> and 00:45:45.230 --> 00:45:45.240 align:start position:0% log into facebook.com using Firefox and 00:45:45.240 --> 00:45:47.329 align:start position:0% log into facebook.com using Firefox and then<00:45:45.359> you<00:45:45.599> go<00:45:45.780> to<00:45:45.960> a<00:45:46.319> chrome<00:45:46.560> and<00:45:46.920> you<00:45:47.040> try<00:45:47.220> to 00:45:47.329 --> 00:45:47.339 align:start position:0% then you go to a chrome and you try to 00:45:47.339 --> 00:45:49.730 align:start position:0% then you go to a chrome and you try to log<00:45:47.460> into<00:45:47.720> facebook.com<00:45:48.720> you're<00:45:49.319> gonna<00:45:49.500> have 00:45:49.730 --> 00:45:49.740 align:start position:0% log into facebook.com you're gonna have 00:45:49.740 --> 00:45:51.829 align:start position:0% log into facebook.com you're gonna have to<00:45:49.940> re-authenticate<00:45:50.940> because<00:45:51.420> it<00:45:51.720> doesn't 00:45:51.829 --> 00:45:51.839 align:start position:0% to re-authenticate because it doesn't 00:45:51.839 --> 00:45:53.930 align:start position:0% to re-authenticate because it doesn't have<00:45:52.079> that<00:45:52.260> stored<00:45:52.680> in<00:45:52.920> your<00:45:53.040> browser<00:45:53.520> cache 00:45:53.930 --> 00:45:53.940 align:start position:0% have that stored in your browser cache 00:45:53.940 --> 00:45:56.390 align:start position:0% have that stored in your browser cache so<00:45:54.180> the<00:45:54.359> first<00:45:54.540> place<00:45:54.839> when<00:45:55.260> you<00:45:55.380> type<00:45:55.560> been<00:45:56.160> a 00:45:56.390 --> 00:45:56.400 align:start position:0% so the first place when you type been a 00:45:56.400 --> 00:45:59.150 align:start position:0% so the first place when you type been a web<00:45:56.700> address<00:45:56.940> it<00:45:57.420> is<00:45:57.540> going<00:45:57.720> to<00:45:57.839> go<00:45:57.960> to<00:45:58.260> the<00:45:58.859> web 00:45:59.150 --> 00:45:59.160 align:start position:0% web address it is going to go to the web 00:45:59.160 --> 00:46:01.370 align:start position:0% web address it is going to go to the web browser<00:45:59.579> to<00:45:59.760> see<00:45:59.880> if<00:46:00.000> it's<00:46:00.119> stored<00:46:00.540> in<00:46:01.020> the 00:46:01.370 --> 00:46:01.380 align:start position:0% browser to see if it's stored in the 00:46:01.380 --> 00:46:04.010 align:start position:0% browser to see if it's stored in the cache<00:46:01.740> and<00:46:02.099> before<00:46:02.220> we<00:46:02.579> move<00:46:02.940> on<00:46:03.180> here<00:46:03.660> you<00:46:03.900> can 00:46:04.010 --> 00:46:04.020 align:start position:0% cache and before we move on here you can 00:46:04.020 --> 00:46:06.349 align:start position:0% cache and before we move on here you can see<00:46:04.140> right<00:46:04.319> here<00:46:04.500> google.com<00:46:05.099> they<00:46:05.940> have<00:46:06.119> an 00:46:06.349 --> 00:46:06.359 align:start position:0% see right here google.com they have an 00:46:06.359 --> 00:46:09.109 align:start position:0% see right here google.com they have an IP<00:46:06.599> address<00:46:06.780> for<00:46:07.140> that<00:46:07.380> the<00:46:07.980> reason<00:46:08.160> you<00:46:08.819> have 00:46:09.109 --> 00:46:09.119 align:start position:0% IP address for that the reason you have 00:46:09.119 --> 00:46:11.930 align:start position:0% IP address for that the reason you have actual<00:46:09.720> domain<00:46:10.200> names<00:46:10.440> attached<00:46:11.400> to<00:46:11.579> IP 00:46:11.930 --> 00:46:11.940 align:start position:0% actual domain names attached to IP 00:46:11.940 --> 00:46:14.510 align:start position:0% actual domain names attached to IP addresses<00:46:12.420> is<00:46:13.020> because<00:46:13.260> it's<00:46:13.560> easier<00:46:13.980> for<00:46:14.400> us 00:46:14.510 --> 00:46:14.520 align:start position:0% addresses is because it's easier for us 00:46:14.520 --> 00:46:17.030 align:start position:0% addresses is because it's easier for us to<00:46:14.819> remember<00:46:15.000> a<00:46:15.660> domain<00:46:16.140> name<00:46:16.319> such<00:46:16.680> as<00:46:16.800> a 00:46:17.030 --> 00:46:17.040 align:start position:0% to remember a domain name such as a 00:46:17.040 --> 00:46:19.430 align:start position:0% to remember a domain name such as a Facebook<00:46:17.280> rather<00:46:18.119> than<00:46:18.420> a<00:46:18.780> string<00:46:19.140> of<00:46:19.319> numbers 00:46:19.430 --> 00:46:19.440 align:start position:0% Facebook rather than a string of numbers 00:46:19.440 --> 00:46:22.910 align:start position:0% Facebook rather than a string of numbers for<00:46:20.040> facebook.com<00:46:20.700> or<00:46:21.540> a<00:46:21.839> bunch<00:46:22.020> of<00:46:22.200> other<00:46:22.560> web 00:46:22.910 --> 00:46:22.920 align:start position:0% for facebook.com or a bunch of other web 00:46:22.920 --> 00:46:24.650 align:start position:0% for facebook.com or a bunch of other web apps<00:46:23.280> we<00:46:23.460> just<00:46:23.640> remember<00:46:23.760> we<00:46:24.240> need<00:46:24.359> to<00:46:24.480> Google 00:46:24.650 --> 00:46:24.660 align:start position:0% apps we just remember we need to Google 00:46:24.660 --> 00:46:27.230 align:start position:0% apps we just remember we need to Google we<00:46:24.960> don't<00:46:25.079> need<00:46:25.200> to<00:46:25.319> remember<00:46:25.520> this<00:46:26.520> string<00:46:26.940> of 00:46:27.230 --> 00:46:27.240 align:start position:0% we don't need to remember this string of 00:46:27.240 --> 00:46:29.510 align:start position:0% we don't need to remember this string of numbers<00:46:27.660> right<00:46:28.319> here<00:46:28.500> so<00:46:28.859> the<00:46:29.040> purpose<00:46:29.220> of<00:46:29.400> a 00:46:29.510 --> 00:46:29.520 align:start position:0% numbers right here so the purpose of a 00:46:29.520 --> 00:46:31.370 align:start position:0% numbers right here so the purpose of a domain<00:46:29.760> name<00:46:29.880> is<00:46:30.119> to<00:46:30.300> give<00:46:30.480> you<00:46:30.599> an<00:46:30.960> easy<00:46:31.140> way 00:46:31.370 --> 00:46:31.380 align:start position:0% domain name is to give you an easy way 00:46:31.380 --> 00:46:33.890 align:start position:0% domain name is to give you an easy way to<00:46:31.619> remember<00:46:31.740> the<00:46:32.640> contents<00:46:33.119> of<00:46:33.359> a<00:46:33.660> specific 00:46:33.890 --> 00:46:33.900 align:start position:0% to remember the contents of a specific 00:46:33.900 --> 00:46:35.569 align:start position:0% to remember the contents of a specific IP<00:46:34.319> address<00:46:34.500> which<00:46:34.859> is<00:46:34.920> going<00:46:35.099> to<00:46:35.160> resolve<00:46:35.460> to 00:46:35.569 --> 00:46:35.579 align:start position:0% IP address which is going to resolve to 00:46:35.579 --> 00:46:37.670 align:start position:0% IP address which is going to resolve to either<00:46:35.700> Google<00:46:36.000> or<00:46:36.300> Facebook<00:46:36.540> or<00:46:36.960> Wikipedia 00:46:37.670 --> 00:46:37.680 align:start position:0% either Google or Facebook or Wikipedia 00:46:37.680 --> 00:46:39.650 align:start position:0% either Google or Facebook or Wikipedia as<00:46:37.920> you<00:46:38.040> see<00:46:38.220> right<00:46:38.400> here<00:46:38.579> so<00:46:38.940> that<00:46:39.119> is<00:46:39.300> the 00:46:39.650 --> 00:46:39.660 align:start position:0% as you see right here so that is the 00:46:39.660 --> 00:46:42.890 align:start position:0% as you see right here so that is the purpose<00:46:40.140> of<00:46:40.500> the<00:46:40.920> domain<00:46:41.460> name<00:46:41.640> so<00:46:42.060> after<00:46:42.300> your 00:46:42.890 --> 00:46:42.900 align:start position:0% purpose of the domain name so after your 00:46:42.900 --> 00:46:45.710 align:start position:0% purpose of the domain name so after your browser<00:46:43.560> tries<00:46:44.220> to<00:46:44.579> gather<00:46:45.000> the<00:46:45.540> information 00:46:45.710 --> 00:46:45.720 align:start position:0% browser tries to gather the information 00:46:45.720 --> 00:46:48.950 align:start position:0% browser tries to gather the information and<00:46:46.260> it's<00:46:46.440> not<00:46:46.619> able<00:46:46.859> to<00:46:46.980> we<00:46:47.760> can<00:46:47.880> go<00:46:48.359> to<00:46:48.660> the 00:46:48.950 --> 00:46:48.960 align:start position:0% and it's not able to we can go to the 00:46:48.960 --> 00:46:51.170 align:start position:0% and it's not able to we can go to the next<00:46:49.200> page<00:46:49.560> and<00:46:50.040> it<00:46:50.280> shows<00:46:50.579> the<00:46:50.819> packets 00:46:51.170 --> 00:46:51.180 align:start position:0% next page and it shows the packets 00:46:51.180 --> 00:46:55.309 align:start position:0% next page and it shows the packets moving<00:46:51.599> out<00:46:51.780> to<00:46:52.140> the<00:46:52.500> ISP<00:46:53.339> server 00:46:55.309 --> 00:46:55.319 align:start position:0% moving out to the ISP server 00:46:55.319 --> 00:46:57.290 align:start position:0% moving out to the ISP server which<00:46:55.859> is<00:46:56.040> going<00:46:56.220> to<00:46:56.400> be<00:46:56.520> your<00:46:57.119> internet 00:46:57.290 --> 00:46:57.300 align:start position:0% which is going to be your internet 00:46:57.300 --> 00:46:59.630 align:start position:0% which is going to be your internet service<00:46:57.900> provider<00:46:58.440> which<00:46:58.680> we're<00:46:58.859> told<00:46:59.040> right 00:46:59.630 --> 00:46:59.640 align:start position:0% service provider which we're told right 00:46:59.640 --> 00:47:02.150 align:start position:0% service provider which we're told right here<00:46:59.880> and<00:47:00.540> it's<00:47:00.720> going<00:47:00.960> to<00:47:01.079> ask<00:47:01.380> how<00:47:01.859> do<00:47:01.980> we 00:47:02.150 --> 00:47:02.160 align:start position:0% here and it's going to ask how do we 00:47:02.160 --> 00:47:04.849 align:start position:0% here and it's going to ask how do we find<00:47:02.460> this<00:47:03.000> website<00:47:03.420> and<00:47:04.140> it<00:47:04.380> is<00:47:04.500> going<00:47:04.680> to 00:47:04.849 --> 00:47:04.859 align:start position:0% find this website and it is going to 00:47:04.859 --> 00:47:07.609 align:start position:0% find this website and it is going to tell<00:47:04.980> us<00:47:05.160> that<00:47:05.760> the<00:47:06.180> root<00:47:06.420> server<00:47:06.780> knows<00:47:07.380> where 00:47:07.609 --> 00:47:07.619 align:start position:0% tell us that the root server knows where 00:47:07.619 --> 00:47:10.910 align:start position:0% tell us that the root server knows where to<00:47:07.740> find<00:47:07.920> the<00:47:08.099> location<00:47:08.220> for<00:47:08.780> the.com<00:47:09.780> TDL<00:47:10.560> and 00:47:10.910 --> 00:47:10.920 align:start position:0% to find the location for the.com TDL and 00:47:10.920 --> 00:47:12.770 align:start position:0% to find the location for the.com TDL and we've<00:47:11.099> talked<00:47:11.339> about<00:47:11.400> the<00:47:11.640> TDL<00:47:12.060> before<00:47:12.300> it<00:47:12.599> is 00:47:12.770 --> 00:47:12.780 align:start position:0% we've talked about the TDL before it is 00:47:12.780 --> 00:47:15.190 align:start position:0% we've talked about the TDL before it is the<00:47:13.020> top<00:47:13.260> level<00:47:13.440> domain<00:47:13.920> which<00:47:14.099> can<00:47:14.339> be<00:47:14.460> a<00:47:14.640> dot 00:47:15.190 --> 00:47:15.200 align:start position:0% the top level domain which can be a dot 00:47:15.200 --> 00:47:20.150 align:start position:0% the top level domain which can be a dot com.org.edu<00:47:16.220> dot<00:47:17.220> UK<00:47:17.579> dot<00:47:18.540> FR<00:47:18.859> and<00:47:19.859> many 00:47:20.150 --> 00:47:20.160 align:start position:0% com.org.edu dot UK dot FR and many 00:47:20.160 --> 00:47:22.010 align:start position:0% com.org.edu dot UK dot FR and many others<00:47:20.520> so<00:47:20.640> those<00:47:20.819> will<00:47:21.000> be<00:47:21.119> the<00:47:21.540> top<00:47:21.720> level 00:47:22.010 --> 00:47:22.020 align:start position:0% others so those will be the top level 00:47:22.020 --> 00:47:23.870 align:start position:0% others so those will be the top level domain<00:47:22.740> servers<00:47:23.220> and<00:47:23.460> it's<00:47:23.579> going<00:47:23.700> to<00:47:23.819> tell 00:47:23.870 --> 00:47:23.880 align:start position:0% domain servers and it's going to tell 00:47:23.880 --> 00:47:25.849 align:start position:0% domain servers and it's going to tell you<00:47:24.000> to<00:47:24.180> go<00:47:24.240> out<00:47:24.420> to<00:47:24.599> the<00:47:24.900> root<00:47:25.200> server<00:47:25.500> and<00:47:25.740> the 00:47:25.849 --> 00:47:25.859 align:start position:0% you to go out to the root server and the 00:47:25.859 --> 00:47:27.109 align:start position:0% you to go out to the root server and the root<00:47:26.040> server<00:47:26.339> is<00:47:26.520> going<00:47:26.700> to<00:47:26.819> give<00:47:26.940> the 00:47:27.109 --> 00:47:27.119 align:start position:0% root server is going to give the 00:47:27.119 --> 00:47:29.809 align:start position:0% root server is going to give the information<00:47:27.300> back<00:47:27.780> for<00:47:28.440> which<00:47:28.800> TDL<00:47:29.460> server 00:47:29.809 --> 00:47:29.819 align:start position:0% information back for which TDL server 00:47:29.819 --> 00:47:31.730 align:start position:0% information back for which TDL server you<00:47:30.420> are<00:47:30.540> looking<00:47:30.780> for<00:47:31.020> that's<00:47:31.319> going<00:47:31.560> to 00:47:31.730 --> 00:47:31.740 align:start position:0% you are looking for that's going to 00:47:31.740 --> 00:47:33.829 align:start position:0% you are looking for that's going to contain<00:47:32.160> the<00:47:32.460> information<00:47:32.640> you<00:47:33.300> want<00:47:33.420> so<00:47:33.660> if 00:47:33.829 --> 00:47:33.839 align:start position:0% contain the information you want so if 00:47:33.839 --> 00:47:36.950 align:start position:0% contain the information you want so if you<00:47:33.960> want<00:47:34.220> the.com<00:47:35.220> TDL<00:47:36.000> or<00:47:36.300> if<00:47:36.480> you<00:47:36.599> want<00:47:36.720> the 00:47:36.950 --> 00:47:36.960 align:start position:0% you want the.com TDL or if you want the 00:47:36.960 --> 00:47:39.470 align:start position:0% you want the.com TDL or if you want the dot<00:47:37.440> org<00:47:37.680> TDL<00:47:38.099> and<00:47:38.460> the<00:47:38.640> root<00:47:38.819> server<00:47:39.119> is<00:47:39.300> going 00:47:39.470 --> 00:47:39.480 align:start position:0% dot org TDL and the root server is going 00:47:39.480 --> 00:47:42.410 align:start position:0% dot org TDL and the root server is going to<00:47:39.660> pass<00:47:40.140> the<00:47:40.380> information<00:47:40.560> on<00:47:41.099> to<00:47:41.579> the<00:47:42.240> next 00:47:42.410 --> 00:47:42.420 align:start position:0% to pass the information on to the next 00:47:42.420 --> 00:47:44.630 align:start position:0% to pass the information on to the next server<00:47:43.020> inline<00:47:43.500> to<00:47:43.920> give<00:47:44.099> you<00:47:44.220> the 00:47:44.630 --> 00:47:44.640 align:start position:0% server inline to give you the 00:47:44.640 --> 00:47:45.770 align:start position:0% server inline to give you the information 00:47:45.770 --> 00:47:45.780 align:start position:0% information 00:47:45.780 --> 00:47:48.770 align:start position:0% information so<00:47:46.380> here<00:47:46.680> we<00:47:46.800> are<00:47:46.980> at<00:47:47.280> the<00:47:47.520> root<00:47:47.940> server<00:47:48.300> and 00:47:48.770 --> 00:47:48.780 align:start position:0% so here we are at the root server and 00:47:48.780 --> 00:47:50.510 align:start position:0% so here we are at the root server and our<00:47:49.020> packets<00:47:49.440> are<00:47:49.619> going<00:47:49.800> to<00:47:49.980> make<00:47:50.339> the 00:47:50.510 --> 00:47:50.520 align:start position:0% our packets are going to make the 00:47:50.520 --> 00:47:52.849 align:start position:0% our packets are going to make the request<00:47:50.880> and<00:47:51.599> we're<00:47:51.720> going<00:47:51.839> to<00:47:51.960> be<00:47:52.020> told<00:47:52.260> that 00:47:52.849 --> 00:47:52.859 align:start position:0% request and we're going to be told that 00:47:52.859 --> 00:47:55.550 align:start position:0% request and we're going to be told that it<00:47:53.099> doesn't<00:47:53.280> know<00:47:53.520> where<00:47:53.760> to<00:47:54.060> find<00:47:54.560> DNS 00:47:55.550 --> 00:47:55.560 align:start position:0% it doesn't know where to find DNS 00:47:55.560 --> 00:47:57.770 align:start position:0% it doesn't know where to find DNS simple.com<00:47:56.339> but<00:47:57.060> it's<00:47:57.180> going<00:47:57.359> to<00:47:57.480> be<00:47:57.540> able<00:47:57.660> to 00:47:57.770 --> 00:47:57.780 align:start position:0% simple.com but it's going to be able to 00:47:57.780 --> 00:48:00.890 align:start position:0% simple.com but it's going to be able to tell<00:47:57.960> us<00:47:58.140> where<00:47:58.560> the<00:47:58.920> the<00:47:59.099> TLD<00:47:59.460> is<00:47:59.940> located<00:48:00.180> and 00:48:00.890 --> 00:48:00.900 align:start position:0% tell us where the the TLD is located and 00:48:00.900 --> 00:48:02.990 align:start position:0% tell us where the the TLD is located and it's<00:48:01.140> going<00:48:01.380> to<00:48:01.619> send<00:48:01.980> us<00:48:02.160> on<00:48:02.339> our<00:48:02.460> way<00:48:02.579> so<00:48:02.880> you 00:48:02.990 --> 00:48:03.000 align:start position:0% it's going to send us on our way so you 00:48:03.000 --> 00:48:05.450 align:start position:0% it's going to send us on our way so you can<00:48:03.119> see<00:48:03.300> here<00:48:03.540> is<00:48:03.780> root<00:48:04.260> and<00:48:04.619> here<00:48:04.800> are<00:48:05.099> the 00:48:05.450 --> 00:48:05.460 align:start position:0% can see here is root and here are the 00:48:05.460 --> 00:48:08.329 align:start position:0% can see here is root and here are the tlds<00:48:06.300> and<00:48:06.599> it's<00:48:06.720> going<00:48:06.900> to<00:48:07.020> send<00:48:07.260> us<00:48:07.440> to<00:48:07.859> the 00:48:08.329 --> 00:48:08.339 align:start position:0% tlds and it's going to send us to the 00:48:08.339 --> 00:48:10.849 align:start position:0% tlds and it's going to send us to the right<00:48:08.579> one<00:48:08.880> so<00:48:09.420> before<00:48:09.720> we<00:48:09.960> move<00:48:10.140> on<00:48:10.260> too<00:48:10.619> far 00:48:10.849 --> 00:48:10.859 align:start position:0% right one so before we move on too far 00:48:10.859 --> 00:48:12.470 align:start position:0% right one so before we move on too far if<00:48:11.160> you're<00:48:11.280> wondering<00:48:11.640> how<00:48:11.940> this<00:48:12.180> would<00:48:12.359> work 00:48:12.470 --> 00:48:12.480 align:start position:0% if you're wondering how this would work 00:48:12.480 --> 00:48:14.510 align:start position:0% if you're wondering how this would work with<00:48:12.839> say<00:48:13.079> something<00:48:13.380> like<00:48:13.619> the<00:48:13.800> Tor<00:48:14.099> Browser 00:48:14.510 --> 00:48:14.520 align:start position:0% with say something like the Tor Browser 00:48:14.520 --> 00:48:16.970 align:start position:0% with say something like the Tor Browser my<00:48:15.359> understanding<00:48:15.780> of<00:48:16.020> how<00:48:16.140> the<00:48:16.260> Tor<00:48:16.560> Browser 00:48:16.970 --> 00:48:16.980 align:start position:0% my understanding of how the Tor Browser 00:48:16.980 --> 00:48:19.430 align:start position:0% my understanding of how the Tor Browser works<00:48:17.579> is<00:48:17.819> that<00:48:18.000> it's<00:48:18.180> going<00:48:18.420> to<00:48:18.540> encrypt<00:48:19.079> all 00:48:19.430 --> 00:48:19.440 align:start position:0% works is that it's going to encrypt all 00:48:19.440 --> 00:48:21.829 align:start position:0% works is that it's going to encrypt all of<00:48:19.619> your<00:48:19.859> data<00:48:20.400> so<00:48:20.640> that<00:48:20.819> the<00:48:21.000> ISP<00:48:21.420> isn't 00:48:21.829 --> 00:48:21.839 align:start position:0% of your data so that the ISP isn't 00:48:21.839 --> 00:48:24.170 align:start position:0% of your data so that the ISP isn't actually<00:48:22.079> able<00:48:22.380> to<00:48:22.500> track<00:48:23.160> the<00:48:24.000> web 00:48:24.170 --> 00:48:24.180 align:start position:0% actually able to track the web 00:48:24.180 --> 00:48:26.450 align:start position:0% actually able to track the web application<00:48:24.720> that<00:48:25.020> you<00:48:25.200> are<00:48:25.380> trying<00:48:25.619> to<00:48:25.980> reach 00:48:26.450 --> 00:48:26.460 align:start position:0% application that you are trying to reach 00:48:26.460 --> 00:48:29.270 align:start position:0% application that you are trying to reach and<00:48:26.819> the<00:48:27.180> Tor<00:48:27.540> Network<00:48:27.839> opens<00:48:28.440> up<00:48:28.560> a<00:48:28.859> bunch<00:48:29.160> of 00:48:29.270 --> 00:48:29.280 align:start position:0% and the Tor Network opens up a bunch of 00:48:29.280 --> 00:48:31.430 align:start position:0% and the Tor Network opens up a bunch of nodes<00:48:29.579> for<00:48:30.000> your<00:48:30.300> encrypted<00:48:30.780> data<00:48:31.140> and<00:48:31.319> it 00:48:31.430 --> 00:48:31.440 align:start position:0% nodes for your encrypted data and it 00:48:31.440 --> 00:48:32.930 align:start position:0% nodes for your encrypted data and it doesn't<00:48:31.619> actually<00:48:31.859> go<00:48:32.099> through<00:48:32.280> this<00:48:32.579> process 00:48:32.930 --> 00:48:32.940 align:start position:0% doesn't actually go through this process 00:48:32.940 --> 00:48:35.270 align:start position:0% doesn't actually go through this process until<00:48:33.300> actually<00:48:33.660> until<00:48:34.319> after<00:48:34.800> it<00:48:35.099> has 00:48:35.270 --> 00:48:35.280 align:start position:0% until actually until after it has 00:48:35.280 --> 00:48:38.150 align:start position:0% until actually until after it has reached<00:48:35.760> the<00:48:36.180> exit<00:48:36.540> node<00:48:36.900> and<00:48:37.500> that<00:48:37.800> is<00:48:37.920> how 00:48:38.150 --> 00:48:38.160 align:start position:0% reached the exit node and that is how 00:48:38.160 --> 00:48:40.550 align:start position:0% reached the exit node and that is how your<00:48:38.400> ISP<00:48:39.000> your<00:48:39.480> internet<00:48:39.599> service<00:48:40.020> provider 00:48:40.550 --> 00:48:40.560 align:start position:0% your ISP your internet service provider 00:48:40.560 --> 00:48:43.609 align:start position:0% your ISP your internet service provider is<00:48:40.800> not<00:48:40.980> actually<00:48:41.220> able<00:48:41.819> to<00:48:42.060> track<00:48:42.420> where<00:48:43.319> you 00:48:43.609 --> 00:48:43.619 align:start position:0% is not actually able to track where you 00:48:43.619 --> 00:48:47.210 align:start position:0% is not actually able to track where you are<00:48:43.920> sending<00:48:44.579> your<00:48:44.940> requests<00:48:45.480> to<00:48:45.720> to<00:48:46.380> and<00:48:46.920> the 00:48:47.210 --> 00:48:47.220 align:start position:0% are sending your requests to to and the 00:48:47.220 --> 00:48:49.609 align:start position:0% are sending your requests to to and the same<00:48:47.339> thing<00:48:47.520> would<00:48:47.760> work<00:48:47.940> with<00:48:48.300> a<00:48:48.599> VPN<00:48:49.140> as<00:48:49.500> well 00:48:49.609 --> 00:48:49.619 align:start position:0% same thing would work with a VPN as well 00:48:49.619 --> 00:48:52.910 align:start position:0% same thing would work with a VPN as well so<00:48:50.280> on<00:48:50.520> to<00:48:50.700> the<00:48:51.119> next<00:48:51.240> page<00:48:51.660> and<00:48:52.200> it<00:48:52.500> gives<00:48:52.680> a 00:48:52.910 --> 00:48:52.920 align:start position:0% so on to the next page and it gives a 00:48:52.920 --> 00:48:54.710 align:start position:0% so on to the next page and it gives a little<00:48:53.099> bit<00:48:53.220> of<00:48:53.339> a<00:48:53.520> history<00:48:53.700> that<00:48:54.300> we<00:48:54.480> don't 00:48:54.710 --> 00:48:54.720 align:start position:0% little bit of a history that we don't 00:48:54.720 --> 00:48:58.190 align:start position:0% little bit of a history that we don't really<00:48:55.140> care<00:48:55.500> about<00:48:55.740> on<00:48:56.640> the<00:48:57.119> tlds<00:48:57.780> and 00:48:58.190 --> 00:48:58.200 align:start position:0% really care about on the tlds and 00:48:58.200 --> 00:49:01.550 align:start position:0% really care about on the tlds and finally<00:48:58.560> we<00:48:58.920> make<00:48:59.160> it<00:48:59.339> to<00:48:59.520> the.com<00:49:00.359> TLD<00:49:00.900> and 00:49:01.550 --> 00:49:01.560 align:start position:0% finally we make it to the.com TLD and 00:49:01.560 --> 00:49:03.410 align:start position:0% finally we make it to the.com TLD and it's<00:49:01.740> going<00:49:01.920> to<00:49:01.980> say<00:49:02.160> here<00:49:02.520> is<00:49:02.760> the<00:49:03.119> name 00:49:03.410 --> 00:49:03.420 align:start position:0% it's going to say here is the name 00:49:03.420 --> 00:49:05.329 align:start position:0% it's going to say here is the name server<00:49:03.900> one<00:49:04.079> and<00:49:04.319> the<00:49:04.440> name<00:49:04.560> server<00:49:04.920> 2<00:49:05.040> name 00:49:05.329 --> 00:49:05.339 align:start position:0% server one and the name server 2 name 00:49:05.339 --> 00:49:07.609 align:start position:0% server one and the name server 2 name server<00:49:05.700> 3<00:49:05.819> and<00:49:06.060> name<00:49:06.240> server<00:49:06.599> four<00:49:06.839> I'm<00:49:07.380> not 00:49:07.609 --> 00:49:07.619 align:start position:0% server 3 and name server four I'm not 00:49:07.619 --> 00:49:09.410 align:start position:0% server 3 and name server four I'm not actually<00:49:07.859> positive<00:49:08.520> but<00:49:08.760> I<00:49:08.940> think<00:49:09.060> all 00:49:09.410 --> 00:49:09.420 align:start position:0% actually positive but I think all 00:49:09.420 --> 00:49:12.530 align:start position:0% actually positive but I think all domains<00:49:09.900> will<00:49:10.079> have<00:49:10.339> four<00:49:11.339> name<00:49:11.880> servers<00:49:12.420> so 00:49:12.530 --> 00:49:12.540 align:start position:0% domains will have four name servers so 00:49:12.540 --> 00:49:15.349 align:start position:0% domains will have four name servers so if<00:49:12.720> you<00:49:12.780> host<00:49:12.960> with<00:49:13.380> cloudflare<00:49:13.980> or<00:49:14.700> Google 00:49:15.349 --> 00:49:15.359 align:start position:0% if you host with cloudflare or Google 00:49:15.359 --> 00:49:17.510 align:start position:0% if you host with cloudflare or Google domains<00:49:16.260> or<00:49:16.560> and<00:49:16.800> I'm<00:49:16.980> pretty<00:49:17.099> sure<00:49:17.220> with<00:49:17.400> any 00:49:17.510 --> 00:49:17.520 align:start position:0% domains or and I'm pretty sure with any 00:49:17.520 --> 00:49:18.950 align:start position:0% domains or and I'm pretty sure with any other<00:49:17.700> hosting<00:49:18.060> companies<00:49:18.420> you're<00:49:18.660> going<00:49:18.839> to 00:49:18.950 --> 00:49:18.960 align:start position:0% other hosting companies you're going to 00:49:18.960 --> 00:49:21.290 align:start position:0% other hosting companies you're going to have<00:49:19.079> this<00:49:19.319> ns1<00:49:19.859> and<00:49:20.040> S2<00:49:20.460> and<00:49:20.940> you're<00:49:21.000> going<00:49:21.180> to 00:49:21.290 --> 00:49:21.300 align:start position:0% have this ns1 and S2 and you're going to 00:49:21.300 --> 00:49:23.030 align:start position:0% have this ns1 and S2 and you're going to see<00:49:21.420> this<00:49:21.660> when<00:49:21.960> you're<00:49:22.200> actually<00:49:22.500> setting<00:49:22.920> up 00:49:23.030 --> 00:49:23.040 align:start position:0% see this when you're actually setting up 00:49:23.040 --> 00:49:25.370 align:start position:0% see this when you're actually setting up your<00:49:23.339> domain<00:49:23.700> to<00:49:23.880> resolve<00:49:24.359> to<00:49:24.480> a<00:49:24.660> specific<00:49:24.900> IP 00:49:25.370 --> 00:49:25.380 align:start position:0% your domain to resolve to a specific IP 00:49:25.380 --> 00:49:28.130 align:start position:0% your domain to resolve to a specific IP address<00:49:25.560> so<00:49:26.520> it's<00:49:26.700> going<00:49:26.880> to<00:49:27.000> send<00:49:27.119> you<00:49:27.300> to<00:49:27.660> the 00:49:28.130 --> 00:49:28.140 align:start position:0% address so it's going to send you to the 00:49:28.140 --> 00:49:31.670 align:start position:0% address so it's going to send you to the name<00:49:28.440> server<00:49:29.099> at<00:49:29.700> this<00:49:29.940> point<00:49:30.260> and<00:49:31.260> you<00:49:31.500> get 00:49:31.670 --> 00:49:31.680 align:start position:0% name server at this point and you get 00:49:31.680 --> 00:49:34.670 align:start position:0% name server at this point and you get sent<00:49:31.920> on<00:49:32.220> your<00:49:32.400> way<00:49:32.579> to<00:49:33.420> the<00:49:33.720> next<00:49:33.839> page<00:49:34.260> and 00:49:34.670 --> 00:49:34.680 align:start position:0% sent on your way to the next page and 00:49:34.680 --> 00:49:37.609 align:start position:0% sent on your way to the next page and here<00:49:34.920> you<00:49:35.099> make<00:49:35.280> it<00:49:35.460> to<00:49:35.760> the<00:49:36.240> ns1<00:49:36.839> and<00:49:37.079> then<00:49:37.200> S1 00:49:37.609 --> 00:49:37.619 align:start position:0% here you make it to the ns1 and then S1 00:49:37.619 --> 00:49:39.650 align:start position:0% here you make it to the ns1 and then S1 it<00:49:37.920> says<00:49:38.160> I<00:49:38.400> can<00:49:38.579> give<00:49:38.760> you<00:49:38.880> the<00:49:39.180> IP<00:49:39.480> address 00:49:39.650 --> 00:49:39.660 align:start position:0% it says I can give you the IP address 00:49:39.660 --> 00:49:41.750 align:start position:0% it says I can give you the IP address and<00:49:40.380> then<00:49:40.500> you<00:49:40.800> get<00:49:40.920> the<00:49:41.099> IP<00:49:41.339> address<00:49:41.520> and 00:49:41.750 --> 00:49:41.760 align:start position:0% and then you get the IP address and 00:49:41.760 --> 00:49:44.270 align:start position:0% and then you get the IP address and you're<00:49:41.940> able<00:49:42.119> to<00:49:42.240> resolve<00:49:42.960> to<00:49:43.140> that<00:49:43.859> specific 00:49:44.270 --> 00:49:44.280 align:start position:0% you're able to resolve to that specific 00:49:44.280 --> 00:49:47.329 align:start position:0% you're able to resolve to that specific IP<00:49:45.060> address<00:49:45.300> that<00:49:45.900> you<00:49:45.960> query<00:49:46.319> read<00:49:46.859> in<00:49:47.280> the 00:49:47.329 --> 00:49:47.339 align:start position:0% IP address that you query read in the 00:49:47.339 --> 00:49:49.849 align:start position:0% IP address that you query read in the beginning<00:49:47.460> such<00:49:47.940> as<00:49:48.119> google.com<00:49:48.839> so<00:49:49.440> I<00:49:49.680> hope 00:49:49.849 --> 00:49:49.859 align:start position:0% beginning such as google.com so I hope 00:49:49.859 --> 00:49:52.970 align:start position:0% beginning such as google.com so I hope this<00:49:50.280> made<00:49:50.579> sense<00:49:50.880> if<00:49:51.300> not<00:49:51.500> you<00:49:52.500> can<00:49:52.560> watch<00:49:52.800> it 00:49:52.970 --> 00:49:52.980 align:start position:0% this made sense if not you can watch it 00:49:52.980 --> 00:49:54.650 align:start position:0% this made sense if not you can watch it again<00:49:53.099> or<00:49:53.400> you<00:49:53.579> can<00:49:53.640> read<00:49:53.819> through<00:49:54.060> this<00:49:54.300> you 00:49:54.650 --> 00:49:54.660 align:start position:0% again or you can read through this you 00:49:54.660 --> 00:49:57.530 align:start position:0% again or you can read through this you can<00:49:54.780> see<00:49:55.079> the<00:49:55.619> URL<00:49:56.099> is<00:49:56.520> right<00:49:57.000> here<00:49:57.180> for<00:49:57.300> you<00:49:57.420> to 00:49:57.530 --> 00:49:57.540 align:start position:0% can see the URL is right here for you to 00:49:57.540 --> 00:49:59.569 align:start position:0% can see the URL is right here for you to go<00:49:57.720> to<00:49:57.839> or<00:49:58.319> you<00:49:58.500> can<00:49:58.619> Google<00:49:58.740> around<00:49:59.040> and<00:49:59.400> read 00:49:59.569 --> 00:49:59.579 align:start position:0% go to or you can Google around and read 00:49:59.579 --> 00:50:01.190 align:start position:0% go to or you can Google around and read maybe<00:49:59.880> something<00:50:00.180> else<00:50:00.359> explains<00:50:00.839> to<00:50:00.960> you<00:50:01.020> how 00:50:01.190 --> 00:50:01.200 align:start position:0% maybe something else explains to you how 00:50:01.200 --> 00:50:04.190 align:start position:0% maybe something else explains to you how DNS<00:50:01.740> works<00:50:02.160> if<00:50:02.520> this<00:50:02.819> was<00:50:03.060> too<00:50:03.359> confusing<00:50:03.900> and 00:50:04.190 --> 00:50:04.200 align:start position:0% DNS works if this was too confusing and 00:50:04.200 --> 00:50:06.530 align:start position:0% DNS works if this was too confusing and if<00:50:04.619> not<00:50:04.859> you<00:50:05.339> don't<00:50:05.640> necessarily<00:50:06.119> need<00:50:06.420> to 00:50:06.530 --> 00:50:06.540 align:start position:0% if not you don't necessarily need to 00:50:06.540 --> 00:50:09.230 align:start position:0% if not you don't necessarily need to know<00:50:07.079> all<00:50:07.319> of<00:50:07.440> this<00:50:07.619> information<00:50:07.800> to<00:50:08.460> move<00:50:09.060> on 00:50:09.230 --> 00:50:09.240 align:start position:0% know all of this information to move on 00:50:09.240 --> 00:50:11.270 align:start position:0% know all of this information to move on into<00:50:09.540> the<00:50:09.839> world<00:50:09.960> of<00:50:10.200> ethical<00:50:10.500> hacking<00:50:10.920> but<00:50:11.099> I 00:50:11.270 --> 00:50:11.280 align:start position:0% into the world of ethical hacking but I 00:50:11.280 --> 00:50:12.650 align:start position:0% into the world of ethical hacking but I thought<00:50:11.339> it'd<00:50:11.520> be<00:50:11.640> helpful<00:50:11.940> for<00:50:12.420> you<00:50:12.540> to 00:50:12.650 --> 00:50:12.660 align:start position:0% thought it'd be helpful for you to 00:50:12.660 --> 00:50:15.650 align:start position:0% thought it'd be helpful for you to understand<00:50:12.839> how<00:50:13.319> the<00:50:13.440> web<00:50:13.619> works 00:50:15.650 --> 00:50:15.660 align:start position:0% understand how the web works 00:50:15.660 --> 00:50:18.050 align:start position:0% understand how the web works all<00:50:16.200> right<00:50:16.380> in<00:50:16.859> this<00:50:17.099> video<00:50:17.280> we're<00:50:17.579> going<00:50:17.760> to 00:50:18.050 --> 00:50:18.060 align:start position:0% all right in this video we're going to 00:50:18.060 --> 00:50:22.010 align:start position:0% all right in this video we're going to cover<00:50:18.540> a<00:50:19.140> tool<00:50:19.680> that<00:50:20.339> is<00:50:20.520> called<00:50:20.760> dig<00:50:21.300> and<00:50:21.839> it 00:50:22.010 --> 00:50:22.020 align:start position:0% cover a tool that is called dig and it 00:50:22.020 --> 00:50:24.530 align:start position:0% cover a tool that is called dig and it will<00:50:22.200> check<00:50:22.500> for<00:50:22.980> Zone<00:50:23.579> transfers<00:50:24.240> that 00:50:24.530 --> 00:50:24.540 align:start position:0% will check for Zone transfers that 00:50:24.540 --> 00:50:25.550 align:start position:0% will check for Zone transfers that you're<00:50:24.660> going<00:50:24.780> to<00:50:24.900> hear<00:50:25.020> about<00:50:25.140> Zone 00:50:25.550 --> 00:50:25.560 align:start position:0% you're going to hear about Zone 00:50:25.560 --> 00:50:27.710 align:start position:0% you're going to hear about Zone transfers<00:50:26.040> it<00:50:26.339> is<00:50:26.520> a<00:50:26.819> great<00:50:26.940> way<00:50:27.180> to<00:50:27.480> find 00:50:27.710 --> 00:50:27.720 align:start position:0% transfers it is a great way to find 00:50:27.720 --> 00:50:30.829 align:start position:0% transfers it is a great way to find additional<00:50:28.319> subdomains<00:50:29.220> you<00:50:29.640> can<00:50:30.060> use<00:50:30.359> fluff 00:50:30.829 --> 00:50:30.839 align:start position:0% additional subdomains you can use fluff 00:50:30.839 --> 00:50:32.690 align:start position:0% additional subdomains you can use fluff and<00:50:31.020> go<00:50:31.140> Buster<00:50:31.619> and<00:50:31.740> W<00:50:31.859> fuzz<00:50:32.339> and<00:50:32.460> try<00:50:32.579> and 00:50:32.690 --> 00:50:32.700 align:start position:0% and go Buster and W fuzz and try and 00:50:32.700 --> 00:50:35.030 align:start position:0% and go Buster and W fuzz and try and Brute<00:50:33.000> Force<00:50:33.300> for<00:50:33.740> subdomains<00:50:34.740> and<00:50:34.859> use 00:50:35.030 --> 00:50:35.040 align:start position:0% Brute Force for subdomains and use 00:50:35.040 --> 00:50:37.430 align:start position:0% Brute Force for subdomains and use sublister<00:50:35.700> but<00:50:36.119> you<00:50:36.359> can<00:50:36.480> also<00:50:36.660> use<00:50:36.839> dig<00:50:37.140> it's 00:50:37.430 --> 00:50:37.440 align:start position:0% sublister but you can also use dig it's 00:50:37.440 --> 00:50:39.829 align:start position:0% sublister but you can also use dig it's really<00:50:37.680> quick<00:50:37.920> and<00:50:38.579> if<00:50:39.000> there<00:50:39.300> are<00:50:39.480> any 00:50:39.829 --> 00:50:39.839 align:start position:0% really quick and if there are any 00:50:39.839 --> 00:50:42.170 align:start position:0% really quick and if there are any subdomains<00:50:40.560> it's<00:50:40.740> really<00:50:40.920> helpful<00:50:41.339> tool 00:50:42.170 --> 00:50:42.180 align:start position:0% subdomains it's really helpful tool 00:50:42.180 --> 00:50:44.930 align:start position:0% subdomains it's really helpful tool because<00:50:42.359> you'll<00:50:42.660> find<00:50:42.839> them<00:50:43.079> right<00:50:43.380> away<00:50:43.560> so<00:50:44.400> a 00:50:44.930 --> 00:50:44.940 align:start position:0% because you'll find them right away so a 00:50:44.940 --> 00:50:47.890 align:start position:0% because you'll find them right away so a DNS<00:50:45.420> Zone<00:50:45.960> transfer<00:50:46.380> is<00:50:46.920> supposed<00:50:47.160> to 00:50:47.890 --> 00:50:47.900 align:start position:0% DNS Zone transfer is supposed to 00:50:47.900 --> 00:50:51.410 align:start position:0% DNS Zone transfer is supposed to replicate<00:50:48.900> a<00:50:49.260> DNS<00:50:49.680> database<00:50:50.339> between<00:50:50.760> DNS 00:50:51.410 --> 00:50:51.420 align:start position:0% replicate a DNS database between DNS 00:50:51.420 --> 00:50:53.569 align:start position:0% replicate a DNS database between DNS servers<00:50:51.839> which<00:50:52.140> means<00:50:52.500> if<00:50:52.920> it<00:50:53.099> is<00:50:53.220> vulnerable 00:50:53.569 --> 00:50:53.579 align:start position:0% servers which means if it is vulnerable 00:50:53.579 --> 00:50:55.309 align:start position:0% servers which means if it is vulnerable to<00:50:53.819> a<00:50:54.000> Zone<00:50:54.300> transfer<00:50:54.660> it<00:50:54.900> will<00:50:55.020> give<00:50:55.140> us 00:50:55.309 --> 00:50:55.319 align:start position:0% to a Zone transfer it will give us 00:50:55.319 --> 00:50:57.950 align:start position:0% to a Zone transfer it will give us information<00:50:55.619> like<00:50:56.460> subdomains<00:50:57.300> and<00:50:57.599> some 00:50:57.950 --> 00:50:57.960 align:start position:0% information like subdomains and some 00:50:57.960 --> 00:51:00.230 align:start position:0% information like subdomains and some other<00:50:58.079> information<00:50:58.380> which<00:50:58.920> we'll<00:50:59.099> see<00:50:59.339> in 00:51:00.230 --> 00:51:00.240 align:start position:0% other information which we'll see in 00:51:00.240 --> 00:51:02.750 align:start position:0% other information which we'll see in just<00:51:00.599> a<00:51:00.780> second<00:51:00.900> so<00:51:01.319> we'll<00:51:01.440> go<00:51:01.619> ahead<00:51:01.800> and<00:51:02.400> run 00:51:02.750 --> 00:51:02.760 align:start position:0% just a second so we'll go ahead and run 00:51:02.760 --> 00:51:04.849 align:start position:0% just a second so we'll go ahead and run this<00:51:02.940> I<00:51:03.240> have<00:51:03.420> opened<00:51:03.780> up<00:51:03.900> the<00:51:04.140> box<00:51:04.319> friend 00:51:04.849 --> 00:51:04.859 align:start position:0% this I have opened up the box friend 00:51:04.859 --> 00:51:07.130 align:start position:0% this I have opened up the box friend zone<00:51:05.220> from<00:51:05.700> hack<00:51:05.940> the<00:51:06.119> Box<00:51:06.300> because<00:51:06.660> it<00:51:06.960> is 00:51:07.130 --> 00:51:07.140 align:start position:0% zone from hack the Box because it is 00:51:07.140 --> 00:51:10.849 align:start position:0% zone from hack the Box because it is vulnerable<00:51:07.619> to<00:51:08.099> a<00:51:08.579> Zone<00:51:09.359> transfer<00:51:10.020> and<00:51:10.440> if<00:51:10.680> you 00:51:10.849 --> 00:51:10.859 align:start position:0% vulnerable to a Zone transfer and if you 00:51:10.859 --> 00:51:12.829 align:start position:0% vulnerable to a Zone transfer and if you find<00:51:11.220> a<00:51:11.579> bug<00:51:11.819> mining<00:51:12.240> program<00:51:12.420> that's 00:51:12.829 --> 00:51:12.839 align:start position:0% find a bug mining program that's 00:51:12.839 --> 00:51:15.049 align:start position:0% find a bug mining program that's vulnerable<00:51:13.319> to<00:51:13.500> a<00:51:13.619> Zone<00:51:13.920> transfer<00:51:14.339> you're<00:51:14.880> not 00:51:15.049 --> 00:51:15.059 align:start position:0% vulnerable to a Zone transfer you're not 00:51:15.059 --> 00:51:18.890 align:start position:0% vulnerable to a Zone transfer you're not actually<00:51:15.240> able<00:51:15.599> to<00:51:16.319> exploit<00:51:17.040> it<00:51:17.160> and<00:51:17.880> hack<00:51:18.540> per 00:51:18.890 --> 00:51:18.900 align:start position:0% actually able to exploit it and hack per 00:51:18.900 --> 00:51:22.250 align:start position:0% actually able to exploit it and hack per se<00:51:19.140> the<00:51:19.920> web<00:51:20.280> application<00:51:20.760> but<00:51:21.420> when<00:51:21.839> you<00:51:22.020> find 00:51:22.250 --> 00:51:22.260 align:start position:0% se the web application but when you find 00:51:22.260 --> 00:51:23.750 align:start position:0% se the web application but when you find a<00:51:22.500> Zone<00:51:22.680> transfer<00:51:23.099> and<00:51:23.220> something<00:51:23.460> is 00:51:23.750 --> 00:51:23.760 align:start position:0% a Zone transfer and something is 00:51:23.760 --> 00:51:26.390 align:start position:0% a Zone transfer and something is vulnerable<00:51:24.180> to<00:51:24.480> a<00:51:24.839> Zone<00:51:25.200> transfer<00:51:25.619> you'll<00:51:26.099> you 00:51:26.390 --> 00:51:26.400 align:start position:0% vulnerable to a Zone transfer you'll you 00:51:26.400 --> 00:51:28.849 align:start position:0% vulnerable to a Zone transfer you'll you can<00:51:26.640> report<00:51:26.760> it<00:51:27.119> as<00:51:27.359> information<00:51:27.859> disclosure 00:51:28.849 --> 00:51:28.859 align:start position:0% can report it as information disclosure 00:51:28.859 --> 00:51:30.829 align:start position:0% can report it as information disclosure because<00:51:29.099> it's<00:51:29.460> something<00:51:29.700> that<00:51:30.180> should<00:51:30.599> not 00:51:30.829 --> 00:51:30.839 align:start position:0% because it's something that should not 00:51:30.839 --> 00:51:34.370 align:start position:0% because it's something that should not be<00:51:31.200> open<00:51:31.559> to<00:51:31.920> the<00:51:32.460> world<00:51:32.640> so<00:51:33.059> the<00:51:33.660> easy<00:51:33.839> way<00:51:34.079> to 00:51:34.370 --> 00:51:34.380 align:start position:0% be open to the world so the easy way to 00:51:34.380 --> 00:51:37.370 align:start position:0% be open to the world so the easy way to test<00:51:34.680> this<00:51:34.920> is<00:51:35.460> with<00:51:35.640> a<00:51:35.819> tool<00:51:36.059> called<00:51:36.300> dig<00:51:36.839> and 00:51:37.370 --> 00:51:37.380 align:start position:0% test this is with a tool called dig and 00:51:37.380 --> 00:51:41.390 align:start position:0% test this is with a tool called dig and we'll<00:51:37.559> just<00:51:37.800> type<00:51:38.160> in<00:51:38.700> dig<00:51:39.359> so<00:51:39.960> we'll<00:51:40.260> go<00:51:40.500> dig<00:51:40.980> a 00:51:41.390 --> 00:51:41.400 align:start position:0% we'll just type in dig so we'll go dig a 00:51:41.400 --> 00:51:42.950 align:start position:0% we'll just type in dig so we'll go dig a xfr 00:51:42.950 --> 00:51:42.960 align:start position:0% xfr 00:51:42.960 --> 00:51:45.470 align:start position:0% xfr and<00:51:43.500> then<00:51:43.619> we<00:51:43.859> will<00:51:44.040> say<00:51:44.339> at<00:51:44.940> and<00:51:45.300> then<00:51:45.359> we're 00:51:45.470 --> 00:51:45.480 align:start position:0% and then we will say at and then we're 00:51:45.480 --> 00:51:48.049 align:start position:0% and then we will say at and then we're going<00:51:45.599> to<00:51:45.660> use<00:51:45.839> the<00:51:46.020> IP<00:51:46.380> address 00:51:48.049 --> 00:51:48.059 align:start position:0% going to use the IP address 00:51:48.059 --> 00:51:51.829 align:start position:0% going to use the IP address and<00:51:48.720> then<00:51:48.900> we'll<00:51:49.260> use<00:51:49.700> friend<00:51:50.700> zone<00:51:51.540> because 00:51:51.829 --> 00:51:51.839 align:start position:0% and then we'll use friend zone because 00:51:51.839 --> 00:51:55.670 align:start position:0% and then we'll use friend zone because that<00:51:52.260> is<00:51:52.559> the<00:51:53.099> domain<00:51:53.819> that<00:51:54.059> we<00:51:54.359> are<00:51:54.599> after<00:51:54.900> dot 00:51:55.670 --> 00:51:55.680 align:start position:0% that is the domain that we are after dot 00:51:55.680 --> 00:51:56.510 align:start position:0% that is the domain that we are after dot red 00:51:56.510 --> 00:51:56.520 align:start position:0% red 00:51:56.520 --> 00:51:59.270 align:start position:0% red and<00:51:57.180> then<00:51:57.240> we<00:51:57.540> can<00:51:57.660> run<00:51:57.839> this<00:51:58.140> and<00:51:58.559> see<00:51:58.800> what<00:51:59.099> it 00:51:59.270 --> 00:51:59.280 align:start position:0% and then we can run this and see what it 00:51:59.280 --> 00:52:01.790 align:start position:0% and then we can run this and see what it spits<00:51:59.640> out<00:51:59.760> for<00:51:59.940> us<00:52:00.059> we<00:52:00.480> have<00:52:00.720> friend<00:52:01.440> zone 00:52:01.790 --> 00:52:01.800 align:start position:0% spits out for us we have friend zone 00:52:01.800 --> 00:52:03.410 align:start position:0% spits out for us we have friend zone friend<00:52:02.160> zone<00:52:02.400> friend<00:52:02.700> zone<00:52:03.059> and 00:52:03.410 --> 00:52:03.420 align:start position:0% friend zone friend zone and 00:52:03.420 --> 00:52:05.569 align:start position:0% friend zone friend zone and administrator<00:52:04.020> one<00:52:04.380> so<00:52:05.040> this<00:52:05.339> would<00:52:05.460> be 00:52:05.569 --> 00:52:05.579 align:start position:0% administrator one so this would be 00:52:05.579 --> 00:52:06.890 align:start position:0% administrator one so this would be something<00:52:05.819> that<00:52:06.059> would<00:52:06.180> be<00:52:06.300> worth<00:52:06.480> checking 00:52:06.890 --> 00:52:06.900 align:start position:0% something that would be worth checking 00:52:06.900 --> 00:52:09.349 align:start position:0% something that would be worth checking out<00:52:07.020> we<00:52:07.260> have<00:52:07.440> this<00:52:07.619> HR<00:52:08.099> we<00:52:08.640> have<00:52:08.760> an<00:52:08.880> uploads 00:52:09.349 --> 00:52:09.359 align:start position:0% out we have this HR we have an uploads 00:52:09.359 --> 00:52:10.670 align:start position:0% out we have this HR we have an uploads which<00:52:09.480> would<00:52:09.720> also<00:52:10.020> be<00:52:10.140> something<00:52:10.380> worth 00:52:10.670 --> 00:52:10.680 align:start position:0% which would also be something worth 00:52:10.680 --> 00:52:13.790 align:start position:0% which would also be something worth checking<00:52:11.220> out<00:52:11.339> if<00:52:11.640> you're<00:52:11.760> doing<00:52:11.880> a<00:52:12.059> CTF<00:52:12.540> or<00:52:13.500> if 00:52:13.790 --> 00:52:13.800 align:start position:0% checking out if you're doing a CTF or if 00:52:13.800 --> 00:52:16.190 align:start position:0% checking out if you're doing a CTF or if you<00:52:13.980> find<00:52:14.339> this<00:52:14.579> information<00:52:14.760> out<00:52:15.480> in<00:52:15.839> the 00:52:16.190 --> 00:52:16.200 align:start position:0% you find this information out in the 00:52:16.200 --> 00:52:18.710 align:start position:0% you find this information out in the wild<00:52:16.380> and<00:52:17.280> so<00:52:17.460> you<00:52:17.640> can<00:52:17.760> actually<00:52:17.880> save<00:52:18.359> all<00:52:18.599> of 00:52:18.710 --> 00:52:18.720 align:start position:0% wild and so you can actually save all of 00:52:18.720 --> 00:52:21.410 align:start position:0% wild and so you can actually save all of this<00:52:18.960> into<00:52:19.500> an<00:52:20.220> out<00:52:20.400> file<00:52:20.819> and<00:52:21.059> we'll<00:52:21.240> just 00:52:21.410 --> 00:52:21.420 align:start position:0% this into an out file and we'll just 00:52:21.420 --> 00:52:24.170 align:start position:0% this into an out file and we'll just call<00:52:21.599> it<00:52:21.780> Zone<00:52:22.260> just<00:52:22.740> like<00:52:22.980> this<00:52:23.220> and<00:52:24.059> then 00:52:24.170 --> 00:52:24.180 align:start position:0% call it Zone just like this and then 00:52:24.180 --> 00:52:26.990 align:start position:0% call it Zone just like this and then from<00:52:24.660> other<00:52:25.020> Recon<00:52:25.800> that<00:52:26.280> is<00:52:26.460> done<00:52:26.700> on<00:52:26.819> this 00:52:26.990 --> 00:52:27.000 align:start position:0% from other Recon that is done on this 00:52:27.000 --> 00:52:30.710 align:start position:0% from other Recon that is done on this box<00:52:27.119> you<00:52:27.540> also<00:52:27.900> find<00:52:28.700> a<00:52:29.700> another<00:52:30.119> domain 00:52:30.710 --> 00:52:30.720 align:start position:0% box you also find a another domain 00:52:30.720 --> 00:52:33.589 align:start position:0% box you also find a another domain called<00:52:31.260> friend<00:52:31.800> zone<00:52:32.160> portal<00:52:32.819> just<00:52:33.240> like<00:52:33.420> this 00:52:33.589 --> 00:52:33.599 align:start position:0% called friend zone portal just like this 00:52:33.599 --> 00:52:36.710 align:start position:0% called friend zone portal just like this and<00:52:33.839> we<00:52:33.960> can<00:52:34.140> run<00:52:34.260> it<00:52:34.500> and<00:52:35.280> we<00:52:35.760> find<00:52:36.000> admin 00:52:36.710 --> 00:52:36.720 align:start position:0% and we can run it and we find admin 00:52:36.720 --> 00:52:40.130 align:start position:0% and we can run it and we find admin files<00:52:37.380> Imports<00:52:38.160> VPN<00:52:38.880> and<00:52:39.540> you<00:52:39.660> have<00:52:39.780> all<00:52:40.020> of 00:52:40.130 --> 00:52:40.140 align:start position:0% files Imports VPN and you have all of 00:52:40.140 --> 00:52:42.109 align:start position:0% files Imports VPN and you have all of these<00:52:40.319> files<00:52:40.619> as<00:52:40.740> well<00:52:40.920> and<00:52:41.160> so<00:52:41.400> if<00:52:41.640> you<00:52:41.819> double 00:52:42.109 --> 00:52:42.119 align:start position:0% these files as well and so if you double 00:52:42.119 --> 00:52:45.770 align:start position:0% these files as well and so if you double cure<00:52:42.480> it<00:52:42.599> it<00:52:42.780> will<00:52:42.960> just<00:52:43.200> append<00:52:43.740> to<00:52:44.400> our<00:52:45.000> file 00:52:45.770 --> 00:52:45.780 align:start position:0% cure it it will just append to our file 00:52:45.780 --> 00:52:49.130 align:start position:0% cure it it will just append to our file so<00:52:46.020> if<00:52:46.140> we<00:52:46.319> cat<00:52:46.500> out<00:52:46.800> Zone<00:52:47.420> we<00:52:48.420> have<00:52:48.660> all<00:52:49.020> of 00:52:49.130 --> 00:52:49.140 align:start position:0% so if we cat out Zone we have all of 00:52:49.140 --> 00:52:51.530 align:start position:0% so if we cat out Zone we have all of this<00:52:49.319> information<00:52:49.579> and<00:52:50.579> now<00:52:50.760> if<00:52:51.119> you<00:52:51.359> have 00:52:51.530 --> 00:52:51.540 align:start position:0% this information and now if you have 00:52:51.540 --> 00:52:54.349 align:start position:0% this information and now if you have taken<00:52:52.079> my<00:52:52.440> little<00:52:52.740> bash<00:52:53.220> course<00:52:53.700> you<00:52:54.240> know 00:52:54.349 --> 00:52:54.359 align:start position:0% taken my little bash course you know 00:52:54.359 --> 00:52:58.549 align:start position:0% taken my little bash course you know that<00:52:54.780> we<00:52:55.020> can<00:52:55.260> cat<00:52:56.099> out<00:52:56.280> the<00:52:56.520> Zone<00:52:57.300> and<00:52:57.900> we<00:52:58.260> can 00:52:58.549 --> 00:52:58.559 align:start position:0% that we can cat out the Zone and we can 00:52:58.559 --> 00:53:02.089 align:start position:0% that we can cat out the Zone and we can go<00:52:59.099> like<00:52:59.339> this<00:52:59.460> and<00:52:59.640> we<00:52:59.760> can<00:52:59.880> say<00:53:00.000> grep 00:53:02.089 --> 00:53:02.099 align:start position:0% go like this and we can say grep 00:53:02.099 --> 00:53:04.430 align:start position:0% go like this and we can say grep friend<00:53:02.819> zone 00:53:04.430 --> 00:53:04.440 align:start position:0% friend zone 00:53:04.440 --> 00:53:06.650 align:start position:0% friend zone and<00:53:04.980> make<00:53:05.160> sure<00:53:05.280> that<00:53:05.520> works<00:53:05.880> and<00:53:06.119> so<00:53:06.300> It'll 00:53:06.650 --> 00:53:06.660 align:start position:0% and make sure that works and so It'll 00:53:06.660 --> 00:53:08.450 align:start position:0% and make sure that works and so It'll point<00:53:06.839> out<00:53:07.079> it'll<00:53:07.500> give<00:53:07.680> us<00:53:07.859> all<00:53:08.040> everywhere 00:53:08.450 --> 00:53:08.460 align:start position:0% point out it'll give us all everywhere 00:53:08.460 --> 00:53:11.210 align:start position:0% point out it'll give us all everywhere that<00:53:08.700> friend<00:53:08.880> zone<00:53:09.240> is<00:53:09.420> located<00:53:09.859> and<00:53:10.859> then<00:53:10.980> we 00:53:11.210 --> 00:53:11.220 align:start position:0% that friend zone is located and then we 00:53:11.220 --> 00:53:16.490 align:start position:0% that friend zone is located and then we can<00:53:11.400> say<00:53:11.900> grep<00:53:12.900> in<00:53:13.680> and<00:53:14.280> then<00:53:14.460> we<00:53:14.700> want<00:53:14.940> to<00:53:15.500> awk 00:53:16.490 --> 00:53:16.500 align:start position:0% can say grep in and then we want to awk 00:53:16.500 --> 00:53:20.270 align:start position:0% can say grep in and then we want to awk for<00:53:16.740> our<00:53:17.220> cut<00:53:17.520> and<00:53:18.079> go<00:53:19.079> ahead<00:53:19.200> and<00:53:19.380> put<00:53:19.619> in<00:53:19.920> our 00:53:20.270 --> 00:53:20.280 align:start position:0% for our cut and go ahead and put in our 00:53:20.280 --> 00:53:23.390 align:start position:0% for our cut and go ahead and put in our curly<00:53:20.940> braces<00:53:21.420> and<00:53:22.140> quotes<00:53:22.559> and<00:53:22.980> we<00:53:23.099> can<00:53:23.160> say 00:53:23.390 --> 00:53:23.400 align:start position:0% curly braces and quotes and we can say 00:53:23.400 --> 00:53:24.530 align:start position:0% curly braces and quotes and we can say print 00:53:24.530 --> 00:53:24.540 align:start position:0% print 00:53:24.540 --> 00:53:27.890 align:start position:0% print dollar<00:53:25.200> sign<00:53:25.559> one<00:53:26.220> because<00:53:26.880> we<00:53:27.359> only<00:53:27.540> want 00:53:27.890 --> 00:53:27.900 align:start position:0% dollar sign one because we only want 00:53:27.900 --> 00:53:31.250 align:start position:0% dollar sign one because we only want what<00:53:28.200> is<00:53:28.380> at<00:53:28.619> the<00:53:28.920> front<00:53:29.280> of<00:53:29.640> this<00:53:30.300> file 00:53:31.250 --> 00:53:31.260 align:start position:0% what is at the front of this file 00:53:31.260 --> 00:53:34.309 align:start position:0% what is at the front of this file and<00:53:31.859> then<00:53:32.040> we<00:53:32.460> will<00:53:32.819> see<00:53:33.420> what<00:53:33.540> happens<00:53:33.720> yep 00:53:34.309 --> 00:53:34.319 align:start position:0% and then we will see what happens yep 00:53:34.319 --> 00:53:35.270 align:start position:0% and then we will see what happens yep that's<00:53:34.500> what<00:53:34.619> I<00:53:34.740> thought<00:53:34.859> was<00:53:35.040> going<00:53:35.220> to 00:53:35.270 --> 00:53:35.280 align:start position:0% that's what I thought was going to 00:53:35.280 --> 00:53:36.710 align:start position:0% that's what I thought was going to happen<00:53:35.400> it<00:53:35.700> gives<00:53:35.819> us<00:53:36.000> what<00:53:36.119> we<00:53:36.240> want<00:53:36.359> and<00:53:36.599> then 00:53:36.710 --> 00:53:36.720 align:start position:0% happen it gives us what we want and then 00:53:36.720 --> 00:53:40.970 align:start position:0% happen it gives us what we want and then we<00:53:36.960> can<00:53:37.079> say<00:53:37.640> sort<00:53:38.640> Dash<00:53:39.599> U<00:53:39.780> and<00:53:40.680> this<00:53:40.800> should 00:53:40.970 --> 00:53:40.980 align:start position:0% we can say sort Dash U and this should 00:53:40.980 --> 00:53:43.370 align:start position:0% we can say sort Dash U and this should get<00:53:41.160> rid<00:53:41.339> of<00:53:41.520> our<00:53:41.819> replications<00:53:42.660> right<00:53:43.140> here 00:53:43.370 --> 00:53:43.380 align:start position:0% get rid of our replications right here 00:53:43.380 --> 00:53:45.829 align:start position:0% get rid of our replications right here and<00:53:44.099> it<00:53:44.400> does<00:53:44.579> it<00:53:44.819> sorts<00:53:45.119> it<00:53:45.240> out<00:53:45.359> for<00:53:45.480> us<00:53:45.599> and 00:53:45.829 --> 00:53:45.839 align:start position:0% and it does it sorts it out for us and 00:53:45.839 --> 00:53:48.710 align:start position:0% and it does it sorts it out for us and we<00:53:46.079> get<00:53:46.200> rid<00:53:46.440> of<00:53:46.619> a<00:53:46.859> lot<00:53:46.980> of<00:53:47.160> the<00:53:47.460> repeats 00:53:48.710 --> 00:53:48.720 align:start position:0% we get rid of a lot of the repeats 00:53:48.720 --> 00:53:51.890 align:start position:0% we get rid of a lot of the repeats and<00:53:49.200> now<00:53:49.380> you<00:53:49.619> have<00:53:49.859> this<00:53:50.700> nice<00:53:51.059> little<00:53:51.420> happy 00:53:51.890 --> 00:53:51.900 align:start position:0% and now you have this nice little happy 00:53:51.900 --> 00:53:55.130 align:start position:0% and now you have this nice little happy file<00:53:52.440> with<00:53:53.160> just<00:53:53.700> the<00:53:54.000> sub<00:53:54.240> domains<00:53:54.780> that<00:53:54.960> we 00:53:55.130 --> 00:53:55.140 align:start position:0% file with just the sub domains that we 00:53:55.140 --> 00:53:57.829 align:start position:0% file with just the sub domains that we have<00:53:55.260> pulled<00:53:55.619> down<00:53:55.740> from<00:53:56.400> the<00:53:56.940> Zone<00:53:57.300> transfer 00:53:57.829 --> 00:53:57.839 align:start position:0% have pulled down from the Zone transfer 00:53:57.839 --> 00:53:59.930 align:start position:0% have pulled down from the Zone transfer so<00:53:58.260> Zone<00:53:58.619> transfer<00:53:59.099> is<00:53:59.400> something<00:53:59.640> you<00:53:59.880> should 00:53:59.930 --> 00:53:59.940 align:start position:0% so Zone transfer is something you should 00:53:59.940 --> 00:54:01.190 align:start position:0% so Zone transfer is something you should always<00:54:00.119> look<00:54:00.359> at<00:54:00.480> and<00:54:00.660> if<00:54:00.780> you're<00:54:00.839> in<00:54:00.960> a<00:54:01.079> hack 00:54:01.190 --> 00:54:01.200 align:start position:0% always look at and if you're in a hack 00:54:01.200 --> 00:54:02.809 align:start position:0% always look at and if you're in a hack the<00:54:01.380> Box<00:54:01.559> you<00:54:01.800> might<00:54:01.980> have<00:54:02.099> to<00:54:02.220> add<00:54:02.400> more<00:54:02.700> of 00:54:02.809 --> 00:54:02.819 align:start position:0% the Box you might have to add more of 00:54:02.819 --> 00:54:05.450 align:start position:0% the Box you might have to add more of these<00:54:03.000> to<00:54:03.300> your<00:54:03.660> Etsy<00:54:03.839> host<00:54:04.020> file<00:54:04.380> but<00:54:05.040> out<00:54:05.280> in 00:54:05.450 --> 00:54:05.460 align:start position:0% these to your Etsy host file but out in 00:54:05.460 --> 00:54:07.010 align:start position:0% these to your Etsy host file but out in the<00:54:05.579> wild<00:54:05.700> these<00:54:06.300> would<00:54:06.480> be<00:54:06.599> really<00:54:06.780> good 00:54:07.010 --> 00:54:07.020 align:start position:0% the wild these would be really good 00:54:07.020 --> 00:54:10.670 align:start position:0% the wild these would be really good targets<00:54:07.619> to<00:54:08.099> go<00:54:08.520> ahead<00:54:08.819> and<00:54:09.300> try<00:54:09.900> to<00:54:10.500> attack 00:54:10.670 --> 00:54:10.680 align:start position:0% targets to go ahead and try to attack 00:54:10.680 --> 00:54:14.150 align:start position:0% targets to go ahead and try to attack and<00:54:11.099> find<00:54:11.220> exploits<00:54:11.880> on<00:54:12.000> so<00:54:12.720> this<00:54:13.079> is<00:54:13.319> the<00:54:13.740> Zone 00:54:14.150 --> 00:54:14.160 align:start position:0% and find exploits on so this is the Zone 00:54:14.160 --> 00:54:17.329 align:start position:0% and find exploits on so this is the Zone transfer<00:54:14.819> with<00:54:15.300> the<00:54:15.599> Dig<00:54:15.960> tool<00:54:16.559> you'll<00:54:17.220> want 00:54:17.329 --> 00:54:17.339 align:start position:0% transfer with the Dig tool you'll want 00:54:17.339 --> 00:54:19.670 align:start position:0% transfer with the Dig tool you'll want to<00:54:17.460> remember<00:54:17.640> it<00:54:17.940> whenever<00:54:18.359> you<00:54:18.720> see<00:54:18.960> a<00:54:19.440> port 00:54:19.670 --> 00:54:19.680 align:start position:0% to remember it whenever you see a port 00:54:19.680 --> 00:54:22.849 align:start position:0% to remember it whenever you see a port 53<00:54:20.460> that<00:54:21.240> is<00:54:21.420> open<00:54:21.599> that<00:54:22.020> is<00:54:22.140> the<00:54:22.319> port<00:54:22.440> that<00:54:22.740> is 00:54:22.849 --> 00:54:22.859 align:start position:0% 53 that is open that is the port that is 00:54:22.859 --> 00:54:25.910 align:start position:0% 53 that is open that is the port that is used<00:54:23.099> for<00:54:23.460> a<00:54:23.760> Zone<00:54:24.180> transfer<00:54:24.720> so<00:54:25.260> a<00:54:25.559> few<00:54:25.680> things 00:54:25.910 --> 00:54:25.920 align:start position:0% used for a Zone transfer so a few things 00:54:25.920 --> 00:54:28.490 align:start position:0% used for a Zone transfer so a few things to<00:54:26.460> remember<00:54:26.819> about<00:54:27.300> this<00:54:27.660> specific<00:54:27.960> tool<00:54:28.319> if 00:54:28.490 --> 00:54:28.500 align:start position:0% to remember about this specific tool if 00:54:28.500 --> 00:54:31.190 align:start position:0% to remember about this specific tool if you<00:54:28.680> run<00:54:28.800> an<00:54:28.920> nmap<00:54:29.280> scan<00:54:29.579> Port<00:54:30.119> 53<00:54:30.780> if<00:54:31.079> it's 00:54:31.190 --> 00:54:31.200 align:start position:0% you run an nmap scan Port 53 if it's 00:54:31.200 --> 00:54:33.530 align:start position:0% you run an nmap scan Port 53 if it's open<00:54:31.440> you<00:54:31.980> can<00:54:32.040> always<00:54:32.220> try<00:54:32.700> for<00:54:33.059> a<00:54:33.240> Zone 00:54:33.530 --> 00:54:33.540 align:start position:0% open you can always try for a Zone 00:54:33.540 --> 00:54:35.329 align:start position:0% open you can always try for a Zone transfer<00:54:33.960> and<00:54:34.440> see<00:54:34.559> if<00:54:34.680> you<00:54:34.800> can<00:54:34.859> pull<00:54:35.099> down 00:54:35.329 --> 00:54:35.339 align:start position:0% transfer and see if you can pull down 00:54:35.339 --> 00:54:38.089 align:start position:0% transfer and see if you can pull down additional<00:54:36.380> subdomains<00:54:37.380> it's<00:54:37.619> a<00:54:37.800> great<00:54:37.920> place 00:54:38.089 --> 00:54:38.099 align:start position:0% additional subdomains it's a great place 00:54:38.099 --> 00:54:40.130 align:start position:0% additional subdomains it's a great place to<00:54:38.339> grab<00:54:38.520> subdomains<00:54:39.180> you<00:54:39.359> can<00:54:39.480> also<00:54:39.780> report 00:54:40.130 --> 00:54:40.140 align:start position:0% to grab subdomains you can also report 00:54:40.140 --> 00:54:43.130 align:start position:0% to grab subdomains you can also report it<00:54:40.500> as<00:54:40.859> information<00:54:41.160> disclosure<00:54:42.059> if<00:54:42.780> you<00:54:42.960> are 00:54:43.130 --> 00:54:43.140 align:start position:0% it as information disclosure if you are 00:54:43.140 --> 00:54:45.230 align:start position:0% it as information disclosure if you are actually<00:54:43.319> able<00:54:43.619> to<00:54:43.740> pull<00:54:44.339> off<00:54:44.520> a<00:54:44.819> Zone 00:54:45.230 --> 00:54:45.240 align:start position:0% actually able to pull off a Zone 00:54:45.240 --> 00:54:48.109 align:start position:0% actually able to pull off a Zone transfer<00:54:45.720> so<00:54:46.140> with<00:54:46.319> that<00:54:46.500> we<00:54:46.800> will<00:54:47.040> move<00:54:47.460> on<00:54:47.700> to 00:54:48.109 --> 00:54:48.119 align:start position:0% transfer so with that we will move on to 00:54:48.119 --> 00:54:50.510 align:start position:0% transfer so with that we will move on to the<00:54:48.420> next<00:54:48.780> tool<00:54:49.559> all<00:54:49.800> right<00:54:49.920> I<00:54:50.099> want<00:54:50.220> to<00:54:50.339> cover 00:54:50.510 --> 00:54:50.520 align:start position:0% the next tool all right I want to cover 00:54:50.520 --> 00:54:54.470 align:start position:0% the next tool all right I want to cover two<00:54:51.359> more<00:54:51.780> tools<00:54:52.380> that<00:54:53.099> are<00:54:53.400> Recon<00:54:54.000> tools<00:54:54.359> that 00:54:54.470 --> 00:54:54.480 align:start position:0% two more tools that are Recon tools that 00:54:54.480 --> 00:54:56.510 align:start position:0% two more tools that are Recon tools that you're<00:54:54.540> going<00:54:54.660> to<00:54:54.720> hear<00:54:54.900> about<00:54:55.079> but<00:54:55.800> I<00:54:56.400> don't 00:54:56.510 --> 00:54:56.520 align:start position:0% you're going to hear about but I don't 00:54:56.520 --> 00:54:58.309 align:start position:0% you're going to hear about but I don't really<00:54:56.700> use<00:54:56.940> a<00:54:57.119> whole<00:54:57.240> lot<00:54:57.359> because<00:54:57.720> I<00:54:58.200> don't 00:54:58.309 --> 00:54:58.319 align:start position:0% really use a whole lot because I don't 00:54:58.319 --> 00:54:59.809 align:start position:0% really use a whole lot because I don't think<00:54:58.559> I<00:54:58.859> get<00:54:58.980> a<00:54:59.099> whole<00:54:59.220> lot<00:54:59.339> of<00:54:59.460> helpful 00:54:59.809 --> 00:54:59.819 align:start position:0% think I get a whole lot of helpful 00:54:59.819 --> 00:55:01.730 align:start position:0% think I get a whole lot of helpful information<00:55:00.240> from<00:55:00.720> but<00:55:01.140> you're<00:55:01.319> gonna<00:55:01.500> see 00:55:01.730 --> 00:55:01.740 align:start position:0% information from but you're gonna see 00:55:01.740 --> 00:55:03.410 align:start position:0% information from but you're gonna see these<00:55:02.099> in<00:55:02.400> pretty<00:55:02.640> much<00:55:02.760> every<00:55:02.940> penetration 00:55:03.410 --> 00:55:03.420 align:start position:0% these in pretty much every penetration 00:55:03.420 --> 00:55:06.109 align:start position:0% these in pretty much every penetration testing<00:55:03.900> textbook<00:55:04.559> every<00:55:05.280> certification 00:55:06.109 --> 00:55:06.119 align:start position:0% testing textbook every certification 00:55:06.119 --> 00:55:08.750 align:start position:0% testing textbook every certification course<00:55:06.480> you<00:55:06.660> ever<00:55:06.839> come<00:55:07.079> in<00:55:07.260> contact<00:55:07.380> with<00:55:07.800> and 00:55:08.750 --> 00:55:08.760 align:start position:0% course you ever come in contact with and 00:55:08.760 --> 00:55:11.990 align:start position:0% course you ever come in contact with and they<00:55:09.119> are<00:55:09.300> who<00:55:09.599> is<00:55:09.780> and<00:55:10.200> nslookup<00:55:11.040> will<00:55:11.640> you<00:55:11.819> do 00:55:11.990 --> 00:55:12.000 align:start position:0% they are who is and nslookup will you do 00:55:12.000 --> 00:55:14.329 align:start position:0% they are who is and nslookup will you do NS<00:55:12.300> look<00:55:12.540> up<00:55:12.720> real<00:55:12.839> quick<00:55:13.020> because<00:55:13.740> it<00:55:14.220> doesn't 00:55:14.329 --> 00:55:14.339 align:start position:0% NS look up real quick because it doesn't 00:55:14.339 --> 00:55:15.890 align:start position:0% NS look up real quick because it doesn't give<00:55:14.579> us<00:55:14.700> back<00:55:14.880> a<00:55:15.180> whole<00:55:15.300> lot<00:55:15.480> of<00:55:15.720> information 00:55:15.890 --> 00:55:15.900 align:start position:0% give us back a whole lot of information 00:55:15.900 --> 00:55:18.710 align:start position:0% give us back a whole lot of information so<00:55:16.319> we<00:55:16.500> can<00:55:16.619> just<00:55:16.740> type<00:55:16.859> in<00:55:17.099> NS<00:55:17.880> lookup<00:55:18.420> just 00:55:18.710 --> 00:55:18.720 align:start position:0% so we can just type in NS lookup just 00:55:18.720 --> 00:55:20.030 align:start position:0% so we can just type in NS lookup just like<00:55:18.900> this<00:55:19.079> and<00:55:19.380> then<00:55:19.440> you<00:55:19.619> can<00:55:19.740> do<00:55:19.859> something 00:55:20.030 --> 00:55:20.040 align:start position:0% like this and then you can do something 00:55:20.040 --> 00:55:21.250 align:start position:0% like this and then you can do something like 00:55:21.250 --> 00:55:21.260 align:start position:0% like 00:55:21.260 --> 00:55:24.230 align:start position:0% like www.google.com<00:55:22.579> and<00:55:23.579> it's<00:55:23.760> going<00:55:23.940> to<00:55:24.119> tell 00:55:24.230 --> 00:55:24.240 align:start position:0% www.google.com and it's going to tell 00:55:24.240 --> 00:55:26.990 align:start position:0% www.google.com and it's going to tell you<00:55:24.420> their<00:55:25.020> IP<00:55:25.319> address<00:55:25.559> the<00:55:26.339> domain<00:55:26.819> name 00:55:26.990 --> 00:55:27.000 align:start position:0% you their IP address the domain name 00:55:27.000 --> 00:55:30.530 align:start position:0% you their IP address the domain name you're<00:55:27.720> going<00:55:27.900> to<00:55:28.020> get<00:55:28.140> the<00:55:28.640> IPv6<00:55:29.640> name<00:55:30.240> back 00:55:30.530 --> 00:55:30.540 align:start position:0% you're going to get the IPv6 name back 00:55:30.540 --> 00:55:34.490 align:start position:0% you're going to get the IPv6 name back and<00:55:31.380> it's<00:55:31.619> going<00:55:31.859> through<00:55:32.160> Port<00:55:32.640> 53<00:55:33.420> and<00:55:34.260> so 00:55:34.490 --> 00:55:34.500 align:start position:0% and it's going through Port 53 and so 00:55:34.500 --> 00:55:36.290 align:start position:0% and it's going through Port 53 and so this<00:55:34.680> is<00:55:34.740> a<00:55:34.920> tool<00:55:35.160> you<00:55:35.400> would<00:55:35.579> run<00:55:35.700> if<00:55:36.000> you<00:55:36.180> see 00:55:36.290 --> 00:55:36.300 align:start position:0% this is a tool you would run if you see 00:55:36.300 --> 00:55:39.349 align:start position:0% this is a tool you would run if you see Port<00:55:36.540> 53<00:55:37.079> open<00:55:37.319> same<00:55:38.099> as<00:55:38.400> dig<00:55:38.700> and<00:55:39.000> you<00:55:39.180> can<00:55:39.240> get 00:55:39.349 --> 00:55:39.359 align:start position:0% Port 53 open same as dig and you can get 00:55:39.359 --> 00:55:40.730 align:start position:0% Port 53 open same as dig and you can get just<00:55:39.540> a<00:55:39.720> little<00:55:39.780> bit<00:55:39.960> of<00:55:40.079> information<00:55:40.200> back 00:55:40.730 --> 00:55:40.740 align:start position:0% just a little bit of information back 00:55:40.740 --> 00:55:43.549 align:start position:0% just a little bit of information back with<00:55:41.460> NS<00:55:41.940> lookup<00:55:42.420> so<00:55:42.660> you'll<00:55:42.900> hear<00:55:43.079> about<00:55:43.200> this 00:55:43.549 --> 00:55:43.559 align:start position:0% with NS lookup so you'll hear about this 00:55:43.559 --> 00:55:45.410 align:start position:0% with NS lookup so you'll hear about this and<00:55:43.920> you<00:55:44.160> will<00:55:44.339> definitely<00:55:44.700> see<00:55:45.000> it<00:55:45.180> in<00:55:45.300> the 00:55:45.410 --> 00:55:45.420 align:start position:0% and you will definitely see it in the 00:55:45.420 --> 00:55:48.109 align:start position:0% and you will definitely see it in the future<00:55:45.599> this<00:55:46.559> is<00:55:46.740> what<00:55:47.099> it<00:55:47.280> does<00:55:47.460> but<00:55:47.880> then 00:55:48.109 --> 00:55:48.119 align:start position:0% future this is what it does but then 00:55:48.119 --> 00:55:49.430 align:start position:0% future this is what it does but then there's<00:55:48.359> another<00:55:48.540> one<00:55:48.720> one<00:55:49.140> that<00:55:49.319> you're 00:55:49.430 --> 00:55:49.440 align:start position:0% there's another one one that you're 00:55:49.440 --> 00:55:51.349 align:start position:0% there's another one one that you're going<00:55:49.680> to<00:55:49.859> hear<00:55:50.160> about<00:55:50.339> and<00:55:50.760> see<00:55:50.880> regularly 00:55:51.349 --> 00:55:51.359 align:start position:0% going to hear about and see regularly 00:55:51.359 --> 00:55:53.750 align:start position:0% going to hear about and see regularly and<00:55:51.720> it's<00:55:51.900> who<00:55:52.440> is<00:55:52.680> and<00:55:53.099> so<00:55:53.280> if<00:55:53.400> you<00:55:53.460> type<00:55:53.579> in 00:55:53.750 --> 00:55:53.760 align:start position:0% and it's who is and so if you type in 00:55:53.760 --> 00:55:54.910 align:start position:0% and it's who is and so if you type in who<00:55:54.119> is 00:55:54.910 --> 00:55:54.920 align:start position:0% who is 00:55:54.920 --> 00:55:58.010 align:start position:0% who is google.com<00:55:55.920> you're<00:55:56.880> going<00:55:57.000> to<00:55:57.119> get<00:55:57.240> back<00:55:57.480> a 00:55:58.010 --> 00:55:58.020 align:start position:0% google.com you're going to get back a 00:55:58.020 --> 00:56:00.470 align:start position:0% google.com you're going to get back a whole<00:55:58.200> bunch<00:55:58.440> of<00:55:58.800> information<00:55:59.119> and<00:56:00.119> if<00:56:00.300> you're 00:56:00.470 --> 00:56:00.480 align:start position:0% whole bunch of information and if you're 00:56:00.480 --> 00:56:02.030 align:start position:0% whole bunch of information and if you're ever<00:56:00.599> doing<00:56:00.780> like<00:56:00.960> a<00:56:01.079> penetration<00:56:01.500> test<00:56:01.740> this 00:56:02.030 --> 00:56:02.040 align:start position:0% ever doing like a penetration test this 00:56:02.040 --> 00:56:03.530 align:start position:0% ever doing like a penetration test this is<00:56:02.220> actually<00:56:02.460> a<00:56:02.760> good<00:56:02.880> one<00:56:03.000> to<00:56:03.119> run<00:56:03.300> because 00:56:03.530 --> 00:56:03.540 align:start position:0% is actually a good one to run because 00:56:03.540 --> 00:56:05.270 align:start position:0% is actually a good one to run because sometimes<00:56:03.960> you<00:56:04.140> can<00:56:04.260> get<00:56:04.500> back<00:56:04.740> email 00:56:05.270 --> 00:56:05.280 align:start position:0% sometimes you can get back email 00:56:05.280 --> 00:56:07.609 align:start position:0% sometimes you can get back email addresses<00:56:06.000> and<00:56:06.540> a<00:56:06.720> phone<00:56:06.900> number<00:56:07.079> and<00:56:07.440> things 00:56:07.609 --> 00:56:07.619 align:start position:0% addresses and a phone number and things 00:56:07.619 --> 00:56:09.829 align:start position:0% addresses and a phone number and things like<00:56:07.800> that<00:56:07.980> about<00:56:08.400> the<00:56:08.760> company<00:56:08.940> but<00:56:09.540> you<00:56:09.720> can 00:56:09.829 --> 00:56:09.839 align:start position:0% like that about the company but you can 00:56:09.839 --> 00:56:11.089 align:start position:0% like that about the company but you can find<00:56:09.960> out<00:56:10.140> a<00:56:10.319> little<00:56:10.380> bit<00:56:10.500> more<00:56:10.740> about<00:56:10.859> the 00:56:11.089 --> 00:56:11.099 align:start position:0% find out a little bit more about the 00:56:11.099 --> 00:56:13.490 align:start position:0% find out a little bit more about the company<00:56:11.280> so<00:56:11.940> right<00:56:12.240> here<00:56:12.480> you<00:56:12.900> see<00:56:13.140> they're 00:56:13.490 --> 00:56:13.500 align:start position:0% company so right here you see they're 00:56:13.500 --> 00:56:16.910 align:start position:0% company so right here you see they're using<00:56:13.920> the<00:56:14.400> Google<00:56:14.880> domain<00:56:15.720> servers<00:56:16.559> right 00:56:16.910 --> 00:56:16.920 align:start position:0% using the Google domain servers right 00:56:16.920 --> 00:56:18.770 align:start position:0% using the Google domain servers right here<00:56:17.220> which<00:56:17.700> isn't<00:56:18.000> that<00:56:18.119> surprising<00:56:18.480> being 00:56:18.770 --> 00:56:18.780 align:start position:0% here which isn't that surprising being 00:56:18.780 --> 00:56:21.049 align:start position:0% here which isn't that surprising being from<00:56:19.020> Google<00:56:19.380> but<00:56:20.099> if<00:56:20.400> you<00:56:20.520> look<00:56:20.700> at<00:56:20.819> this 00:56:21.049 --> 00:56:21.059 align:start position:0% from Google but if you look at this 00:56:21.059 --> 00:56:24.049 align:start position:0% from Google but if you look at this right<00:56:21.300> here<00:56:21.540> who<00:56:22.020> is<00:56:22.200> Google<00:56:23.099> registered<00:56:23.880> with 00:56:24.049 --> 00:56:24.059 align:start position:0% right here who is Google registered with 00:56:24.059 --> 00:56:25.790 align:start position:0% right here who is Google registered with it's<00:56:24.300> not<00:56:24.480> even<00:56:24.599> registered<00:56:25.260> with<00:56:25.440> the<00:56:25.619> Google 00:56:25.790 --> 00:56:25.800 align:start position:0% it's not even registered with the Google 00:56:25.800 --> 00:56:28.490 align:start position:0% it's not even registered with the Google domains<00:56:26.339> which<00:56:26.460> is<00:56:26.640> kind<00:56:26.940> of<00:56:27.059> ironic<00:56:27.500> that 00:56:28.490 --> 00:56:28.500 align:start position:0% domains which is kind of ironic that 00:56:28.500 --> 00:56:30.770 align:start position:0% domains which is kind of ironic that Google<00:56:28.859> is<00:56:29.280> not<00:56:29.520> does<00:56:29.880> not<00:56:30.059> have<00:56:30.300> their<00:56:30.599> own 00:56:30.770 --> 00:56:30.780 align:start position:0% Google is not does not have their own 00:56:30.780 --> 00:56:33.010 align:start position:0% Google is not does not have their own domain<00:56:31.559> name<00:56:31.740> registered<00:56:32.339> with<00:56:32.460> themselves 00:56:33.010 --> 00:56:33.020 align:start position:0% domain name registered with themselves 00:56:33.020 --> 00:56:36.950 align:start position:0% domain name registered with themselves I'm<00:56:34.020> guessing<00:56:34.440> they<00:56:35.099> must<00:56:35.460> trust<00:56:36.119> this<00:56:36.720> Mark 00:56:36.950 --> 00:56:36.960 align:start position:0% I'm guessing they must trust this Mark 00:56:36.960 --> 00:56:39.290 align:start position:0% I'm guessing they must trust this Mark monitor<00:56:37.500> more<00:56:37.859> with<00:56:38.160> security<00:56:38.400> than<00:56:39.000> they 00:56:39.290 --> 00:56:39.300 align:start position:0% monitor more with security than they 00:56:39.300 --> 00:56:42.170 align:start position:0% monitor more with security than they trust<00:56:39.540> themselves<00:56:40.040> which<00:56:41.040> I<00:56:41.460> mean<00:56:41.579> is<00:56:41.819> saying 00:56:42.170 --> 00:56:42.180 align:start position:0% trust themselves which I mean is saying 00:56:42.180 --> 00:56:44.030 align:start position:0% trust themselves which I mean is saying something<00:56:42.359> I<00:56:43.020> think<00:56:43.200> Google<00:56:43.440> should<00:56:43.859> probably 00:56:44.030 --> 00:56:44.040 align:start position:0% something I think Google should probably 00:56:44.040 --> 00:56:46.130 align:start position:0% something I think Google should probably switch<00:56:44.339> that<00:56:44.579> but<00:56:45.000> anyway<00:56:45.300> if<00:56:45.660> you<00:56:45.780> know<00:56:45.900> why 00:56:46.130 --> 00:56:46.140 align:start position:0% switch that but anyway if you know why 00:56:46.140 --> 00:56:49.190 align:start position:0% switch that but anyway if you know why they're<00:56:46.380> using<00:56:46.859> Mark<00:56:47.400> monitor<00:56:48.000> instead<00:56:48.660> of 00:56:49.190 --> 00:56:49.200 align:start position:0% they're using Mark monitor instead of 00:56:49.200 --> 00:56:51.530 align:start position:0% they're using Mark monitor instead of Google<00:56:49.619> domain<00:56:50.099> names<00:56:50.339> then<00:56:50.880> you<00:56:51.300> can<00:56:51.359> feel 00:56:51.530 --> 00:56:51.540 align:start position:0% Google domain names then you can feel 00:56:51.540 --> 00:56:52.849 align:start position:0% Google domain names then you can feel free<00:56:51.720> to<00:56:51.839> let<00:56:51.960> me<00:56:52.079> know<00:56:52.200> in<00:56:52.440> the<00:56:52.619> comments 00:56:52.849 --> 00:56:52.859 align:start position:0% free to let me know in the comments 00:56:52.859 --> 00:56:54.530 align:start position:0% free to let me know in the comments maybe<00:56:53.160> they're<00:56:53.400> just<00:56:53.579> using<00:56:53.880> it<00:56:54.059> just<00:56:54.359> because 00:56:54.530 --> 00:56:54.540 align:start position:0% maybe they're just using it just because 00:56:54.540 --> 00:56:56.150 align:start position:0% maybe they're just using it just because they've<00:56:54.900> never<00:56:55.079> changed<00:56:55.440> it<00:56:55.500> once<00:56:55.859> Google 00:56:56.150 --> 00:56:56.160 align:start position:0% they've never changed it once Google 00:56:56.160 --> 00:56:59.089 align:start position:0% they've never changed it once Google domains<00:56:56.700> came<00:56:56.819> out<00:56:57.000> anyway<00:56:57.420> this<00:56:58.020> is<00:56:58.200> who<00:56:58.859> is 00:56:59.089 --> 00:56:59.099 align:start position:0% domains came out anyway this is who is 00:56:59.099 --> 00:57:00.890 align:start position:0% domains came out anyway this is who is and<00:56:59.640> it<00:56:59.819> just<00:56:59.940> tells<00:57:00.180> you<00:57:00.300> more<00:57:00.599> information 00:57:00.890 --> 00:57:00.900 align:start position:0% and it just tells you more information 00:57:00.900 --> 00:57:04.190 align:start position:0% and it just tells you more information about<00:57:01.680> the<00:57:02.339> domain<00:57:02.760> name<00:57:02.940> and<00:57:03.839> where<00:57:04.020> it's 00:57:04.190 --> 00:57:04.200 align:start position:0% about the domain name and where it's 00:57:04.200 --> 00:57:06.109 align:start position:0% about the domain name and where it's registered<00:57:04.740> and<00:57:05.220> the<00:57:05.520> kind<00:57:05.700> of<00:57:05.819> the<00:57:05.880> security 00:57:06.109 --> 00:57:06.119 align:start position:0% registered and the kind of the security 00:57:06.119 --> 00:57:08.270 align:start position:0% registered and the kind of the security behind<00:57:06.660> it<00:57:06.839> and<00:57:07.260> who's<00:57:07.500> running<00:57:07.800> it<00:57:07.980> and<00:57:08.160> you 00:57:08.270 --> 00:57:08.280 align:start position:0% behind it and who's running it and you 00:57:08.280 --> 00:57:09.290 align:start position:0% behind it and who's running it and you can<00:57:08.400> look<00:57:08.520> up<00:57:08.640> to<00:57:08.819> see<00:57:08.940> if<00:57:09.059> there's<00:57:09.180> any 00:57:09.290 --> 00:57:09.300 align:start position:0% can look up to see if there's any 00:57:09.300 --> 00:57:10.670 align:start position:0% can look up to see if there's any vulnerabilities<00:57:09.839> or<00:57:10.140> anything<00:57:10.260> like<00:57:10.559> that 00:57:10.670 --> 00:57:10.680 align:start position:0% vulnerabilities or anything like that 00:57:10.680 --> 00:57:12.530 align:start position:0% vulnerabilities or anything like that you're<00:57:11.160> probably<00:57:11.339> not<00:57:11.640> going<00:57:11.819> to<00:57:12.000> find<00:57:12.180> a 00:57:12.530 --> 00:57:12.540 align:start position:0% you're probably not going to find a 00:57:12.540 --> 00:57:15.410 align:start position:0% you're probably not going to find a whole<00:57:12.660> lot<00:57:12.839> from<00:57:13.380> who<00:57:13.920> is<00:57:14.099> other<00:57:14.579> than<00:57:14.940> just 00:57:15.410 --> 00:57:15.420 align:start position:0% whole lot from who is other than just 00:57:15.420 --> 00:57:16.849 align:start position:0% whole lot from who is other than just about<00:57:15.599> the<00:57:15.900> domain<00:57:16.200> name<00:57:16.380> where<00:57:16.680> it's 00:57:16.849 --> 00:57:16.859 align:start position:0% about the domain name where it's 00:57:16.859 --> 00:57:18.710 align:start position:0% about the domain name where it's registered<00:57:17.339> who's<00:57:17.579> is<00:57:17.819> registered<00:57:18.240> with<00:57:18.359> an 00:57:18.710 --> 00:57:18.720 align:start position:0% registered who's is registered with an 00:57:18.720 --> 00:57:22.190 align:start position:0% registered who's is registered with an IP<00:57:19.020> address<00:57:19.260> and<00:57:20.160> basic<00:57:21.000> information<00:57:21.240> like 00:57:22.190 --> 00:57:22.200 align:start position:0% IP address and basic information like 00:57:22.200 --> 00:57:23.690 align:start position:0% IP address and basic information like that<00:57:22.380> so<00:57:22.619> these<00:57:22.859> are<00:57:22.920> two<00:57:23.099> tools<00:57:23.400> that<00:57:23.579> you're 00:57:23.690 --> 00:57:23.700 align:start position:0% that so these are two tools that you're 00:57:23.700 --> 00:57:25.910 align:start position:0% that so these are two tools that you're going<00:57:23.819> to<00:57:23.940> hear<00:57:24.059> about<00:57:24.180> for<00:57:24.720> sure<00:57:24.839> in<00:57:25.800> the 00:57:25.910 --> 00:57:25.920 align:start position:0% going to hear about for sure in the 00:57:25.920 --> 00:57:28.430 align:start position:0% going to hear about for sure in the future<00:57:26.160> and<00:57:26.700> would<00:57:26.940> be<00:57:27.180> worth<00:57:27.660> remembering 00:57:28.430 --> 00:57:28.440 align:start position:0% future and would be worth remembering 00:57:28.440 --> 00:57:30.589 align:start position:0% future and would be worth remembering but<00:57:29.400> I<00:57:29.760> don't<00:57:29.880> use<00:57:30.000> them<00:57:30.180> all<00:57:30.300> that<00:57:30.480> much 00:57:30.589 --> 00:57:30.599 align:start position:0% but I don't use them all that much 00:57:30.599 --> 00:57:32.630 align:start position:0% but I don't use them all that much because<00:57:30.960> I<00:57:31.380> don't<00:57:31.500> find<00:57:31.680> them<00:57:31.859> to<00:57:32.160> be<00:57:32.280> that 00:57:32.630 --> 00:57:32.640 align:start position:0% because I don't find them to be that 00:57:32.640 --> 00:57:34.190 align:start position:0% because I don't find them to be that helpful<00:57:32.940> I<00:57:33.480> wanted<00:57:33.540> to<00:57:33.780> let<00:57:33.839> you<00:57:33.960> know<00:57:34.079> about 00:57:34.190 --> 00:57:34.200 align:start position:0% helpful I wanted to let you know about 00:57:34.200 --> 00:57:35.870 align:start position:0% helpful I wanted to let you know about them<00:57:34.380> because<00:57:34.619> you<00:57:34.920> will<00:57:35.099> see<00:57:35.280> them<00:57:35.520> and<00:57:35.700> hear 00:57:35.870 --> 00:57:35.880 align:start position:0% them because you will see them and hear 00:57:35.880 --> 00:57:37.730 align:start position:0% them because you will see them and hear about<00:57:36.000> them<00:57:36.300> in<00:57:36.540> the<00:57:36.660> future<00:57:36.780> and<00:57:37.140> now<00:57:37.440> you 00:57:37.730 --> 00:57:37.740 align:start position:0% about them in the future and now you 00:57:37.740 --> 00:57:39.950 align:start position:0% about them in the future and now you know<00:57:37.920> what<00:57:38.339> they<00:57:38.520> are<00:57:38.700> and<00:57:38.940> what<00:57:39.059> they<00:57:39.180> do<00:57:39.359> a 00:57:39.950 --> 00:57:39.960 align:start position:0% know what they are and what they do a 00:57:39.960 --> 00:57:42.530 align:start position:0% know what they are and what they do a another<00:57:40.260> tool<00:57:41.040> that<00:57:41.400> would<00:57:41.579> be<00:57:41.880> worth<00:57:42.300> your 00:57:42.530 --> 00:57:42.540 align:start position:0% another tool that would be worth your 00:57:42.540 --> 00:57:46.490 align:start position:0% another tool that would be worth your time<00:57:42.859> investigating<00:57:43.859> is<00:57:44.819> the<00:57:45.240> Harvester<00:57:45.660> it 00:57:46.490 --> 00:57:46.500 align:start position:0% time investigating is the Harvester it 00:57:46.500 --> 00:57:50.329 align:start position:0% time investigating is the Harvester it looks<00:57:46.859> like<00:57:47.460> this<00:57:47.940> and<00:57:48.300> this<00:57:48.599> tool<00:57:49.440> will<00:57:49.980> go 00:57:50.329 --> 00:57:50.339 align:start position:0% looks like this and this tool will go 00:57:50.339 --> 00:57:52.609 align:start position:0% looks like this and this tool will go out<00:57:50.460> and<00:57:50.700> look<00:57:50.880> for<00:57:51.180> other<00:57:51.599> domains<00:57:52.440> and 00:57:52.609 --> 00:57:52.619 align:start position:0% out and look for other domains and 00:57:52.619 --> 00:57:54.589 align:start position:0% out and look for other domains and subdomains<00:57:53.280> and<00:57:53.460> it'll<00:57:53.700> also<00:57:54.000> find<00:57:54.240> email 00:57:54.589 --> 00:57:54.599 align:start position:0% subdomains and it'll also find email 00:57:54.599 --> 00:57:56.690 align:start position:0% subdomains and it'll also find email addresses<00:57:55.260> if<00:57:55.559> you're<00:57:55.680> a<00:57:55.800> penetration<00:57:56.220> tester 00:57:56.690 --> 00:57:56.700 align:start position:0% addresses if you're a penetration tester 00:57:56.700 --> 00:58:00.170 align:start position:0% addresses if you're a penetration tester for<00:57:57.660> you<00:57:57.960> to<00:57:58.200> try<00:57:58.619> and<00:57:58.740> Target<00:57:58.980> and<00:57:59.579> the<00:57:59.880> usage 00:58:00.170 --> 00:58:00.180 align:start position:0% for you to try and Target and the usage 00:58:00.180 --> 00:58:03.349 align:start position:0% for you to try and Target and the usage is<00:58:00.720> really<00:58:01.200> pretty<00:58:01.440> simple<00:58:01.740> you<00:58:02.579> just<00:58:02.880> type<00:58:03.119> in 00:58:03.349 --> 00:58:03.359 align:start position:0% is really pretty simple you just type in 00:58:03.359 --> 00:58:05.569 align:start position:0% is really pretty simple you just type in the<00:58:03.900> Harvester<00:58:04.260> and<00:58:04.680> then<00:58:04.800> you<00:58:04.980> would<00:58:05.099> pass<00:58:05.339> in 00:58:05.569 --> 00:58:05.579 align:start position:0% the Harvester and then you would pass in 00:58:05.579 --> 00:58:10.250 align:start position:0% the Harvester and then you would pass in a<00:58:06.059> domain<00:58:06.480> with<00:58:07.440> the<00:58:07.680> Dash<00:58:08.160> D<00:58:08.520> and<00:58:09.359> then<00:58:09.540> you 00:58:10.250 --> 00:58:10.260 align:start position:0% a domain with the Dash D and then you 00:58:10.260 --> 00:58:12.950 align:start position:0% a domain with the Dash D and then you can<00:58:10.440> pass<00:58:11.040> in<00:58:11.339> the<00:58:11.819> source<00:58:12.240> that<00:58:12.420> you<00:58:12.599> want<00:58:12.780> to 00:58:12.950 --> 00:58:12.960 align:start position:0% can pass in the source that you want to 00:58:12.960 --> 00:58:14.990 align:start position:0% can pass in the source that you want to look<00:58:13.260> for<00:58:13.500> something<00:58:13.859> so<00:58:14.160> you<00:58:14.339> would<00:58:14.460> just<00:58:14.700> use 00:58:14.990 --> 00:58:15.000 align:start position:0% look for something so you would just use 00:58:15.000 --> 00:58:17.930 align:start position:0% look for something so you would just use domain 00:58:17.930 --> 00:58:17.940 align:start position:0% domain 00:58:17.940 --> 00:58:20.870 align:start position:0% domain dot<00:58:18.839> com<00:58:18.900> and<00:58:19.500> then<00:58:19.619> let's<00:58:20.040> say<00:58:20.220> we<00:58:20.460> wanted<00:58:20.640> to 00:58:20.870 --> 00:58:20.880 align:start position:0% dot com and then let's say we wanted to 00:58:20.880 --> 00:58:23.809 align:start position:0% dot com and then let's say we wanted to use<00:58:21.000> Google<00:58:21.359> you<00:58:21.780> can<00:58:21.960> put<00:58:22.260> in<00:58:22.440> a<00:58:22.619> dash<00:58:22.800> B<00:58:23.040> and 00:58:23.809 --> 00:58:23.819 align:start position:0% use Google you can put in a dash B and 00:58:23.819 --> 00:58:26.510 align:start position:0% use Google you can put in a dash B and then<00:58:23.940> google.com<00:58:24.720> or<00:58:25.559> any<00:58:25.800> of<00:58:25.920> these<00:58:26.280> other 00:58:26.510 --> 00:58:26.520 align:start position:0% then google.com or any of these other 00:58:26.520 --> 00:58:29.809 align:start position:0% then google.com or any of these other options<00:58:27.420> down<00:58:27.720> here<00:58:27.960> for<00:58:28.319> the<00:58:28.800> source<00:58:29.339> and<00:58:29.640> it 00:58:29.809 --> 00:58:29.819 align:start position:0% options down here for the source and it 00:58:29.819 --> 00:58:32.870 align:start position:0% options down here for the source and it will<00:58:29.940> go<00:58:30.240> out<00:58:30.540> and<00:58:30.839> it<00:58:31.020> will<00:58:31.200> try<00:58:31.440> to<00:58:31.980> look<00:58:32.579> for 00:58:32.870 --> 00:58:32.880 align:start position:0% will go out and it will try to look for 00:58:32.880 --> 00:58:35.510 align:start position:0% will go out and it will try to look for domains<00:58:33.720> and<00:58:33.960> it<00:58:34.200> will<00:58:34.380> scrape<00:58:34.859> all<00:58:35.280> these 00:58:35.510 --> 00:58:35.520 align:start position:0% domains and it will scrape all these 00:58:35.520 --> 00:58:37.970 align:start position:0% domains and it will scrape all these search<00:58:35.700> engines<00:58:36.119> for<00:58:36.680> subdomains<00:58:37.680> email 00:58:37.970 --> 00:58:37.980 align:start position:0% search engines for subdomains email 00:58:37.980 --> 00:58:41.210 align:start position:0% search engines for subdomains email addresses<00:58:38.640> and<00:58:39.359> things<00:58:39.720> of<00:58:39.960> that<00:58:40.200> nature<00:58:40.559> so 00:58:41.210 --> 00:58:41.220 align:start position:0% addresses and things of that nature so 00:58:41.220 --> 00:58:44.030 align:start position:0% addresses and things of that nature so the<00:58:41.400> Harvester<00:58:41.819> is<00:58:42.540> a<00:58:42.839> penetration<00:58:43.380> testing 00:58:44.030 --> 00:58:44.040 align:start position:0% the Harvester is a penetration testing 00:58:44.040 --> 00:58:45.349 align:start position:0% the Harvester is a penetration testing tool<00:58:44.520> that<00:58:44.700> you're<00:58:44.819> going<00:58:44.940> to<00:58:45.059> hear<00:58:45.180> about 00:58:45.349 --> 00:58:45.359 align:start position:0% tool that you're going to hear about 00:58:45.359 --> 00:58:48.650 align:start position:0% tool that you're going to hear about from<00:58:46.200> time<00:58:46.559> to<00:58:46.740> time<00:58:46.980> and<00:58:47.640> it's<00:58:47.819> one<00:58:48.119> to<00:58:48.299> be 00:58:48.650 --> 00:58:48.660 align:start position:0% from time to time and it's one to be 00:58:48.660 --> 00:58:50.690 align:start position:0% from time to time and it's one to be aware<00:58:48.900> of<00:58:49.020> and<00:58:49.440> know<00:58:49.619> that<00:58:49.799> it<00:58:49.980> exists<00:58:50.280> you're 00:58:50.690 --> 00:58:50.700 align:start position:0% aware of and know that it exists you're 00:58:50.700 --> 00:58:52.190 align:start position:0% aware of and know that it exists you're probably<00:58:50.880> not<00:58:51.180> going<00:58:51.299> to<00:58:51.359> use<00:58:51.540> it<00:58:51.720> in<00:58:51.960> any 00:58:52.190 --> 00:58:52.200 align:start position:0% probably not going to use it in any 00:58:52.200 --> 00:58:56.630 align:start position:0% probably not going to use it in any pursuit<00:58:52.980> of<00:58:53.400> certifications<00:58:54.180> or<00:58:55.220> ctfs<00:58:56.220> but<00:58:56.460> it 00:58:56.630 --> 00:58:56.640 align:start position:0% pursuit of certifications or ctfs but it 00:58:56.640 --> 00:58:59.390 align:start position:0% pursuit of certifications or ctfs but it is<00:58:56.880> a<00:58:57.359> really<00:58:57.599> great<00:58:57.839> Recon<00:58:58.380> tool<00:58:58.740> and<00:58:58.980> one<00:58:59.220> you 00:58:59.390 --> 00:58:59.400 align:start position:0% is a really great Recon tool and one you 00:58:59.400 --> 00:59:02.089 align:start position:0% is a really great Recon tool and one you should<00:58:59.700> know<00:59:00.059> about<00:59:00.240> and<00:59:00.720> be<00:59:00.900> aware<00:59:01.200> of<00:59:01.319> to<00:59:01.920> be 00:59:02.089 --> 00:59:02.099 align:start position:0% should know about and be aware of to be 00:59:02.099 --> 00:59:04.849 align:start position:0% should know about and be aware of to be looking<00:59:02.460> at<00:59:02.819> cert<00:59:03.299> sh<00:59:03.540> I've<00:59:04.020> gone<00:59:04.200> ahead<00:59:04.500> and 00:59:04.849 --> 00:59:04.859 align:start position:0% looking at cert sh I've gone ahead and 00:59:04.859 --> 00:59:06.410 align:start position:0% looking at cert sh I've gone ahead and pulled<00:59:05.280> it<00:59:05.339> up<00:59:05.460> here<00:59:05.640> this<00:59:05.940> is<00:59:06.000> actually<00:59:06.180> the 00:59:06.410 --> 00:59:06.420 align:start position:0% pulled it up here this is actually the 00:59:06.420 --> 00:59:08.270 align:start position:0% pulled it up here this is actually the second<00:59:06.599> time<00:59:06.960> shooting<00:59:07.559> this<00:59:07.799> video<00:59:07.980> because 00:59:08.270 --> 00:59:08.280 align:start position:0% second time shooting this video because 00:59:08.280 --> 00:59:10.490 align:start position:0% second time shooting this video because I<00:59:08.520> forgot<00:59:08.760> to<00:59:08.940> press<00:59:09.480> record<00:59:09.720> the<00:59:10.140> first<00:59:10.319> time 00:59:10.490 --> 00:59:10.500 align:start position:0% I forgot to press record the first time 00:59:10.500 --> 00:59:12.650 align:start position:0% I forgot to press record the first time but<00:59:11.040> when<00:59:11.220> all<00:59:11.400> else<00:59:11.579> fails<00:59:12.299> when<00:59:12.540> you're 00:59:12.650 --> 00:59:12.660 align:start position:0% but when all else fails when you're 00:59:12.660 --> 00:59:15.289 align:start position:0% but when all else fails when you're looking<00:59:12.900> for<00:59:13.200> subdomains<00:59:14.040> the<00:59:14.280> assert.sh<00:59:14.940> is 00:59:15.289 --> 00:59:15.299 align:start position:0% looking for subdomains the assert.sh is 00:59:15.299 --> 00:59:17.030 align:start position:0% looking for subdomains the assert.sh is going<00:59:15.480> to<00:59:15.540> be<00:59:15.599> a<00:59:15.960> great<00:59:16.079> place<00:59:16.319> to<00:59:16.500> come<00:59:16.619> it's 00:59:17.030 --> 00:59:17.040 align:start position:0% going to be a great place to come it's 00:59:17.040 --> 00:59:18.230 align:start position:0% going to be a great place to come it's going<00:59:17.220> to<00:59:17.280> give<00:59:17.400> you<00:59:17.460> this<00:59:17.640> sort<00:59:17.760> of<00:59:17.880> education 00:59:18.230 --> 00:59:18.240 align:start position:0% going to give you this sort of education 00:59:18.240 --> 00:59:21.829 align:start position:0% going to give you this sort of education tickets<00:59:19.140> for<00:59:19.920> the<00:59:20.520> domain<00:59:21.180> that<00:59:21.540> you<00:59:21.660> are 00:59:21.829 --> 00:59:21.839 align:start position:0% tickets for the domain that you are 00:59:21.839 --> 00:59:23.390 align:start position:0% tickets for the domain that you are looking<00:59:22.079> at<00:59:22.260> so<00:59:22.500> we'll<00:59:22.619> go<00:59:22.740> ahead<00:59:22.920> and<00:59:23.160> open 00:59:23.390 --> 00:59:23.400 align:start position:0% looking at so we'll go ahead and open 00:59:23.400 --> 00:59:24.530 align:start position:0% looking at so we'll go ahead and open this<00:59:23.640> up<00:59:23.760> and<00:59:24.000> I'm<00:59:24.059> going<00:59:24.180> to<00:59:24.240> type<00:59:24.359> in 00:59:24.530 --> 00:59:24.540 align:start position:0% this up and I'm going to type in 00:59:24.540 --> 00:59:28.010 align:start position:0% this up and I'm going to type in tesla.com<00:59:25.380> and<00:59:25.980> we<00:59:26.339> can<00:59:26.460> hit<00:59:27.000> search<00:59:27.480> and<00:59:27.780> look 00:59:28.010 --> 00:59:28.020 align:start position:0% tesla.com and we can hit search and look 00:59:28.020 --> 00:59:30.289 align:start position:0% tesla.com and we can hit search and look at<00:59:28.200> the<00:59:28.500> subdomains<00:59:29.220> that<00:59:29.339> it<00:59:29.520> pulls<00:59:29.760> down<00:59:29.880> and 00:59:30.289 --> 00:59:30.299 align:start position:0% at the subdomains that it pulls down and 00:59:30.299 --> 00:59:33.049 align:start position:0% at the subdomains that it pulls down and you're<00:59:30.480> interested<00:59:30.960> in<00:59:31.740> this<00:59:32.160> middle<00:59:32.460> row 00:59:33.049 --> 00:59:33.059 align:start position:0% you're interested in this middle row 00:59:33.059 --> 00:59:34.910 align:start position:0% you're interested in this middle row right<00:59:33.480> here<00:59:33.720> because<00:59:34.020> if<00:59:34.319> you<00:59:34.440> look<00:59:34.619> at<00:59:34.740> this 00:59:34.910 --> 00:59:34.920 align:start position:0% right here because if you look at this 00:59:34.920 --> 00:59:38.270 align:start position:0% right here because if you look at this closely<00:59:35.460> you<00:59:36.299> can<00:59:36.420> see<00:59:36.720> these<00:59:37.440> subdomains 00:59:38.270 --> 00:59:38.280 align:start position:0% closely you can see these subdomains 00:59:38.280 --> 00:59:42.109 align:start position:0% closely you can see these subdomains right<00:59:38.940> here<00:59:39.240> for<00:59:40.220> tesla.com<00:59:41.220> and<00:59:41.760> so<00:59:41.940> this 00:59:42.109 --> 00:59:42.119 align:start position:0% right here for tesla.com and so this 00:59:42.119 --> 00:59:44.809 align:start position:0% right here for tesla.com and so this will<00:59:42.240> give<00:59:42.420> you<00:59:42.599> a<00:59:43.200> bunch<00:59:43.559> of<00:59:43.920> subdomains<00:59:44.700> for 00:59:44.809 --> 00:59:44.819 align:start position:0% will give you a bunch of subdomains for 00:59:44.819 --> 00:59:47.510 align:start position:0% will give you a bunch of subdomains for you<00:59:44.940> to<00:59:45.059> go<00:59:45.299> out<00:59:45.420> and<00:59:45.599> look<00:59:45.780> and<00:59:46.260> test<00:59:46.619> for<00:59:47.040> bugs 00:59:47.510 --> 00:59:47.520 align:start position:0% you to go out and look and test for bugs 00:59:47.520 --> 00:59:49.010 align:start position:0% you to go out and look and test for bugs and<00:59:47.700> see<00:59:47.819> if<00:59:47.940> there's<00:59:48.059> any<00:59:48.240> information<00:59:48.480> out 00:59:49.010 --> 00:59:49.020 align:start position:0% and see if there's any information out 00:59:49.020 --> 00:59:51.770 align:start position:0% and see if there's any information out there<00:59:49.140> or<00:59:49.619> anything<00:59:50.280> you<00:59:50.880> want<00:59:51.180> to<00:59:51.359> attest 00:59:51.770 --> 00:59:51.780 align:start position:0% there or anything you want to attest 00:59:51.780 --> 00:59:53.990 align:start position:0% there or anything you want to attest against<00:59:52.040> when<00:59:53.040> I<00:59:53.280> look<00:59:53.460> at<00:59:53.579> something<00:59:53.760> like 00:59:53.990 --> 00:59:54.000 align:start position:0% against when I look at something like 00:59:54.000 --> 00:59:55.490 align:start position:0% against when I look at something like this<00:59:54.180> one<00:59:54.540> of<00:59:54.660> the<00:59:54.720> first<00:59:54.839> things<00:59:55.020> when<00:59:55.319> you 00:59:55.490 --> 00:59:55.500 align:start position:0% this one of the first things when you 00:59:55.500 --> 00:59:58.010 align:start position:0% this one of the first things when you have<00:59:55.619> so<00:59:55.920> many<00:59:56.040> subdomains<00:59:56.760> is<00:59:57.240> to<00:59:57.540> see<00:59:57.839> which 00:59:58.010 --> 00:59:58.020 align:start position:0% have so many subdomains is to see which 00:59:58.020 --> 01:00:00.470 align:start position:0% have so many subdomains is to see which ones<00:59:58.319> look<00:59:58.559> specifically<00:59:59.160> interesting<00:59:59.819> to 01:00:00.470 --> 01:00:00.480 align:start position:0% ones look specifically interesting to 01:00:00.480 --> 01:00:02.870 align:start position:0% ones look specifically interesting to you<01:00:00.900> and<01:00:01.559> then<01:00:01.740> you<01:00:02.220> can<01:00:02.280> go<01:00:02.400> and<01:00:02.520> check<01:00:02.700> those 01:00:02.870 --> 01:00:02.880 align:start position:0% you and then you can go and check those 01:00:02.880 --> 01:00:05.569 align:start position:0% you and then you can go and check those but<01:00:03.180> always<01:00:03.359> make<01:00:03.780> sure<01:00:04.079> that<01:00:04.799> they<01:00:05.099> are<01:00:05.339> in 01:00:05.569 --> 01:00:05.579 align:start position:0% but always make sure that they are in 01:00:05.579 --> 01:00:07.370 align:start position:0% but always make sure that they are in scope<01:00:05.819> so<01:00:06.059> you'd<01:00:06.299> want<01:00:06.420> to<01:00:06.540> make<01:00:06.660> sure<01:00:06.900> that 01:00:07.370 --> 01:00:07.380 align:start position:0% scope so you'd want to make sure that 01:00:07.380 --> 01:00:10.609 align:start position:0% scope so you'd want to make sure that this<01:00:07.799> assets<01:00:08.640> first<01:00:09.119> of<01:00:09.299> all<01:00:09.359> is<01:00:09.780> owned<01:00:10.319> by 01:00:10.609 --> 01:00:10.619 align:start position:0% this assets first of all is owned by 01:00:10.619 --> 01:00:12.530 align:start position:0% this assets first of all is owned by tesla.com<01:00:11.339> and<01:00:11.880> then<01:00:12.000> you'd<01:00:12.180> want<01:00:12.299> to<01:00:12.420> make 01:00:12.530 --> 01:00:12.540 align:start position:0% tesla.com and then you'd want to make 01:00:12.540 --> 01:00:15.770 align:start position:0% tesla.com and then you'd want to make sure<01:00:12.720> that<01:00:13.079> it's<01:00:13.319> in<01:00:13.680> scope<01:00:14.040> and<01:00:14.400> second<01:00:14.760> a<01:00:15.299> tip 01:00:15.770 --> 01:00:15.780 align:start position:0% sure that it's in scope and second a tip 01:00:15.780 --> 01:00:18.710 align:start position:0% sure that it's in scope and second a tip is<01:00:16.260> to<01:00:16.500> look<01:00:16.799> for<01:00:17.160> the<01:00:17.520> dev<01:00:17.819> of<01:00:18.299> typically 01:00:18.710 --> 01:00:18.720 align:start position:0% is to look for the dev of typically 01:00:18.720 --> 01:00:21.470 align:start position:0% is to look for the dev of typically these<01:00:19.260> Dev<01:00:19.500> sites<01:00:20.280> and<01:00:20.460> these<01:00:20.579> Dev<01:00:20.760> subdomains 01:00:21.470 --> 01:00:21.480 align:start position:0% these Dev sites and these Dev subdomains 01:00:21.480 --> 01:00:23.870 align:start position:0% these Dev sites and these Dev subdomains right<01:00:21.599> here<01:00:21.839> are<01:00:22.500> going<01:00:22.740> to<01:00:22.920> be<01:00:23.400> hosting 01:00:23.870 --> 01:00:23.880 align:start position:0% right here are going to be hosting 01:00:23.880 --> 01:00:26.569 align:start position:0% right here are going to be hosting information<01:00:24.200> or<01:00:25.200> new<01:00:25.440> software<01:00:25.859> or<01:00:26.099> new<01:00:26.280> code 01:00:26.569 --> 01:00:26.579 align:start position:0% information or new software or new code 01:00:26.579 --> 01:00:29.990 align:start position:0% information or new software or new code before<01:00:27.299> it<01:00:27.780> goes<01:00:28.079> live<01:00:28.260> on<01:00:28.619> the<01:00:28.859> actual<01:00:29.220> main 01:00:29.990 --> 01:00:30.000 align:start position:0% before it goes live on the actual main 01:00:30.000 --> 01:00:32.150 align:start position:0% before it goes live on the actual main domain<01:00:30.660> and<01:00:30.960> so<01:00:31.079> these<01:00:31.380> devs<01:00:31.740> are<01:00:31.980> always 01:00:32.150 --> 01:00:32.160 align:start position:0% domain and so these devs are always 01:00:32.160 --> 01:00:34.789 align:start position:0% domain and so these devs are always something<01:00:32.460> good<01:00:32.819> to<01:00:33.059> look<01:00:33.900> at<01:00:34.140> another<01:00:34.500> one 01:00:34.789 --> 01:00:34.799 align:start position:0% something good to look at another one 01:00:34.799 --> 01:00:36.289 align:start position:0% something good to look at another one that's<01:00:35.040> good<01:00:35.339> to<01:00:35.400> look<01:00:35.520> at<01:00:35.640> is<01:00:35.760> look<01:00:36.000> at<01:00:36.119> like 01:00:36.289 --> 01:00:36.299 align:start position:0% that's good to look at is look at like 01:00:36.299 --> 01:00:38.450 align:start position:0% that's good to look at is look at like admin<01:00:36.780> portals<01:00:37.260> and<01:00:37.440> see<01:00:37.619> if<01:00:37.799> you<01:00:37.980> can<01:00:38.099> get 01:00:38.450 --> 01:00:38.460 align:start position:0% admin portals and see if you can get 01:00:38.460 --> 01:00:40.970 align:start position:0% admin portals and see if you can get into<01:00:38.700> any<01:00:39.240> of<01:00:39.359> those<01:00:39.540> or<01:00:40.319> fuzz<01:00:40.799> for 01:00:40.970 --> 01:00:40.980 align:start position:0% into any of those or fuzz for 01:00:40.980 --> 01:00:42.770 align:start position:0% into any of those or fuzz for directories<01:00:41.700> because<01:00:42.119> there<01:00:42.480> might<01:00:42.660> be 01:00:42.770 --> 01:00:42.780 align:start position:0% directories because there might be 01:00:42.780 --> 01:00:44.630 align:start position:0% directories because there might be something<01:00:43.200> there<01:00:43.559> that<01:00:43.980> you<01:00:44.280> might<01:00:44.460> need 01:00:44.630 --> 01:00:44.640 align:start position:0% something there that you might need 01:00:44.640 --> 01:00:47.210 align:start position:0% something there that you might need authentic<01:00:45.240> authentication<01:00:45.960> for<01:00:46.380> in<01:00:46.859> order<01:00:47.040> to 01:00:47.210 --> 01:00:47.220 align:start position:0% authentic authentication for in order to 01:00:47.220 --> 01:00:49.370 align:start position:0% authentic authentication for in order to see<01:00:47.400> but<01:00:47.819> you<01:00:48.059> can<01:00:48.180> access<01:00:48.359> it<01:00:48.660> without<01:00:48.900> being 01:00:49.370 --> 01:00:49.380 align:start position:0% see but you can access it without being 01:00:49.380 --> 01:00:51.710 align:start position:0% see but you can access it without being authenticated<01:00:50.280> so<01:00:50.640> the<01:00:50.819> devs<01:00:51.240> the<01:00:51.359> admins 01:00:51.710 --> 01:00:51.720 align:start position:0% authenticated so the devs the admins 01:00:51.720 --> 01:00:54.170 align:start position:0% authenticated so the devs the admins Pages<01:00:52.079> like<01:00:52.319> those<01:00:52.500> this<01:00:53.280> API<01:00:53.760> would<01:00:54.000> be 01:00:54.170 --> 01:00:54.180 align:start position:0% Pages like those this API would be 01:00:54.180 --> 01:00:56.569 align:start position:0% Pages like those this API would be interesting<01:00:54.599> to<01:00:54.960> look<01:00:55.319> at<01:00:55.500> and<01:00:56.099> so<01:00:56.280> you<01:00:56.520> can 01:00:56.569 --> 01:00:56.579 align:start position:0% interesting to look at and so you can 01:00:56.579 --> 01:00:58.490 align:start position:0% interesting to look at and so you can come<01:00:56.760> in<01:00:56.940> and<01:00:57.240> look<01:00:57.420> at<01:00:57.540> all<01:00:57.780> these<01:00:57.960> subdomains 01:00:58.490 --> 01:00:58.500 align:start position:0% come in and look at all these subdomains 01:00:58.500 --> 01:01:00.349 align:start position:0% come in and look at all these subdomains if<01:00:58.740> amass<01:00:59.160> and<01:00:59.339> sublister<01:00:59.880> are<01:01:00.000> not<01:01:00.119> pulling 01:01:00.349 --> 01:01:00.359 align:start position:0% if amass and sublister are not pulling 01:01:00.359 --> 01:01:02.329 align:start position:0% if amass and sublister are not pulling back<01:01:00.480> enough<01:01:00.720> subdomains<01:01:01.559> for<01:01:01.740> you<01:01:01.859> you<01:01:02.220> can 01:01:02.329 --> 01:01:02.339 align:start position:0% back enough subdomains for you you can 01:01:02.339 --> 01:01:06.049 align:start position:0% back enough subdomains for you you can always<01:01:02.460> come<01:01:02.760> to<01:01:03.380> srt.sh<01:01:04.380> and<01:01:05.280> check<01:01:05.640> this<01:01:05.880> out 01:01:06.049 --> 01:01:06.059 align:start position:0% always come to srt.sh and check this out 01:01:06.059 --> 01:01:07.849 align:start position:0% always come to srt.sh and check this out so<01:01:06.420> in<01:01:06.599> this<01:01:06.720> video<01:01:06.839> what<01:01:07.380> I<01:01:07.559> think<01:01:07.680> we're 01:01:07.849 --> 01:01:07.859 align:start position:0% so in this video what I think we're 01:01:07.859 --> 01:01:09.349 align:start position:0% so in this video what I think we're going<01:01:08.040> to<01:01:08.160> do<01:01:08.220> is<01:01:08.400> I'm<01:01:08.579> going<01:01:08.700> to<01:01:08.760> show<01:01:08.940> you<01:01:09.059> how 01:01:09.349 --> 01:01:09.359 align:start position:0% going to do is I'm going to show you how 01:01:09.359 --> 01:01:11.569 align:start position:0% going to do is I'm going to show you how to<01:01:09.420> grab<01:01:09.960> all<01:01:10.619> of<01:01:10.740> the<01:01:10.980> different<01:01:11.099> possible 01:01:11.569 --> 01:01:11.579 align:start position:0% to grab all of the different possible 01:01:11.579 --> 01:01:14.270 align:start position:0% to grab all of the different possible URL<01:01:12.240> targets<01:01:12.720> for<01:01:12.900> you<01:01:13.020> within<01:01:13.380> a<01:01:13.559> bug<01:01:13.799> Bounty 01:01:14.270 --> 01:01:14.280 align:start position:0% URL targets for you within a bug Bounty 01:01:14.280 --> 01:01:16.069 align:start position:0% URL targets for you within a bug Bounty program<01:01:14.460> and<01:01:15.059> then<01:01:15.180> we're<01:01:15.299> going<01:01:15.480> to<01:01:15.599> start<01:01:15.780> to 01:01:16.069 --> 01:01:16.079 align:start position:0% program and then we're going to start to 01:01:16.079 --> 01:01:18.170 align:start position:0% program and then we're going to start to narrow<01:01:16.559> it<01:01:16.680> down<01:01:16.859> to<01:01:17.099> the<01:01:17.280> URLs<01:01:17.640> that<01:01:17.760> are 01:01:18.170 --> 01:01:18.180 align:start position:0% narrow it down to the URLs that are 01:01:18.180 --> 01:01:19.789 align:start position:0% narrow it down to the URLs that are actually<01:01:18.420> responsive<01:01:18.900> and<01:01:19.319> then<01:01:19.440> the<01:01:19.559> ones 01:01:19.789 --> 01:01:19.799 align:start position:0% actually responsive and then the ones 01:01:19.799 --> 01:01:21.890 align:start position:0% actually responsive and then the ones that<01:01:19.980> I<01:01:20.339> think<01:01:20.460> will<01:01:20.640> be<01:01:20.819> helpful<01:01:21.119> for<01:01:21.599> you<01:01:21.720> to 01:01:21.890 --> 01:01:21.900 align:start position:0% that I think will be helpful for you to 01:01:21.900 --> 01:01:23.990 align:start position:0% that I think will be helpful for you to Target<01:01:22.200> as<01:01:22.740> a<01:01:23.099> beginner<01:01:23.400> and<01:01:23.640> so<01:01:23.760> I'm<01:01:23.880> going<01:01:23.940> to 01:01:23.990 --> 01:01:24.000 align:start position:0% Target as a beginner and so I'm going to 01:01:24.000 --> 01:01:25.910 align:start position:0% Target as a beginner and so I'm going to show<01:01:24.119> you<01:01:24.180> how<01:01:24.299> to<01:01:24.420> find<01:01:24.540> the<01:01:25.020> most<01:01:25.380> obscure 01:01:25.910 --> 01:01:25.920 align:start position:0% show you how to find the most obscure 01:01:25.920 --> 01:01:28.430 align:start position:0% show you how to find the most obscure URLs<01:01:26.640> within<01:01:27.059> a<01:01:27.180> bug<01:01:27.299> Bounty<01:01:27.720> programs<01:01:28.140> for 01:01:28.430 --> 01:01:28.440 align:start position:0% URLs within a bug Bounty programs for 01:01:28.440 --> 01:01:30.230 align:start position:0% URLs within a bug Bounty programs for you<01:01:28.619> to<01:01:28.859> a<01:01:28.980> Target<01:01:29.160> but<01:01:29.579> always<01:01:29.760> make<01:01:29.940> sure<01:01:30.119> to 01:01:30.230 --> 01:01:30.240 align:start position:0% you to a Target but always make sure to 01:01:30.240 --> 01:01:32.569 align:start position:0% you to a Target but always make sure to remember<01:01:30.359> that<01:01:30.660> these<01:01:30.960> URLs<01:01:31.500> are<01:01:31.980> in<01:01:32.220> scope 01:01:32.569 --> 01:01:32.579 align:start position:0% remember that these URLs are in scope 01:01:32.579 --> 01:01:33.890 align:start position:0% remember that these URLs are in scope that's<01:01:32.760> going<01:01:32.940> to<01:01:33.000> be<01:01:33.059> really<01:01:33.240> important<01:01:33.660> so 01:01:33.890 --> 01:01:33.900 align:start position:0% that's going to be really important so 01:01:33.900 --> 01:01:35.150 align:start position:0% that's going to be really important so always<01:01:34.079> check<01:01:34.440> that<01:01:34.619> because<01:01:34.799> sometimes 01:01:35.150 --> 01:01:35.160 align:start position:0% always check that because sometimes 01:01:35.160 --> 01:01:37.250 align:start position:0% always check that because sometimes you'll<01:01:35.400> see<01:01:35.520> URLs<01:01:36.059> that<01:01:36.359> maybe<01:01:36.540> are<01:01:36.839> several 01:01:37.250 --> 01:01:37.260 align:start position:0% you'll see URLs that maybe are several 01:01:37.260 --> 01:01:38.870 align:start position:0% you'll see URLs that maybe are several years<01:01:37.440> old<01:01:37.619> and<01:01:38.040> a<01:01:38.220> specific<01:01:38.400> bug<01:01:38.579> bunny 01:01:38.870 --> 01:01:38.880 align:start position:0% years old and a specific bug bunny 01:01:38.880 --> 01:01:41.450 align:start position:0% years old and a specific bug bunny program<01:01:39.299> has<01:01:39.960> forgotten<01:01:40.500> to<01:01:40.619> remove<01:01:40.980> them<01:01:41.280> and 01:01:41.450 --> 01:01:41.460 align:start position:0% program has forgotten to remove them and 01:01:41.460 --> 01:01:42.349 align:start position:0% program has forgotten to remove them and you're<01:01:41.579> going<01:01:41.700> to<01:01:41.760> think<01:01:41.880> this<01:01:42.000> is<01:01:42.119> a<01:01:42.299> really 01:01:42.349 --> 01:01:42.359 align:start position:0% you're going to think this is a really 01:01:42.359 --> 01:01:44.030 align:start position:0% you're going to think this is a really great<01:01:42.540> Target<01:01:42.720> but<01:01:43.079> it<01:01:43.200> will<01:01:43.319> end<01:01:43.500> up<01:01:43.680> falling 01:01:44.030 --> 01:01:44.040 align:start position:0% great Target but it will end up falling 01:01:44.040 --> 01:01:46.609 align:start position:0% great Target but it will end up falling into<01:01:44.339> the<01:01:44.819> category<01:01:45.119> of<01:01:45.299> out<01:01:45.540> of<01:01:45.720> scope<01:01:45.960> so 01:01:46.609 --> 01:01:46.619 align:start position:0% into the category of out of scope so 01:01:46.619 --> 01:01:49.130 align:start position:0% into the category of out of scope so make<01:01:47.040> sure<01:01:47.220> as<01:01:47.640> you<01:01:47.940> go<01:01:48.240> through<01:01:48.420> your<01:01:48.780> recon 01:01:49.130 --> 01:01:49.140 align:start position:0% make sure as you go through your recon 01:01:49.140 --> 01:01:51.289 align:start position:0% make sure as you go through your recon phase<01:01:49.440> to<01:01:49.619> only<01:01:49.859> target<01:01:50.040> URLs<01:01:50.700> that<01:01:51.059> are<01:01:51.180> in 01:01:51.289 --> 01:01:51.299 align:start position:0% phase to only target URLs that are in 01:01:51.299 --> 01:01:52.910 align:start position:0% phase to only target URLs that are in the<01:01:51.359> bug<01:01:51.480> binding<01:01:51.900> scope<01:01:52.079> this<01:01:52.440> is<01:01:52.619> something 01:01:52.910 --> 01:01:52.920 align:start position:0% the bug binding scope this is something 01:01:52.920 --> 01:01:54.770 align:start position:0% the bug binding scope this is something that<01:01:53.220> I<01:01:53.339> really<01:01:53.460> struggled<01:01:53.819> with<01:01:54.000> in<01:01:54.540> the 01:01:54.770 --> 01:01:54.780 align:start position:0% that I really struggled with in the 01:01:54.780 --> 01:01:56.750 align:start position:0% that I really struggled with in the beginning<01:01:54.960> I<01:01:55.380> would<01:01:55.559> end<01:01:55.799> up<01:01:55.980> out<01:01:56.160> of<01:01:56.339> scope<01:01:56.520> so 01:01:56.750 --> 01:01:56.760 align:start position:0% beginning I would end up out of scope so 01:01:56.760 --> 01:01:58.549 align:start position:0% beginning I would end up out of scope so you<01:01:56.940> don't<01:01:57.119> want<01:01:57.299> to<01:01:57.540> do<01:01:57.900> that<01:01:58.079> all<01:01:58.380> right 01:01:58.549 --> 01:01:58.559 align:start position:0% you don't want to do that all right 01:01:58.559 --> 01:02:01.069 align:start position:0% you don't want to do that all right there<01:01:58.920> is<01:01:59.099> something<01:01:59.520> called<01:01:59.940> the<01:02:00.540> Wayback 01:02:01.069 --> 01:02:01.079 align:start position:0% there is something called the Wayback 01:02:01.079 --> 01:02:03.589 align:start position:0% there is something called the Wayback machine<01:02:01.440> which<01:02:01.920> is<01:02:02.040> really<01:02:02.520> cool<01:02:02.760> and<01:02:03.480> we're 01:02:03.589 --> 01:02:03.599 align:start position:0% machine which is really cool and we're 01:02:03.599 --> 01:02:05.750 align:start position:0% machine which is really cool and we're going<01:02:03.780> to<01:02:03.900> be<01:02:03.960> utilizing<01:02:04.440> this<01:02:04.680> and<01:02:05.040> thanks<01:02:05.400> to 01:02:05.750 --> 01:02:05.760 align:start position:0% going to be utilizing this and thanks to 01:02:05.760 --> 01:02:08.690 align:start position:0% going to be utilizing this and thanks to Tom<01:02:06.180> nom<01:02:06.540> nom<01:02:06.780> for<01:02:07.260> making<01:02:07.440> a<01:02:07.859> way<01:02:08.099> back<01:02:08.280> tool 01:02:08.690 --> 01:02:08.700 align:start position:0% Tom nom nom for making a way back tool 01:02:08.700 --> 01:02:10.430 align:start position:0% Tom nom nom for making a way back tool that<01:02:08.880> is<01:02:09.059> really<01:02:09.359> going<01:02:09.599> to<01:02:09.780> save<01:02:10.079> us<01:02:10.260> some 01:02:10.430 --> 01:02:10.440 align:start position:0% that is really going to save us some 01:02:10.440 --> 01:02:12.230 align:start position:0% that is really going to save us some time<01:02:10.680> as<01:02:10.980> well<01:02:11.099> as<01:02:11.220> a<01:02:11.400> couple<01:02:11.520> of<01:02:11.640> other<01:02:11.819> tools 01:02:12.230 --> 01:02:12.240 align:start position:0% time as well as a couple of other tools 01:02:12.240 --> 01:02:14.690 align:start position:0% time as well as a couple of other tools so<01:02:12.780> if<01:02:13.020> you<01:02:13.140> want<01:02:13.380> to<01:02:13.500> check<01:02:13.859> this<01:02:14.040> out<01:02:14.280> online 01:02:14.690 --> 01:02:14.700 align:start position:0% so if you want to check this out online 01:02:14.700 --> 01:02:17.510 align:start position:0% so if you want to check this out online you<01:02:15.240> can<01:02:15.359> type<01:02:15.540> way<01:02:15.900> back<01:02:16.140> into<01:02:16.559> Google<01:02:17.099> and 01:02:17.510 --> 01:02:17.520 align:start position:0% you can type way back into Google and 01:02:17.520 --> 01:02:19.490 align:start position:0% you can type way back into Google and you'll<01:02:17.700> be<01:02:18.180> brought<01:02:18.480> to<01:02:18.599> the<01:02:18.839> Wayback<01:02:19.200> machine 01:02:19.490 --> 01:02:19.500 align:start position:0% you'll be brought to the Wayback machine 01:02:19.500 --> 01:02:21.650 align:start position:0% you'll be brought to the Wayback machine and<01:02:20.040> we<01:02:20.280> can<01:02:20.339> come<01:02:20.520> right<01:02:20.760> in<01:02:20.940> here<01:02:21.059> and<01:02:21.480> it 01:02:21.650 --> 01:02:21.660 align:start position:0% and we can come right in here and it 01:02:21.660 --> 01:02:23.750 align:start position:0% and we can come right in here and it tells<01:02:21.960> us<01:02:22.079> at<01:02:22.380> the<01:02:22.500> top<01:02:22.619> that<01:02:23.040> it<01:02:23.220> has<01:02:23.400> saved 01:02:23.750 --> 01:02:23.760 align:start position:0% tells us at the top that it has saved 01:02:23.760 --> 01:02:27.770 align:start position:0% tells us at the top that it has saved more<01:02:24.119> than<01:02:24.740> 737<01:02:25.740> million<01:02:26.520> web<01:02:26.819> pages<01:02:27.119> and 01:02:27.770 --> 01:02:27.780 align:start position:0% more than 737 million web pages and 01:02:27.780 --> 01:02:29.150 align:start position:0% more than 737 million web pages and let's<01:02:27.900> go<01:02:28.079> ahead<01:02:28.260> and<01:02:28.500> check<01:02:28.680> out<01:02:28.859> what<01:02:29.040> this 01:02:29.150 --> 01:02:29.160 align:start position:0% let's go ahead and check out what this 01:02:29.160 --> 01:02:31.549 align:start position:0% let's go ahead and check out what this does<01:02:29.280> so<01:02:29.460> we<01:02:29.579> can<01:02:29.700> type<01:02:29.819> in<01:02:30.000> yahoo.com<01:02:30.960> and 01:02:31.549 --> 01:02:31.559 align:start position:0% does so we can type in yahoo.com and 01:02:31.559 --> 01:02:33.710 align:start position:0% does so we can type in yahoo.com and it's<01:02:31.740> going<01:02:31.920> to<01:02:31.980> give<01:02:32.160> us<01:02:32.339> all<01:02:33.000> of<01:02:33.299> the 01:02:33.710 --> 01:02:33.720 align:start position:0% it's going to give us all of the 01:02:33.720 --> 01:02:35.930 align:start position:0% it's going to give us all of the screenshots<01:02:34.319> that<01:02:34.799> it<01:02:34.920> has<01:02:35.099> taken<01:02:35.579> of 01:02:35.930 --> 01:02:35.940 align:start position:0% screenshots that it has taken of 01:02:35.940 --> 01:02:39.730 align:start position:0% screenshots that it has taken of yahoo.com<01:02:36.839> from<01:02:37.740> October<01:02:38.640> 17 01:02:39.730 --> 01:02:39.740 align:start position:0% yahoo.com from October 17 01:02:39.740 --> 01:02:42.109 align:start position:0% yahoo.com from October 17 1996<01:02:40.740> so<01:02:41.099> this<01:02:41.280> is<01:02:41.339> why<01:02:41.520> it's<01:02:41.640> called<01:02:41.880> the 01:02:42.109 --> 01:02:42.119 align:start position:0% 1996 so this is why it's called the 01:02:42.119 --> 01:02:44.569 align:start position:0% 1996 so this is why it's called the Wayback<01:02:42.480> machine<01:02:42.780> and<01:02:43.380> it<01:02:43.500> doesn't<01:02:43.680> just<01:02:44.099> take 01:02:44.569 --> 01:02:44.579 align:start position:0% Wayback machine and it doesn't just take 01:02:44.579 --> 01:02:46.309 align:start position:0% Wayback machine and it doesn't just take screenshots<01:02:45.059> it'll<01:02:45.420> actually<01:02:45.599> store<01:02:45.960> the 01:02:46.309 --> 01:02:46.319 align:start position:0% screenshots it'll actually store the 01:02:46.319 --> 01:02:48.410 align:start position:0% screenshots it'll actually store the URLs<01:02:46.920> and<01:02:47.339> you<01:02:47.460> can<01:02:47.520> go<01:02:47.700> back<01:02:47.819> and<01:02:48.059> check<01:02:48.240> out 01:02:48.410 --> 01:02:48.420 align:start position:0% URLs and you can go back and check out 01:02:48.420 --> 01:02:50.390 align:start position:0% URLs and you can go back and check out the<01:02:48.660> timestamps<01:02:49.140> and<01:02:49.260> it'll<01:02:49.440> show<01:02:49.680> you<01:02:49.799> what 01:02:50.390 --> 01:02:50.400 align:start position:0% the timestamps and it'll show you what 01:02:50.400 --> 01:02:52.430 align:start position:0% the timestamps and it'll show you what the<01:02:50.640> web<01:02:50.819> page<01:02:51.119> actually<01:02:51.540> looked<01:02:52.020> like<01:02:52.079> at 01:02:52.430 --> 01:02:52.440 align:start position:0% the web page actually looked like at 01:02:52.440 --> 01:02:54.530 align:start position:0% the web page actually looked like at that<01:02:52.559> time<01:02:52.740> so<01:02:52.980> if<01:02:53.099> we<01:02:53.280> click<01:02:53.579> back<01:02:53.760> here<01:02:54.000> to 01:02:54.530 --> 01:02:54.540 align:start position:0% that time so if we click back here to 01:02:54.540 --> 01:02:57.170 align:start position:0% that time so if we click back here to the<01:02:54.839> year<01:02:55.020> 2000<01:02:55.680> and<01:02:56.280> let's<01:02:56.400> say<01:02:56.579> we<01:02:56.819> want<01:02:57.000> to 01:02:57.170 --> 01:02:57.180 align:start position:0% the year 2000 and let's say we want to 01:02:57.180 --> 01:03:00.770 align:start position:0% the year 2000 and let's say we want to open<01:02:57.480> up<01:02:57.720> a<01:02:57.960> February<01:02:58.319> 29th<01:02:59.040> 2000<01:02:59.579> we<01:03:00.299> can<01:03:00.599> do 01:03:00.770 --> 01:03:00.780 align:start position:0% open up a February 29th 2000 we can do 01:03:00.780 --> 01:03:03.049 align:start position:0% open up a February 29th 2000 we can do this<01:03:00.900> so<01:03:01.140> we'll<01:03:01.319> right<01:03:01.500> click<01:03:01.799> say<01:03:02.099> open<01:03:02.460> in<01:03:02.819> a 01:03:03.049 --> 01:03:03.059 align:start position:0% this so we'll right click say open in a 01:03:03.059 --> 01:03:04.849 align:start position:0% this so we'll right click say open in a new<01:03:03.240> tab<01:03:03.540> and<01:03:03.960> it's<01:03:04.079> going<01:03:04.260> to<01:03:04.319> render<01:03:04.559> what 01:03:04.849 --> 01:03:04.859 align:start position:0% new tab and it's going to render what 01:03:04.859 --> 01:03:07.190 align:start position:0% new tab and it's going to render what that<01:03:05.040> page<01:03:05.280> looked<01:03:05.760> like<01:03:05.880> for<01:03:06.119> us<01:03:06.299> from<01:03:06.780> its 01:03:07.190 --> 01:03:07.200 align:start position:0% that page looked like for us from its 01:03:07.200 --> 01:03:10.010 align:start position:0% that page looked like for us from its archive<01:03:07.619> which<01:03:08.160> is<01:03:08.400> pretty<01:03:08.700> cool<01:03:08.880> and<01:03:09.480> so<01:03:09.660> this 01:03:10.010 --> 01:03:10.020 align:start position:0% archive which is pretty cool and so this 01:03:10.020 --> 01:03:12.349 align:start position:0% archive which is pretty cool and so this is<01:03:10.200> what<01:03:10.559> the<01:03:10.740> main<01:03:10.920> page<01:03:11.220> looks<01:03:11.640> like<01:03:11.760> and 01:03:12.349 --> 01:03:12.359 align:start position:0% is what the main page looks like and 01:03:12.359 --> 01:03:14.750 align:start position:0% is what the main page looks like and some<01:03:12.599> of<01:03:12.720> the<01:03:12.720> HTML<01:03:13.319> might<01:03:13.799> not<01:03:13.980> render<01:03:14.280> quite 01:03:14.750 --> 01:03:14.760 align:start position:0% some of the HTML might not render quite 01:03:14.760 --> 01:03:16.730 align:start position:0% some of the HTML might not render quite right<01:03:15.119> but<01:03:15.480> that's<01:03:15.660> okay<01:03:15.839> so<01:03:16.319> we<01:03:16.440> just<01:03:16.619> really 01:03:16.730 --> 01:03:16.740 align:start position:0% right but that's okay so we just really 01:03:16.740 --> 01:03:18.710 align:start position:0% right but that's okay so we just really want<01:03:16.920> to<01:03:17.040> grab<01:03:17.099> the<01:03:17.280> URL<01:03:17.640> and<01:03:18.180> a<01:03:18.420> lot<01:03:18.480> of<01:03:18.599> the 01:03:18.710 --> 01:03:18.720 align:start position:0% want to grab the URL and a lot of the 01:03:18.720 --> 01:03:20.630 align:start position:0% want to grab the URL and a lot of the links<01:03:19.020> that<01:03:19.260> were<01:03:19.619> available<01:03:19.920> at<01:03:20.339> that<01:03:20.520> time 01:03:20.630 --> 01:03:20.640 align:start position:0% links that were available at that time 01:03:20.640 --> 01:03:22.730 align:start position:0% links that were available at that time just<01:03:21.059> in<01:03:21.240> case<01:03:21.420> they<01:03:21.780> are<01:03:21.900> still<01:03:22.079> being<01:03:22.260> hosted 01:03:22.730 --> 01:03:22.740 align:start position:0% just in case they are still being hosted 01:03:22.740 --> 01:03:25.190 align:start position:0% just in case they are still being hosted on<01:03:23.520> our<01:03:23.760> specific<01:03:24.119> Target<01:03:24.359> and<01:03:24.720> they<01:03:24.900> have<01:03:25.020> not 01:03:25.190 --> 01:03:25.200 align:start position:0% on our specific Target and they have not 01:03:25.200 --> 01:03:27.829 align:start position:0% on our specific Target and they have not removed<01:03:25.680> them<01:03:25.799> which<01:03:26.220> does<01:03:26.640> happen<01:03:26.940> programs 01:03:27.829 --> 01:03:27.839 align:start position:0% removed them which does happen programs 01:03:27.839 --> 01:03:29.930 align:start position:0% removed them which does happen programs and<01:03:28.200> companies<01:03:28.740> will<01:03:29.160> be<01:03:29.339> hosting<01:03:29.760> up 01:03:29.930 --> 01:03:29.940 align:start position:0% and companies will be hosting up 01:03:29.940 --> 01:03:32.329 align:start position:0% and companies will be hosting up specific<01:03:30.480> subdomains<01:03:31.440> and<01:03:31.740> then<01:03:31.859> after<01:03:32.099> a 01:03:32.329 --> 01:03:32.339 align:start position:0% specific subdomains and then after a 01:03:32.339 --> 01:03:34.910 align:start position:0% specific subdomains and then after a while<01:03:32.460> that<01:03:32.880> subdomain<01:03:33.420> is<01:03:33.660> no<01:03:33.960> longer<01:03:34.319> in<01:03:34.680> use 01:03:34.910 --> 01:03:34.920 align:start position:0% while that subdomain is no longer in use 01:03:34.920 --> 01:03:36.829 align:start position:0% while that subdomain is no longer in use and<01:03:35.460> this<01:03:35.579> is<01:03:35.760> really<01:03:36.000> common<01:03:36.240> with<01:03:36.660> with 01:03:36.829 --> 01:03:36.839 align:start position:0% and this is really common with with 01:03:36.839 --> 01:03:39.890 align:start position:0% and this is really common with with blogs<01:03:37.440> on<01:03:37.799> large<01:03:38.160> companies<01:03:38.640> say<01:03:39.119> PlayStation 01:03:39.890 --> 01:03:39.900 align:start position:0% blogs on large companies say PlayStation 01:03:39.900 --> 01:03:42.650 align:start position:0% blogs on large companies say PlayStation comes<01:03:40.319> out<01:03:40.440> with<01:03:40.799> a<01:03:41.220> new<01:03:41.700> video<01:03:42.000> game<01:03:42.299> they'll 01:03:42.650 --> 01:03:42.660 align:start position:0% comes out with a new video game they'll 01:03:42.660 --> 01:03:44.329 align:start position:0% comes out with a new video game they'll create<01:03:42.839> a<01:03:43.020> subdomain<01:03:43.500> all<01:03:43.740> about<01:03:43.920> that<01:03:44.160> video 01:03:44.329 --> 01:03:44.339 align:start position:0% create a subdomain all about that video 01:03:44.339 --> 01:03:46.430 align:start position:0% create a subdomain all about that video game<01:03:44.640> and<01:03:45.180> then<01:03:45.359> they<01:03:45.720> will<01:03:45.839> forget<01:03:46.020> about 01:03:46.430 --> 01:03:46.440 align:start position:0% game and then they will forget about 01:03:46.440 --> 01:03:48.950 align:start position:0% game and then they will forget about that<01:03:46.680> video<01:03:46.799> game<01:03:47.099> and<01:03:47.579> years<01:03:47.760> pass<01:03:48.119> by<01:03:48.420> and 01:03:48.950 --> 01:03:48.960 align:start position:0% that video game and years pass by and 01:03:48.960 --> 01:03:50.809 align:start position:0% that video game and years pass by and that<01:03:49.140> subdomain<01:03:49.680> will<01:03:49.920> still<01:03:50.040> be<01:03:50.220> up<01:03:50.400> and<01:03:50.640> it 01:03:50.809 --> 01:03:50.819 align:start position:0% that subdomain will still be up and it 01:03:50.819 --> 01:03:52.910 align:start position:0% that subdomain will still be up and it won't<01:03:51.000> be<01:03:51.299> updated<01:03:51.900> and<01:03:52.380> it<01:03:52.680> might<01:03:52.799> be 01:03:52.910 --> 01:03:52.920 align:start position:0% won't be updated and it might be 01:03:52.920 --> 01:03:55.609 align:start position:0% won't be updated and it might be vulnerable<01:03:53.339> to<01:03:53.700> new<01:03:54.059> exploits<01:03:54.660> and<01:03:54.780> cves<01:03:55.140> and 01:03:55.609 --> 01:03:55.619 align:start position:0% vulnerable to new exploits and cves and 01:03:55.619 --> 01:03:57.829 align:start position:0% vulnerable to new exploits and cves and so<01:03:55.740> that's<01:03:55.859> why<01:03:56.099> we<01:03:56.280> want<01:03:56.460> to<01:03:56.579> look<01:03:57.059> back<01:03:57.480> into 01:03:57.829 --> 01:03:57.839 align:start position:0% so that's why we want to look back into 01:03:57.839 --> 01:04:00.789 align:start position:0% so that's why we want to look back into in<01:03:58.200> the<01:03:58.380> past<01:03:58.500> and<01:03:59.099> see<01:03:59.220> if<01:03:59.339> we<01:03:59.460> can<01:03:59.640> grab<01:04:00.000> any 01:04:00.789 --> 01:04:00.799 align:start position:0% in the past and see if we can grab any 01:04:00.799 --> 01:04:04.730 align:start position:0% in the past and see if we can grab any subdomains<01:04:01.940> or<01:04:02.940> URLs<01:04:03.660> or<01:04:03.839> links<01:04:04.260> that<01:04:04.619> may 01:04:04.730 --> 01:04:04.740 align:start position:0% subdomains or URLs or links that may 01:04:04.740 --> 01:04:07.190 align:start position:0% subdomains or URLs or links that may lead<01:04:04.920> us<01:04:05.099> to<01:04:05.400> bugs<01:04:05.940> that<01:04:06.359> other<01:04:06.599> people<01:04:06.780> have 01:04:07.190 --> 01:04:07.200 align:start position:0% lead us to bugs that other people have 01:04:07.200 --> 01:04:10.190 align:start position:0% lead us to bugs that other people have not<01:04:07.440> checked<01:04:07.920> for<01:04:08.040> within<01:04:08.819> those<01:04:09.299> forgotten 01:04:10.190 --> 01:04:10.200 align:start position:0% not checked for within those forgotten 01:04:10.200 --> 01:04:12.770 align:start position:0% not checked for within those forgotten subdomains<01:04:10.980> and<01:04:11.099> links<01:04:11.520> so<01:04:11.819> this<01:04:12.059> is<01:04:12.299> the 01:04:12.770 --> 01:04:12.780 align:start position:0% subdomains and links so this is the 01:04:12.780 --> 01:04:14.750 align:start position:0% subdomains and links so this is the Wayback<01:04:13.260> machine<01:04:13.559> you<01:04:13.920> can<01:04:13.980> come<01:04:14.099> in<01:04:14.280> here<01:04:14.400> and 01:04:14.750 --> 01:04:14.760 align:start position:0% Wayback machine you can come in here and 01:04:14.760 --> 01:04:17.390 align:start position:0% Wayback machine you can come in here and get<01:04:15.119> a<01:04:15.299> feel<01:04:15.540> for<01:04:15.960> how<01:04:16.319> it<01:04:16.440> works<01:04:16.799> and<01:04:17.280> now 01:04:17.390 --> 01:04:17.400 align:start position:0% get a feel for how it works and now 01:04:17.400 --> 01:04:18.530 align:start position:0% get a feel for how it works and now we're<01:04:17.579> we're<01:04:17.940> going<01:04:18.059> to<01:04:18.119> go<01:04:18.240> ahead<01:04:18.359> and 01:04:18.530 --> 01:04:18.540 align:start position:0% we're we're going to go ahead and 01:04:18.540 --> 01:04:21.530 align:start position:0% we're we're going to go ahead and install<01:04:18.900> the<01:04:19.500> Wayback<01:04:19.920> tool<01:04:20.339> by<01:04:20.640> Tom<01:04:20.940> Nom<01:04:21.299> Nom 01:04:21.530 --> 01:04:21.540 align:start position:0% install the Wayback tool by Tom Nom Nom 01:04:21.540 --> 01:04:23.569 align:start position:0% install the Wayback tool by Tom Nom Nom so<01:04:21.839> what<01:04:22.020> you<01:04:22.140> will<01:04:22.319> do<01:04:22.440> is<01:04:22.680> come<01:04:23.099> to<01:04:23.280> Google 01:04:23.569 --> 01:04:23.579 align:start position:0% so what you will do is come to Google 01:04:23.579 --> 01:04:25.190 align:start position:0% so what you will do is come to Google and<01:04:23.940> you're<01:04:24.059> just<01:04:24.180> going<01:04:24.299> to<01:04:24.359> type<01:04:24.540> in<01:04:24.780> way 01:04:25.190 --> 01:04:25.200 align:start position:0% and you're just going to type in way 01:04:25.200 --> 01:04:26.750 align:start position:0% and you're just going to type in way back<01:04:25.380> Tom<01:04:25.680> Nom<01:04:25.980> Nom<01:04:26.220> and<01:04:26.339> it's<01:04:26.460> going<01:04:26.640> to<01:04:26.760> be 01:04:26.750 --> 01:04:26.760 align:start position:0% back Tom Nom Nom and it's going to be 01:04:26.760 --> 01:04:29.870 align:start position:0% back Tom Nom Nom and it's going to be the<01:04:27.299> first<01:04:27.540> tool<01:04:28.079> here<01:04:28.260> for<01:04:28.680> us<01:04:28.799> and<01:04:29.520> we're 01:04:29.870 --> 01:04:29.880 align:start position:0% the first tool here for us and we're 01:04:29.880 --> 01:04:32.270 align:start position:0% the first tool here for us and we're actually<01:04:30.059> going<01:04:30.299> to<01:04:30.420> have<01:04:30.540> to<01:04:30.780> install<01:04:31.260> the<01:04:31.980> go 01:04:32.270 --> 01:04:32.280 align:start position:0% actually going to have to install the go 01:04:32.280 --> 01:04:34.730 align:start position:0% actually going to have to install the go language<01:04:32.819> before<01:04:33.660> we're<01:04:33.960> able<01:04:34.260> to<01:04:34.380> install 01:04:34.730 --> 01:04:34.740 align:start position:0% language before we're able to install 01:04:34.740 --> 01:04:36.230 align:start position:0% language before we're able to install this<01:04:35.040> so<01:04:35.280> what<01:04:35.400> you<01:04:35.520> can<01:04:35.640> do<01:04:35.700> is<01:04:35.760> open<01:04:36.000> up<01:04:36.119> a 01:04:36.230 --> 01:04:36.240 align:start position:0% this so what you can do is open up a 01:04:36.240 --> 01:04:37.430 align:start position:0% this so what you can do is open up a terminal<01:04:36.480> and<01:04:36.660> come<01:04:36.780> in<01:04:36.960> here<01:04:37.079> and<01:04:37.200> just<01:04:37.319> type 01:04:37.430 --> 01:04:37.440 align:start position:0% terminal and come in here and just type 01:04:37.440 --> 01:04:39.170 align:start position:0% terminal and come in here and just type in<01:04:37.619> go<01:04:37.799> and<01:04:38.040> if<01:04:38.160> it<01:04:38.280> doesn't<01:04:38.400> turn<01:04:38.640> green<01:04:38.880> then 01:04:39.170 --> 01:04:39.180 align:start position:0% in go and if it doesn't turn green then 01:04:39.180 --> 01:04:40.609 align:start position:0% in go and if it doesn't turn green then you<01:04:39.359> do<01:04:39.480> not<01:04:39.660> have<01:04:39.900> the<01:04:40.140> go<01:04:40.319> language 01:04:40.609 --> 01:04:40.619 align:start position:0% you do not have the go language 01:04:40.619 --> 01:04:42.589 align:start position:0% you do not have the go language installed<01:04:41.400> so<01:04:41.880> what<01:04:42.059> we're<01:04:42.180> going<01:04:42.299> to<01:04:42.359> need<01:04:42.540> to 01:04:42.589 --> 01:04:42.599 align:start position:0% installed so what we're going to need to 01:04:42.599 --> 01:04:45.230 align:start position:0% installed so what we're going to need to do<01:04:42.720> is<01:04:43.020> run<01:04:43.319> a<01:04:43.619> sudo<01:04:44.099> apt<01:04:44.339> update<01:04:44.700> just<01:04:45.059> like 01:04:45.230 --> 01:04:45.240 align:start position:0% do is run a sudo apt update just like 01:04:45.240 --> 01:04:47.750 align:start position:0% do is run a sudo apt update just like this<01:04:45.480> and<01:04:46.020> let<01:04:46.319> this<01:04:46.559> update<01:04:46.920> and<01:04:47.099> if<01:04:47.220> yours<01:04:47.579> it 01:04:47.750 --> 01:04:47.760 align:start position:0% this and let this update and if yours it 01:04:47.760 --> 01:04:49.069 align:start position:0% this and let this update and if yours it doesn't<01:04:47.880> update<01:04:48.240> or<01:04:48.359> gives<01:04:48.599> you<01:04:48.660> some<01:04:48.839> kind<01:04:48.960> of 01:04:49.069 --> 01:04:49.079 align:start position:0% doesn't update or gives you some kind of 01:04:49.079 --> 01:04:51.109 align:start position:0% doesn't update or gives you some kind of warning<01:04:49.380> you<01:04:49.559> might<01:04:49.680> have<01:04:49.859> to<01:04:49.980> run<01:04:50.160> a<01:04:50.400> sudo<01:04:50.760> apt 01:04:51.109 --> 01:04:51.119 align:start position:0% warning you might have to run a sudo apt 01:04:51.119 --> 01:04:53.569 align:start position:0% warning you might have to run a sudo apt upgrade<01:04:51.540> and<01:04:52.079> then<01:04:52.200> run<01:04:52.440> the<01:04:52.680> sudo<01:04:53.099> app<01:04:53.220> update 01:04:53.569 --> 01:04:53.579 align:start position:0% upgrade and then run the sudo app update 01:04:53.579 --> 01:04:55.190 align:start position:0% upgrade and then run the sudo app update so<01:04:53.760> now<01:04:53.940> that<01:04:54.059> we're<01:04:54.180> all<01:04:54.359> updated<01:04:54.720> we<01:04:54.900> can<01:04:55.020> run 01:04:55.190 --> 01:04:55.200 align:start position:0% so now that we're all updated we can run 01:04:55.200 --> 01:04:59.990 align:start position:0% so now that we're all updated we can run sudo<01:04:55.799> app<01:04:56.160> install<01:04:56.960> go<01:04:57.960> Lang<01:04:58.740> like<01:04:59.220> this 01:04:59.990 --> 01:05:00.000 align:start position:0% sudo app install go Lang like this 01:05:00.000 --> 01:05:02.569 align:start position:0% sudo app install go Lang like this and<01:05:00.540> we'll<01:05:00.660> say<01:05:00.900> yes<01:05:01.200> and<01:05:01.740> now<01:05:01.920> if<01:05:02.160> we<01:05:02.280> type<01:05:02.400> in 01:05:02.569 --> 01:05:02.579 align:start position:0% and we'll say yes and now if we type in 01:05:02.579 --> 01:05:05.210 align:start position:0% and we'll say yes and now if we type in go<01:05:02.880> it<01:05:03.299> should<01:05:03.480> turn<01:05:03.780> blue<01:05:04.260> for<01:05:04.619> us<01:05:04.859> or<01:05:05.040> some 01:05:05.210 --> 01:05:05.220 align:start position:0% go it should turn blue for us or some 01:05:05.220 --> 01:05:07.250 align:start position:0% go it should turn blue for us or some other<01:05:05.400> color<01:05:05.640> meaning<01:05:06.359> that<01:05:06.660> we<01:05:06.839> have<01:05:06.900> the<01:05:07.079> go 01:05:07.250 --> 01:05:07.260 align:start position:0% other color meaning that we have the go 01:05:07.260 --> 01:05:09.230 align:start position:0% other color meaning that we have the go language<01:05:07.559> installed<01:05:08.220> so<01:05:08.339> we<01:05:08.520> can<01:05:08.640> come<01:05:08.760> back 01:05:09.230 --> 01:05:09.240 align:start position:0% language installed so we can come back 01:05:09.240 --> 01:05:12.049 align:start position:0% language installed so we can come back to<01:05:09.540> the<01:05:09.960> Tom<01:05:10.260> Nom<01:05:10.619> Nom<01:05:10.920> site<01:05:11.220> and<01:05:11.640> we<01:05:11.819> can<01:05:11.880> just 01:05:12.049 --> 01:05:12.059 align:start position:0% to the Tom Nom Nom site and we can just 01:05:12.059 --> 01:05:14.210 align:start position:0% to the Tom Nom Nom site and we can just highlight<01:05:12.359> this<01:05:12.599> and<01:05:12.780> it's<01:05:12.900> gonna<01:05:13.079> and<01:05:13.859> we<01:05:14.160> can 01:05:14.210 --> 01:05:14.220 align:start position:0% highlight this and it's gonna and we can 01:05:14.220 --> 01:05:16.190 align:start position:0% highlight this and it's gonna and we can just<01:05:14.339> copy<01:05:14.700> this<01:05:14.940> right<01:05:15.240> here<01:05:15.480> and<01:05:16.020> it's 01:05:16.190 --> 01:05:16.200 align:start position:0% just copy this right here and it's 01:05:16.200 --> 01:05:18.349 align:start position:0% just copy this right here and it's actually<01:05:16.440> going<01:05:16.859> to<01:05:17.099> install<01:05:17.520> the<01:05:17.940> tool<01:05:18.180> for 01:05:18.349 --> 01:05:18.359 align:start position:0% actually going to install the tool for 01:05:18.359 --> 01:05:20.750 align:start position:0% actually going to install the tool for us<01:05:18.480> and<01:05:18.660> I<01:05:18.780> think<01:05:18.900> it<01:05:19.020> installs<01:05:19.559> it<01:05:19.680> in<01:05:20.040> in<01:05:20.460> the 01:05:20.750 --> 01:05:20.760 align:start position:0% us and I think it installs it in in the 01:05:20.760 --> 01:05:23.630 align:start position:0% us and I think it installs it in in the directory<01:05:21.480> Go<01:05:22.079> slash<01:05:22.500> bin<01:05:22.920> so<01:05:23.220> I'll<01:05:23.339> show<01:05:23.520> you 01:05:23.630 --> 01:05:23.640 align:start position:0% directory Go slash bin so I'll show you 01:05:23.640 --> 01:05:25.490 align:start position:0% directory Go slash bin so I'll show you that<01:05:23.760> in<01:05:23.880> just<01:05:24.059> a<01:05:24.180> second<01:05:24.299> we<01:05:24.900> can<01:05:25.079> paste<01:05:25.380> this 01:05:25.490 --> 01:05:25.500 align:start position:0% that in just a second we can paste this 01:05:25.500 --> 01:05:26.690 align:start position:0% that in just a second we can paste this in<01:05:25.619> and<01:05:25.859> I<01:05:25.980> think<01:05:26.099> we're<01:05:26.220> gonna<01:05:26.339> have<01:05:26.520> to<01:05:26.579> run 01:05:26.690 --> 01:05:26.700 align:start position:0% in and I think we're gonna have to run 01:05:26.700 --> 01:05:29.030 align:start position:0% in and I think we're gonna have to run this<01:05:26.880> as<01:05:27.119> a<01:05:27.480> sudo<01:05:28.079> okay<01:05:28.260> so<01:05:28.559> when<01:05:28.680> I<01:05:28.799> ran<01:05:28.980> it 01:05:29.030 --> 01:05:29.040 align:start position:0% this as a sudo okay so when I ran it 01:05:29.040 --> 01:05:31.069 align:start position:0% this as a sudo okay so when I ran it with<01:05:29.160> sudo<01:05:29.640> it<01:05:29.880> didn't<01:05:30.000> work<01:05:30.180> for<01:05:30.359> me<01:05:30.480> so<01:05:30.780> when 01:05:31.069 --> 01:05:31.079 align:start position:0% with sudo it didn't work for me so when 01:05:31.079 --> 01:05:33.470 align:start position:0% with sudo it didn't work for me so when it<01:05:31.380> actually<01:05:31.559> installs<01:05:32.220> the<01:05:32.460> proper<01:05:32.819> way<01:05:32.940> it's 01:05:33.470 --> 01:05:33.480 align:start position:0% it actually installs the proper way it's 01:05:33.480 --> 01:05:34.730 align:start position:0% it actually installs the proper way it's going<01:05:33.660> to<01:05:33.720> run<01:05:33.839> just<01:05:34.200> like<01:05:34.319> this<01:05:34.500> and<01:05:34.619> you're 01:05:34.730 --> 01:05:34.740 align:start position:0% going to run just like this and you're 01:05:34.740 --> 01:05:36.109 align:start position:0% going to run just like this and you're going<01:05:34.859> to<01:05:34.980> see<01:05:35.040> nothing<01:05:35.339> in<01:05:35.579> the<01:05:35.700> output<01:05:35.940> and 01:05:36.109 --> 01:05:36.119 align:start position:0% going to see nothing in the output and 01:05:36.119 --> 01:05:37.250 align:start position:0% going to see nothing in the output and then<01:05:36.240> what<01:05:36.420> you're<01:05:36.540> going<01:05:36.599> to<01:05:36.660> want<01:05:36.780> to<01:05:36.900> do<01:05:37.020> is 01:05:37.250 --> 01:05:37.260 align:start position:0% then what you're going to want to do is 01:05:37.260 --> 01:05:40.069 align:start position:0% then what you're going to want to do is CD<01:05:37.799> over<01:05:38.160> to<01:05:38.520> the<01:05:39.000> go<01:05:39.240> bin<01:05:39.599> and<01:05:39.780> it's<01:05:39.839> going<01:05:39.960> to 01:05:40.069 --> 01:05:40.079 align:start position:0% CD over to the go bin and it's going to 01:05:40.079 --> 01:05:41.630 align:start position:0% CD over to the go bin and it's going to look<01:05:40.200> like<01:05:40.319> this<01:05:40.500> and<01:05:40.799> you'll<01:05:41.099> hit<01:05:41.220> enter<01:05:41.400> and 01:05:41.630 --> 01:05:41.640 align:start position:0% look like this and you'll hit enter and 01:05:41.640 --> 01:05:42.650 align:start position:0% look like this and you'll hit enter and you're<01:05:41.760> going<01:05:41.880> to<01:05:41.940> automatically<01:05:42.299> come<01:05:42.480> into 01:05:42.650 --> 01:05:42.660 align:start position:0% you're going to automatically come into 01:05:42.660 --> 01:05:44.030 align:start position:0% you're going to automatically come into the<01:05:42.900> directory<01:05:43.200> like<01:05:43.380> this<01:05:43.500> and<01:05:43.680> then<01:05:43.740> if<01:05:43.859> you 01:05:44.030 --> 01:05:44.040 align:start position:0% the directory like this and then if you 01:05:44.040 --> 01:05:46.549 align:start position:0% the directory like this and then if you LS<01:05:44.339> you're<01:05:44.520> going<01:05:44.640> to<01:05:44.760> see<01:05:44.940> the<01:05:45.420> Wayback<01:05:45.900> URLs 01:05:46.549 --> 01:05:46.559 align:start position:0% LS you're going to see the Wayback URLs 01:05:46.559 --> 01:05:48.890 align:start position:0% LS you're going to see the Wayback URLs within<01:05:47.339> the<01:05:47.700> file<01:05:48.000> here<01:05:48.240> and<01:05:48.540> the<01:05:48.720> way<01:05:48.780> we're 01:05:48.890 --> 01:05:48.900 align:start position:0% within the file here and the way we're 01:05:48.900 --> 01:05:50.630 align:start position:0% within the file here and the way we're going<01:05:49.020> to<01:05:49.140> run<01:05:49.260> this<01:05:49.380> is<01:05:49.619> with<01:05:49.799> this<01:05:49.980> dot<01:05:50.400> slash 01:05:50.630 --> 01:05:50.640 align:start position:0% going to run this is with this dot slash 01:05:50.640 --> 01:05:53.089 align:start position:0% going to run this is with this dot slash and<01:05:51.059> then<01:05:51.240> the<01:05:51.900> name<01:05:52.319> of<01:05:52.559> the<01:05:52.680> tool<01:05:52.920> that<01:05:52.980> we 01:05:53.089 --> 01:05:53.099 align:start position:0% and then the name of the tool that we 01:05:53.099 --> 01:05:54.650 align:start position:0% and then the name of the tool that we want<01:05:53.280> to<01:05:53.400> run<01:05:53.520> and<01:05:54.000> just<01:05:54.180> so<01:05:54.240> you<01:05:54.359> can<01:05:54.480> see<01:05:54.540> what 01:05:54.650 --> 01:05:54.660 align:start position:0% want to run and just so you can see what 01:05:54.660 --> 01:05:56.510 align:start position:0% want to run and just so you can see what it<01:05:54.780> looks<01:05:54.960> like<01:05:55.020> you<01:05:55.200> can<01:05:55.319> run<01:05:55.440> a<01:05:55.680> dash<01:05:55.980> H<01:05:56.160> and 01:05:56.510 --> 01:05:56.520 align:start position:0% it looks like you can run a dash H and 01:05:56.520 --> 01:05:59.329 align:start position:0% it looks like you can run a dash H and see<01:05:56.880> the<01:05:57.240> output<01:05:57.599> here<01:05:57.900> okay<01:05:58.260> yeah<01:05:58.559> so<01:05:58.980> my 01:05:59.329 --> 01:05:59.339 align:start position:0% see the output here okay yeah so my 01:05:59.339 --> 01:06:01.970 align:start position:0% see the output here okay yeah so my other<01:05:59.520> VM<01:05:59.940> was<01:06:00.839> freezing<01:06:01.380> so<01:06:01.559> I<01:06:01.680> went<01:06:01.799> ahead 01:06:01.970 --> 01:06:01.980 align:start position:0% other VM was freezing so I went ahead 01:06:01.980 --> 01:06:03.589 align:start position:0% other VM was freezing so I went ahead and<01:06:02.040> opened<01:06:02.280> up<01:06:02.400> a<01:06:02.579> new<01:06:02.640> one<01:06:02.819> which<01:06:03.119> is<01:06:03.299> just 01:06:03.589 --> 01:06:03.599 align:start position:0% and opened up a new one which is just 01:06:03.599 --> 01:06:06.049 align:start position:0% and opened up a new one which is just fine<01:06:03.839> it<01:06:04.740> will<01:06:04.859> all<01:06:05.040> work<01:06:05.339> the<01:06:05.520> same<01:06:05.700> so<01:06:05.880> I<01:06:06.000> went 01:06:06.049 --> 01:06:06.059 align:start position:0% fine it will all work the same so I went 01:06:06.059 --> 01:06:07.549 align:start position:0% fine it will all work the same so I went ahead<01:06:06.299> and<01:06:06.420> installed<01:06:06.960> it<01:06:07.079> on<01:06:07.319> this<01:06:07.440> new 01:06:07.549 --> 01:06:07.559 align:start position:0% ahead and installed it on this new 01:06:07.559 --> 01:06:09.109 align:start position:0% ahead and installed it on this new machine<01:06:07.799> and<01:06:08.099> you're<01:06:08.220> going<01:06:08.400> to<01:06:08.460> find<01:06:08.579> it<01:06:08.819> in 01:06:09.109 --> 01:06:09.119 align:start position:0% machine and you're going to find it in 01:06:09.119 --> 01:06:11.750 align:start position:0% machine and you're going to find it in the<01:06:09.480> go<01:06:09.720> bin<01:06:10.079> and<01:06:10.260> so<01:06:10.380> if<01:06:10.500> I<01:06:10.680> run<01:06:10.799> an<01:06:11.160> LS<01:06:11.520> you're 01:06:11.750 --> 01:06:11.760 align:start position:0% the go bin and so if I run an LS you're 01:06:11.760 --> 01:06:13.130 align:start position:0% the go bin and so if I run an LS you're going<01:06:11.940> to<01:06:12.000> see<01:06:12.180> I<01:06:12.599> actually<01:06:12.720> have<01:06:12.900> a<01:06:13.020> couple 01:06:13.130 --> 01:06:13.140 align:start position:0% going to see I actually have a couple 01:06:13.140 --> 01:06:14.569 align:start position:0% going to see I actually have a couple other<01:06:13.319> tools<01:06:13.680> in<01:06:13.859> here<01:06:13.980> but<01:06:14.280> I'm<01:06:14.400> going<01:06:14.520> to 01:06:14.569 --> 01:06:14.579 align:start position:0% other tools in here but I'm going to 01:06:14.579 --> 01:06:16.309 align:start position:0% other tools in here but I'm going to show<01:06:14.700> you<01:06:14.819> how<01:06:15.059> to<01:06:15.240> install<01:06:15.540> those<01:06:15.839> in<01:06:16.079> just<01:06:16.200> a 01:06:16.309 --> 01:06:16.319 align:start position:0% show you how to install those in just a 01:06:16.319 --> 01:06:18.530 align:start position:0% show you how to install those in just a second<01:06:16.500> but<01:06:17.160> this<01:06:17.400> is<01:06:17.579> the<01:06:17.819> tool<01:06:18.119> you<01:06:18.299> just 01:06:18.530 --> 01:06:18.540 align:start position:0% second but this is the tool you just 01:06:18.540 --> 01:06:20.329 align:start position:0% second but this is the tool you just installed<01:06:19.020> right<01:06:19.140> here<01:06:19.380> so<01:06:19.859> the<01:06:20.040> way<01:06:20.220> we're 01:06:20.329 --> 01:06:20.339 align:start position:0% installed right here so the way we're 01:06:20.339 --> 01:06:22.190 align:start position:0% installed right here so the way we're going<01:06:20.520> to<01:06:20.579> run<01:06:20.700> it<01:06:20.880> is<01:06:21.119> really<01:06:21.359> simple<01:06:21.780> but 01:06:22.190 --> 01:06:22.200 align:start position:0% going to run it is really simple but 01:06:22.200 --> 01:06:25.430 align:start position:0% going to run it is really simple but first<01:06:22.380> we<01:06:22.740> need<01:06:22.920> to<01:06:23.220> create<01:06:23.640> a<01:06:24.119> Target<01:06:24.440> domain 01:06:25.430 --> 01:06:25.440 align:start position:0% first we need to create a Target domain 01:06:25.440 --> 01:06:28.069 align:start position:0% first we need to create a Target domain for<01:06:25.740> us<01:06:25.859> so<01:06:26.039> we're<01:06:26.160> going<01:06:26.280> to<01:06:26.339> G<01:06:26.520> edit<01:06:27.359> and<01:06:27.900> I'm 01:06:28.069 --> 01:06:28.079 align:start position:0% for us so we're going to G edit and I'm 01:06:28.079 --> 01:06:30.190 align:start position:0% for us so we're going to G edit and I'm going<01:06:28.319> to<01:06:28.559> get<01:06:28.980> it<01:06:29.400> yahoo 01:06:30.190 --> 01:06:30.200 align:start position:0% going to get it yahoo 01:06:30.200 --> 01:06:33.549 align:start position:0% going to get it yahoo Dot<01:06:31.200> txt<01:06:31.579> and<01:06:32.579> we<01:06:32.760> can<01:06:32.880> just<01:06:33.000> type<01:06:33.240> in 01:06:33.549 --> 01:06:33.559 align:start position:0% Dot txt and we can just type in 01:06:33.559 --> 01:06:35.930 align:start position:0% Dot txt and we can just type in yahoo.com<01:06:34.559> and<01:06:35.099> this<01:06:35.220> is<01:06:35.339> going<01:06:35.460> to<01:06:35.579> be<01:06:35.640> our 01:06:35.930 --> 01:06:35.940 align:start position:0% yahoo.com and this is going to be our 01:06:35.940 --> 01:06:38.029 align:start position:0% yahoo.com and this is going to be our domain<01:06:36.359> that<01:06:36.720> we<01:06:36.839> Target<01:06:37.140> and<01:06:37.619> if<01:06:37.740> there's<01:06:37.859> any 01:06:38.029 --> 01:06:38.039 align:start position:0% domain that we Target and if there's any 01:06:38.039 --> 01:06:40.069 align:start position:0% domain that we Target and if there's any subdomains<01:06:38.700> in<01:06:38.760> here<01:06:38.940> you'd<01:06:39.299> want<01:06:39.480> to<01:06:39.599> paste 01:06:40.069 --> 01:06:40.079 align:start position:0% subdomains in here you'd want to paste 01:06:40.079 --> 01:06:41.230 align:start position:0% subdomains in here you'd want to paste in<01:06:40.140> like<01:06:40.440> a 01:06:41.230 --> 01:06:41.240 align:start position:0% in like a 01:06:41.240 --> 01:06:43.670 align:start position:0% in like a sub.yahoo.com<01:06:42.240> and<01:06:43.200> I'm<01:06:43.319> going<01:06:43.440> to<01:06:43.500> show<01:06:43.619> you 01:06:43.670 --> 01:06:43.680 align:start position:0% sub.yahoo.com and I'm going to show you 01:06:43.680 --> 01:06:45.589 align:start position:0% sub.yahoo.com and I'm going to show you how<01:06:43.920> to<01:06:44.039> grab<01:06:44.339> these<01:06:44.640> subdomains<01:06:45.180> here<01:06:45.359> in 01:06:45.589 --> 01:06:45.599 align:start position:0% how to grab these subdomains here in 01:06:45.599 --> 01:06:46.970 align:start position:0% how to grab these subdomains here in just<01:06:45.780> a<01:06:45.900> second<01:06:46.020> so<01:06:46.380> we're<01:06:46.500> going<01:06:46.619> to<01:06:46.740> leave<01:06:46.799> it 01:06:46.970 --> 01:06:46.980 align:start position:0% just a second so we're going to leave it 01:06:46.980 --> 01:06:48.170 align:start position:0% just a second so we're going to leave it just<01:06:47.160> like<01:06:47.339> this 01:06:48.170 --> 01:06:48.180 align:start position:0% just like this 01:06:48.180 --> 01:06:52.130 align:start position:0% just like this we<01:06:48.900> will<01:06:49.140> save<01:06:49.619> and<01:06:50.579> now<01:06:50.760> we<01:06:51.059> can<01:06:51.240> run<01:06:51.660> the 01:06:52.130 --> 01:06:52.140 align:start position:0% we will save and now we can run the 01:06:52.140 --> 01:06:55.010 align:start position:0% we will save and now we can run the Wayback<01:06:52.559> URLs<01:06:53.160> tool<01:06:53.640> and<01:06:54.180> while<01:06:54.359> it<01:06:54.539> runs<01:06:54.839> I'll 01:06:55.010 --> 01:06:55.020 align:start position:0% Wayback URLs tool and while it runs I'll 01:06:55.020 --> 01:06:57.230 align:start position:0% Wayback URLs tool and while it runs I'll show<01:06:55.200> you<01:06:55.260> how<01:06:55.440> to<01:06:55.559> grab<01:06:55.859> the<01:06:56.099> subdomains<01:06:56.819> so 01:06:57.230 --> 01:06:57.240 align:start position:0% show you how to grab the subdomains so 01:06:57.240 --> 01:06:59.329 align:start position:0% show you how to grab the subdomains so what<01:06:57.420> we'll<01:06:57.539> do<01:06:57.660> is<01:06:57.900> cat<01:06:58.140> that<01:06:58.500> file<01:06:58.740> that<01:06:59.039> we 01:06:59.329 --> 01:06:59.339 align:start position:0% what we'll do is cat that file that we 01:06:59.339 --> 01:07:01.970 align:start position:0% what we'll do is cat that file that we just<01:06:59.760> made<01:07:00.059> and<01:07:00.660> we're<01:07:00.780> going<01:07:00.900> to<01:07:00.960> run<01:07:01.079> it<01:07:01.319> into 01:07:01.970 --> 01:07:01.980 align:start position:0% just made and we're going to run it into 01:07:01.980 --> 01:07:05.390 align:start position:0% just made and we're going to run it into the<01:07:02.819> Wayback<01:07:03.420> URLs<01:07:04.140> just<01:07:04.380> like<01:07:04.500> this<01:07:04.740> and<01:07:05.280> then 01:07:05.390 --> 01:07:05.400 align:start position:0% the Wayback URLs just like this and then 01:07:05.400 --> 01:07:07.069 align:start position:0% the Wayback URLs just like this and then you<01:07:05.579> can<01:07:05.700> actually<01:07:05.819> save<01:07:06.180> all<01:07:06.420> those<01:07:06.599> into<01:07:06.839> an 01:07:07.069 --> 01:07:07.079 align:start position:0% you can actually save all those into an 01:07:07.079 --> 01:07:09.829 align:start position:0% you can actually save all those into an out<01:07:07.200> file<01:07:07.500> by<01:07:08.039> pointing<01:07:08.579> it<01:07:08.700> over<01:07:08.880> to<01:07:09.359> the<01:07:09.539> file 01:07:09.829 --> 01:07:09.839 align:start position:0% out file by pointing it over to the file 01:07:09.839 --> 01:07:11.150 align:start position:0% out file by pointing it over to the file you<01:07:10.020> would<01:07:10.140> like<01:07:10.260> to<01:07:10.380> call<01:07:10.500> it<01:07:10.619> so<01:07:10.740> we'll<01:07:10.920> call 01:07:11.150 --> 01:07:11.160 align:start position:0% you would like to call it so we'll call 01:07:11.160 --> 01:07:14.029 align:start position:0% you would like to call it so we'll call it<01:07:11.280> yahoo<01:07:11.880> dot<01:07:12.660> urls 01:07:14.029 --> 01:07:14.039 align:start position:0% it yahoo dot urls 01:07:14.039 --> 01:07:16.609 align:start position:0% it yahoo dot urls and<01:07:14.640> we'll<01:07:14.819> let<01:07:15.000> this<01:07:15.180> run<01:07:15.420> and<01:07:16.140> now<01:07:16.319> while 01:07:16.609 --> 01:07:16.619 align:start position:0% and we'll let this run and now while 01:07:16.619 --> 01:07:18.589 align:start position:0% and we'll let this run and now while that<01:07:16.859> runs<01:07:17.220> we're<01:07:17.460> going<01:07:17.640> to<01:07:17.700> go<01:07:17.880> ahead<01:07:18.059> and 01:07:18.589 --> 01:07:18.599 align:start position:0% that runs we're going to go ahead and 01:07:18.599 --> 01:07:20.089 align:start position:0% that runs we're going to go ahead and grab<01:07:18.960> some<01:07:19.140> subdomains<01:07:19.680> so<01:07:19.799> we're<01:07:19.920> going<01:07:20.039> to 01:07:20.089 --> 01:07:20.099 align:start position:0% grab some subdomains so we're going to 01:07:20.099 --> 01:07:21.650 align:start position:0% grab some subdomains so we're going to run<01:07:20.280> an<01:07:20.520> amass 01:07:21.650 --> 01:07:21.660 align:start position:0% run an amass 01:07:21.660 --> 01:07:26.289 align:start position:0% run an amass enum<01:07:22.579> Dash<01:07:23.579> passive<01:07:24.380> Dash<01:07:25.380> D 01:07:26.289 --> 01:07:26.299 align:start position:0% enum Dash passive Dash D 01:07:26.299 --> 01:07:28.910 align:start position:0% enum Dash passive Dash D yahoo.com<01:07:27.299> and<01:07:28.020> this<01:07:28.319> might<01:07:28.500> take<01:07:28.680> a<01:07:28.799> second 01:07:28.910 --> 01:07:28.920 align:start position:0% yahoo.com and this might take a second 01:07:28.920 --> 01:07:31.250 align:start position:0% yahoo.com and this might take a second and<01:07:29.160> it's<01:07:29.280> going<01:07:29.460> to<01:07:29.579> give<01:07:29.640> us<01:07:29.880> a<01:07:30.240> ton<01:07:30.660> of<01:07:30.960> sub 01:07:31.250 --> 01:07:31.260 align:start position:0% and it's going to give us a ton of sub 01:07:31.260 --> 01:07:33.410 align:start position:0% and it's going to give us a ton of sub domains<01:07:31.740> that<01:07:31.920> we<01:07:32.039> would<01:07:32.160> want<01:07:32.280> to<01:07:32.460> run<01:07:32.700> the 01:07:33.410 --> 01:07:33.420 align:start position:0% domains that we would want to run the 01:07:33.420 --> 01:07:35.569 align:start position:0% domains that we would want to run the Wayback<01:07:33.839> tool<01:07:34.200> on<01:07:34.380> and<01:07:34.740> so<01:07:34.859> our<01:07:35.039> goal<01:07:35.280> is<01:07:35.400> to 01:07:35.569 --> 01:07:35.579 align:start position:0% Wayback tool on and so our goal is to 01:07:35.579 --> 01:07:38.210 align:start position:0% Wayback tool on and so our goal is to find<01:07:35.760> really<01:07:36.059> old<01:07:36.299> pages<01:07:36.740> on<01:07:37.740> these 01:07:38.210 --> 01:07:38.220 align:start position:0% find really old pages on these 01:07:38.220 --> 01:07:41.150 align:start position:0% find really old pages on these subdomains<01:07:38.940> from<01:07:39.180> the<01:07:39.539> way<01:07:39.780> back<01:07:40.020> tool<01:07:40.500> that 01:07:41.150 --> 01:07:41.160 align:start position:0% subdomains from the way back tool that 01:07:41.160 --> 01:07:42.589 align:start position:0% subdomains from the way back tool that are<01:07:41.280> going<01:07:41.460> to<01:07:41.579> have<01:07:41.700> some<01:07:41.940> vulnerabilities 01:07:42.589 --> 01:07:42.599 align:start position:0% are going to have some vulnerabilities 01:07:42.599 --> 01:07:44.450 align:start position:0% are going to have some vulnerabilities so<01:07:42.839> we'll<01:07:43.020> go<01:07:43.140> ahead<01:07:43.319> and<01:07:43.500> close<01:07:43.859> out<01:07:44.099> of<01:07:44.280> this 01:07:44.450 --> 01:07:44.460 align:start position:0% so we'll go ahead and close out of this 01:07:44.460 --> 01:07:45.890 align:start position:0% so we'll go ahead and close out of this and<01:07:44.880> what<01:07:45.000> we're<01:07:45.119> going<01:07:45.240> to<01:07:45.299> end<01:07:45.420> up<01:07:45.480> doing<01:07:45.660> is 01:07:45.890 --> 01:07:45.900 align:start position:0% and what we're going to end up doing is 01:07:45.900 --> 01:07:48.410 align:start position:0% and what we're going to end up doing is just<01:07:46.079> grabbing<01:07:46.619> like<01:07:47.280> 10<01:07:47.579> of<01:07:47.760> these<01:07:47.940> because<01:07:48.119> I 01:07:48.410 --> 01:07:48.420 align:start position:0% just grabbing like 10 of these because I 01:07:48.420 --> 01:07:50.029 align:start position:0% just grabbing like 10 of these because I don't<01:07:48.480> really<01:07:48.780> want<01:07:48.960> to<01:07:49.140> run<01:07:49.380> the<01:07:49.680> Wayback 01:07:50.029 --> 01:07:50.039 align:start position:0% don't really want to run the Wayback 01:07:50.039 --> 01:07:52.370 align:start position:0% don't really want to run the Wayback tool<01:07:50.400> on<01:07:50.460> all<01:07:50.640> of<01:07:50.760> these<01:07:50.940> you<01:07:51.480> would<01:07:51.720> run<01:07:52.020> it<01:07:52.200> on 01:07:52.370 --> 01:07:52.380 align:start position:0% tool on all of these you would run it on 01:07:52.380 --> 01:07:54.529 align:start position:0% tool on all of these you would run it on these<01:07:52.619> if<01:07:52.859> you<01:07:52.980> were<01:07:53.099> actually<01:07:53.220> looking<01:07:53.579> for 01:07:54.529 --> 01:07:54.539 align:start position:0% these if you were actually looking for 01:07:54.539 --> 01:07:56.870 align:start position:0% these if you were actually looking for any<01:07:55.020> vulnerabilities<01:07:55.859> Within<01:07:56.460> These<01:07:56.700> pages 01:07:56.870 --> 01:07:56.880 align:start position:0% any vulnerabilities Within These pages 01:07:56.880 --> 01:07:59.270 align:start position:0% any vulnerabilities Within These pages but<01:07:57.240> my<01:07:57.480> goal<01:07:57.720> is<01:07:57.839> just<01:07:58.020> to<01:07:58.319> showcase<01:07:58.799> the<01:07:59.039> tool 01:07:59.270 --> 01:07:59.280 align:start position:0% but my goal is just to showcase the tool 01:07:59.280 --> 01:08:01.789 align:start position:0% but my goal is just to showcase the tool for<01:07:59.460> you<01:07:59.579> so<01:08:00.119> we<01:08:00.299> will<01:08:00.539> copy<01:08:01.079> some<01:08:01.440> of<01:08:01.559> these 01:08:01.789 --> 01:08:01.799 align:start position:0% for you so we will copy some of these 01:08:01.799 --> 01:08:04.490 align:start position:0% for you so we will copy some of these URLs<01:08:02.520> and<01:08:03.059> come<01:08:03.359> back<01:08:03.480> over<01:08:03.660> here<01:08:03.900> and<01:08:04.200> this<01:08:04.380> is 01:08:04.490 --> 01:08:04.500 align:start position:0% URLs and come back over here and this is 01:08:04.500 --> 01:08:07.309 align:start position:0% URLs and come back over here and this is still<01:08:04.740> running<01:08:04.980> so<01:08:05.880> oh<01:08:06.180> it<01:08:06.480> just<01:08:06.599> finished<01:08:06.780> so 01:08:07.309 --> 01:08:07.319 align:start position:0% still running so oh it just finished so 01:08:07.319 --> 01:08:10.609 align:start position:0% still running so oh it just finished so what<01:08:07.440> we'll<01:08:07.619> do<01:08:07.799> is<01:08:08.099> now<01:08:08.400> we<01:08:08.700> can<01:08:09.000> G<01:08:09.780> edit<01:08:10.200> our 01:08:10.609 --> 01:08:10.619 align:start position:0% what we'll do is now we can G edit our 01:08:10.619 --> 01:08:12.770 align:start position:0% what we'll do is now we can G edit our yahoo.txt 01:08:12.770 --> 01:08:12.780 align:start position:0% yahoo.txt 01:08:12.780 --> 01:08:15.529 align:start position:0% yahoo.txt like<01:08:13.440> this<01:08:13.680> and<01:08:14.460> what<01:08:14.640> you<01:08:14.760> would<01:08:14.880> do<01:08:15.000> is<01:08:15.299> you 01:08:15.529 --> 01:08:15.539 align:start position:0% like this and what you would do is you 01:08:15.539 --> 01:08:18.650 align:start position:0% like this and what you would do is you would<01:08:15.720> run<01:08:16.020> all<01:08:16.739> of<01:08:16.859> these<01:08:17.219> subdomains<01:08:18.000> in<01:08:18.420> a 01:08:18.650 --> 01:08:18.660 align:start position:0% would run all of these subdomains in a 01:08:18.660 --> 01:08:20.930 align:start position:0% would run all of these subdomains in a file<01:08:19.140> just<01:08:19.560> like<01:08:19.739> this<01:08:19.920> so<01:08:20.219> you<01:08:20.339> might<01:08:20.460> want<01:08:20.699> to 01:08:20.930 --> 01:08:20.940 align:start position:0% file just like this so you might want to 01:08:20.940 --> 01:08:24.829 align:start position:0% file just like this so you might want to save<01:08:21.480> this<01:08:22.140> a<01:08:22.380> mouse<01:08:22.620> right<01:08:23.580> here<01:08:23.819> into<01:08:24.359> an<01:08:24.660> out 01:08:24.829 --> 01:08:24.839 align:start position:0% save this a mouse right here into an out 01:08:24.839 --> 01:08:26.510 align:start position:0% save this a mouse right here into an out file<01:08:25.199> so<01:08:25.380> that<01:08:25.500> you<01:08:25.679> don't<01:08:25.799> have<01:08:25.920> to<01:08:26.100> copy<01:08:26.400> and 01:08:26.510 --> 01:08:26.520 align:start position:0% file so that you don't have to copy and 01:08:26.520 --> 01:08:29.030 align:start position:0% file so that you don't have to copy and paste<01:08:26.940> but<01:08:27.540> that's<01:08:28.020> okay<01:08:28.259> that<01:08:28.679> we're<01:08:28.920> not 01:08:29.030 --> 01:08:29.040 align:start position:0% paste but that's okay that we're not 01:08:29.040 --> 01:08:31.010 align:start position:0% paste but that's okay that we're not going<01:08:29.219> to<01:08:29.219> do<01:08:29.400> that<01:08:29.520> and<01:08:30.359> we're<01:08:30.540> going<01:08:30.660> to<01:08:30.779> save 01:08:31.010 --> 01:08:31.020 align:start position:0% going to do that and we're going to save 01:08:31.020 --> 01:08:32.930 align:start position:0% going to do that and we're going to save this<01:08:31.319> and<01:08:31.560> now<01:08:31.679> if<01:08:31.799> we<01:08:31.920> ran<01:08:32.219> it<01:08:32.339> it<01:08:32.460> would<01:08:32.640> run 01:08:32.930 --> 01:08:32.940 align:start position:0% this and now if we ran it it would run 01:08:32.940 --> 01:08:36.349 align:start position:0% this and now if we ran it it would run and<01:08:33.420> grab<01:08:33.839> the<01:08:34.380> valid<01:08:34.799> URLs<01:08:35.339> for<01:08:35.640> all<01:08:36.000> of<01:08:36.120> these 01:08:36.349 --> 01:08:36.359 align:start position:0% and grab the valid URLs for all of these 01:08:36.359 --> 01:08:38.450 align:start position:0% and grab the valid URLs for all of these domain<01:08:36.779> all<01:08:37.080> of<01:08:37.199> these<01:08:37.440> subdomains<01:08:38.219> for 01:08:38.450 --> 01:08:38.460 align:start position:0% domain all of these subdomains for 01:08:38.460 --> 01:08:41.269 align:start position:0% domain all of these subdomains for yahoo.com<01:08:39.239> so<01:08:40.140> now<01:08:40.380> that<01:08:40.500> we<01:08:40.620> have<01:08:40.739> that<01:08:40.920> saved 01:08:41.269 --> 01:08:41.279 align:start position:0% yahoo.com so now that we have that saved 01:08:41.279 --> 01:08:42.890 align:start position:0% yahoo.com so now that we have that saved what<01:08:41.520> you<01:08:41.640> would<01:08:41.759> do<01:08:41.940> is<01:08:42.120> you<01:08:42.239> would<01:08:42.420> run<01:08:42.600> this 01:08:42.890 --> 01:08:42.900 align:start position:0% what you would do is you would run this 01:08:42.900 --> 01:08:44.630 align:start position:0% what you would do is you would run this the<01:08:43.380> exact<01:08:43.620> same<01:08:43.799> way<01:08:43.920> you<01:08:44.100> did<01:08:44.279> right<01:08:44.460> here 01:08:44.630 --> 01:08:44.640 align:start position:0% the exact same way you did right here 01:08:44.640 --> 01:08:47.510 align:start position:0% the exact same way you did right here and<01:08:44.940> it<01:08:45.060> would<01:08:45.179> run<01:08:45.420> this<01:08:45.839> way<01:08:46.259> back<01:08:46.500> tool<01:08:46.920> on 01:08:47.510 --> 01:08:47.520 align:start position:0% and it would run this way back tool on 01:08:47.520 --> 01:08:49.189 align:start position:0% and it would run this way back tool on all<01:08:47.759> of<01:08:47.819> those<01:08:48.000> subdomains<01:08:48.660> that<01:08:48.779> we<01:08:48.900> just<01:08:49.020> put 01:08:49.189 --> 01:08:49.199 align:start position:0% all of those subdomains that we just put 01:08:49.199 --> 01:08:51.110 align:start position:0% all of those subdomains that we just put in<01:08:49.380> that<01:08:49.500> file<01:08:49.799> and<01:08:50.279> it<01:08:50.400> would<01:08:50.520> save<01:08:50.699> them<01:08:50.880> over 01:08:51.110 --> 01:08:51.120 align:start position:0% in that file and it would save them over 01:08:51.120 --> 01:08:54.590 align:start position:0% in that file and it would save them over here<01:08:51.359> in<01:08:51.600> the<01:08:51.779> URLs<01:08:52.620> for<01:08:53.400> us<01:08:53.520> so<01:08:54.000> what<01:08:54.239> I<01:08:54.420> want 01:08:54.590 --> 01:08:54.600 align:start position:0% here in the URLs for us so what I want 01:08:54.600 --> 01:08:56.329 align:start position:0% here in the URLs for us so what I want to<01:08:54.719> show<01:08:54.839> you<01:08:55.020> is<01:08:55.199> if<01:08:55.380> we<01:08:55.560> run<01:08:55.739> a<01:08:55.980> word<01:08:56.100> count 01:08:56.329 --> 01:08:56.339 align:start position:0% to show you is if we run a word count 01:08:56.339 --> 01:08:58.610 align:start position:0% to show you is if we run a word count right<01:08:56.580> here<01:08:56.759> on<01:08:56.940> this<01:08:57.060> yahoo.txt<01:08:57.960> it's<01:08:58.440> going 01:08:58.610 --> 01:08:58.620 align:start position:0% right here on this yahoo.txt it's going 01:08:58.620 --> 01:09:00.050 align:start position:0% right here on this yahoo.txt it's going to<01:08:58.679> show<01:08:58.799> us<01:08:58.920> uh<01:08:59.160> that's<01:08:59.460> the<01:08:59.580> file<01:08:59.759> that<01:08:59.940> we 01:09:00.050 --> 01:09:00.060 align:start position:0% to show us uh that's the file that we 01:09:00.060 --> 01:09:02.090 align:start position:0% to show us uh that's the file that we made<01:09:00.239> so<01:09:00.540> we'd<01:09:00.779> want<01:09:00.960> to<01:09:01.080> run<01:09:01.140> it<01:09:01.319> on<01:09:01.500> the<01:09:01.620> URLs 01:09:02.090 --> 01:09:02.100 align:start position:0% made so we'd want to run it on the URLs 01:09:02.100 --> 01:09:04.189 align:start position:0% made so we'd want to run it on the URLs and<01:09:02.400> it'll<01:09:02.759> show<01:09:03.000> us<01:09:03.120> that<01:09:03.299> we<01:09:03.480> have<01:09:03.660> more<01:09:04.020> than 01:09:04.189 --> 01:09:04.199 align:start position:0% and it'll show us that we have more than 01:09:04.199 --> 01:09:05.749 align:start position:0% and it'll show us that we have more than 128 01:09:05.749 --> 01:09:05.759 align:start position:0% 128 01:09:05.759 --> 01:09:08.570 align:start position:0% 128 000<01:09:06.020> valid<01:09:07.020> responses<01:09:07.739> from<01:09:08.100> the<01:09:08.219> way<01:09:08.339> back 01:09:08.570 --> 01:09:08.580 align:start position:0% 000 valid responses from the way back 01:09:08.580 --> 01:09:10.490 align:start position:0% 000 valid responses from the way back tool<01:09:08.940> and<01:09:09.299> we<01:09:09.480> don't<01:09:09.600> necessarily<01:09:10.140> want<01:09:10.380> to 01:09:10.490 --> 01:09:10.500 align:start position:0% tool and we don't necessarily want to 01:09:10.500 --> 01:09:14.809 align:start position:0% tool and we don't necessarily want to visit<01:09:10.920> all<01:09:11.759> of<01:09:12.000> these<01:09:12.359> 100<01:09:12.719> 128<01:09:13.739> 000<01:09:13.859> URLs<01:09:14.460> and 01:09:14.809 --> 01:09:14.819 align:start position:0% visit all of these 100 128 000 URLs and 01:09:14.819 --> 01:09:17.209 align:start position:0% visit all of these 100 128 000 URLs and if<01:09:15.000> we<01:09:15.239> ran<01:09:15.600> the<01:09:15.839> Wayback<01:09:16.199> tool<01:09:16.560> with<01:09:16.859> all<01:09:17.160> of 01:09:17.209 --> 01:09:17.219 align:start position:0% if we ran the Wayback tool with all of 01:09:17.219 --> 01:09:19.189 align:start position:0% if we ran the Wayback tool with all of these<01:09:17.460> subdomains<01:09:18.060> I<01:09:18.480> bet<01:09:18.660> we<01:09:18.839> would<01:09:19.020> have 01:09:19.189 --> 01:09:19.199 align:start position:0% these subdomains I bet we would have 01:09:19.199 --> 01:09:22.430 align:start position:0% these subdomains I bet we would have well<01:09:19.620> over<01:09:19.859> a<01:09:20.699> million<01:09:21.120> different<01:09:21.480> URLs<01:09:22.199> and 01:09:22.430 --> 01:09:22.440 align:start position:0% well over a million different URLs and 01:09:22.440 --> 01:09:23.570 align:start position:0% well over a million different URLs and we<01:09:22.560> don't<01:09:22.620> really<01:09:22.799> want<01:09:22.980> to<01:09:23.100> check<01:09:23.219> all<01:09:23.400> of 01:09:23.570 --> 01:09:23.580 align:start position:0% we don't really want to check all of 01:09:23.580 --> 01:09:25.550 align:start position:0% we don't really want to check all of those<01:09:23.699> so<01:09:24.179> now<01:09:24.359> we<01:09:24.600> want<01:09:24.719> to<01:09:24.900> see<01:09:25.020> which<01:09:25.259> ones 01:09:25.550 --> 01:09:25.560 align:start position:0% those so now we want to see which ones 01:09:25.560 --> 01:09:28.189 align:start position:0% those so now we want to see which ones resolve<01:09:26.100> in<01:09:26.640> order<01:09:26.759> for<01:09:27.239> us<01:09:27.420> to<01:09:27.719> know<01:09:27.900> which 01:09:28.189 --> 01:09:28.199 align:start position:0% resolve in order for us to know which 01:09:28.199 --> 01:09:30.349 align:start position:0% resolve in order for us to know which ones<01:09:28.500> to<01:09:28.679> Target<01:09:29.040> so<01:09:29.460> what<01:09:29.759> we<01:09:29.880> would<01:09:30.000> do<01:09:30.179> at 01:09:30.349 --> 01:09:30.359 align:start position:0% ones to Target so what we would do at 01:09:30.359 --> 01:09:31.849 align:start position:0% ones to Target so what we would do at this<01:09:30.540> point<01:09:30.660> is<01:09:30.839> you're<01:09:31.020> going<01:09:31.140> to<01:09:31.199> run<01:09:31.319> a<01:09:31.500> sudo 01:09:31.849 --> 01:09:31.859 align:start position:0% this point is you're going to run a sudo 01:09:31.859 --> 01:09:34.490 align:start position:0% this point is you're going to run a sudo app<01:09:32.040> install<01:09:32.339> HTTP<01:09:33.239> probe<01:09:33.779> and<01:09:34.080> it's<01:09:34.199> going<01:09:34.380> to 01:09:34.490 --> 01:09:34.500 align:start position:0% app install HTTP probe and it's going to 01:09:34.500 --> 01:09:35.990 align:start position:0% app install HTTP probe and it's going to look<01:09:34.620> like<01:09:34.799> this<01:09:35.040> I<01:09:35.400> already<01:09:35.520> have<01:09:35.819> it 01:09:35.990 --> 01:09:36.000 align:start position:0% look like this I already have it 01:09:36.000 --> 01:09:37.430 align:start position:0% look like this I already have it installed<01:09:36.420> so<01:09:36.600> you<01:09:36.719> can<01:09:36.779> go<01:09:36.839> ahead<01:09:36.960> and<01:09:37.080> run<01:09:37.259> it 01:09:37.430 --> 01:09:37.440 align:start position:0% installed so you can go ahead and run it 01:09:37.440 --> 01:09:39.410 align:start position:0% installed so you can go ahead and run it and<01:09:37.920> then<01:09:38.040> after<01:09:38.400> you<01:09:38.699> run<01:09:38.819> it<01:09:39.000> you<01:09:39.179> can<01:09:39.299> type 01:09:39.410 --> 01:09:39.420 align:start position:0% and then after you run it you can type 01:09:39.420 --> 01:09:41.450 align:start position:0% and then after you run it you can type in<01:09:39.660> HTTP<01:09:40.319> probe<01:09:40.739> to<01:09:40.859> make<01:09:41.040> sure<01:09:41.160> that<01:09:41.339> it's 01:09:41.450 --> 01:09:41.460 align:start position:0% in HTTP probe to make sure that it's 01:09:41.460 --> 01:09:44.090 align:start position:0% in HTTP probe to make sure that it's installed<01:09:41.940> and<01:09:42.179> it<01:09:42.359> should<01:09:42.480> turn<01:09:42.900> blue<01:09:43.380> for 01:09:44.090 --> 01:09:44.100 align:start position:0% installed and it should turn blue for 01:09:44.100 --> 01:09:46.370 align:start position:0% installed and it should turn blue for you<01:09:44.339> just<01:09:44.699> like<01:09:44.880> this<01:09:45.060> and<01:09:45.420> the<01:09:45.719> way<01:09:45.779> we<01:09:45.960> run<01:09:46.140> it 01:09:46.370 --> 01:09:46.380 align:start position:0% you just like this and the way we run it 01:09:46.380 --> 01:09:49.010 align:start position:0% you just like this and the way we run it is<01:09:46.620> the<01:09:46.980> same<01:09:47.100> way<01:09:47.279> we<01:09:47.699> would<01:09:47.880> run<01:09:48.120> the<01:09:48.660> way 01:09:49.010 --> 01:09:49.020 align:start position:0% is the same way we would run the way 01:09:49.020 --> 01:09:50.990 align:start position:0% is the same way we would run the way back<01:09:49.259> just<01:09:49.560> like<01:09:49.739> this<01:09:49.980> so<01:09:50.400> we're<01:09:50.580> going<01:09:50.759> to<01:09:50.819> go 01:09:50.990 --> 01:09:51.000 align:start position:0% back just like this so we're going to go 01:09:51.000 --> 01:09:53.650 align:start position:0% back just like this so we're going to go ahead<01:09:51.179> and<01:09:51.540> cut<01:09:51.839> out<01:09:52.140> our<01:09:52.620> Yahoo 01:09:53.650 --> 01:09:53.660 align:start position:0% ahead and cut out our Yahoo 01:09:53.660 --> 01:09:56.689 align:start position:0% ahead and cut out our Yahoo URLs<01:09:54.660> just<01:09:55.020> like<01:09:55.199> this<01:09:55.440> and<01:09:56.280> I'm<01:09:56.460> going<01:09:56.580> to 01:09:56.689 --> 01:09:56.699 align:start position:0% URLs just like this and I'm going to 01:09:56.699 --> 01:09:58.610 align:start position:0% URLs just like this and I'm going to actually<01:09:56.820> delete<01:09:57.060> the<01:09:57.300> valid<01:09:57.600> URLs<01:09:58.140> and<01:09:58.440> you 01:09:58.610 --> 01:09:58.620 align:start position:0% actually delete the valid URLs and you 01:09:58.620 --> 01:10:00.590 align:start position:0% actually delete the valid URLs and you can<01:09:58.679> save<01:09:58.860> it<01:09:59.040> into<01:09:59.160> an<01:09:59.340> out<01:09:59.460> file<01:09:59.760> if<01:10:00.120> you<01:10:00.360> want 01:10:00.590 --> 01:10:00.600 align:start position:0% can save it into an out file if you want 01:10:00.600 --> 01:10:01.790 align:start position:0% can save it into an out file if you want I'm<01:10:00.840> not<01:10:01.020> going<01:10:01.140> to<01:10:01.260> I'm<01:10:01.440> just<01:10:01.560> going<01:10:01.679> to<01:10:01.679> let 01:10:01.790 --> 01:10:01.800 align:start position:0% I'm not going to I'm just going to let 01:10:01.800 --> 01:10:03.350 align:start position:0% I'm not going to I'm just going to let it<01:10:01.920> spit<01:10:02.100> out<01:10:02.219> to<01:10:02.460> the<01:10:02.699> console<01:10:03.060> and<01:10:03.239> then 01:10:03.350 --> 01:10:03.360 align:start position:0% it spit out to the console and then 01:10:03.360 --> 01:10:05.689 align:start position:0% it spit out to the console and then cancel<01:10:03.660> it<01:10:03.900> and<01:10:04.260> so<01:10:04.440> we<01:10:04.620> would<01:10:04.739> go<01:10:04.980> ahead<01:10:05.160> and 01:10:05.689 --> 01:10:05.699 align:start position:0% cancel it and so we would go ahead and 01:10:05.699 --> 01:10:09.110 align:start position:0% cancel it and so we would go ahead and run<01:10:06.179> this<01:10:06.420> and<01:10:06.900> I<01:10:07.140> think<01:10:07.260> this<01:10:07.500> is<01:10:07.880> URLs<01:10:08.880> with 01:10:09.110 --> 01:10:09.120 align:start position:0% run this and I think this is URLs with 01:10:09.120 --> 01:10:11.450 align:start position:0% run this and I think this is URLs with an<01:10:09.300> S<01:10:09.480> like<01:10:10.260> that<01:10:10.500> and<01:10:10.920> it's<01:10:11.100> going<01:10:11.280> to<01:10:11.340> go 01:10:11.450 --> 01:10:11.460 align:start position:0% an S like that and it's going to go 01:10:11.460 --> 01:10:13.430 align:start position:0% an S like that and it's going to go ahead<01:10:11.580> and<01:10:11.699> start<01:10:11.940> running<01:10:12.239> this<01:10:12.660> all<01:10:13.320> of 01:10:13.430 --> 01:10:13.440 align:start position:0% ahead and start running this all of 01:10:13.440 --> 01:10:15.650 align:start position:0% ahead and start running this all of those<01:10:13.800> 128 01:10:15.650 --> 01:10:15.660 align:start position:0% those 128 01:10:15.660 --> 01:10:18.350 align:start position:0% those 128 000<01:10:15.840> URLs<01:10:16.739> that<01:10:17.160> we<01:10:17.460> pulled<01:10:17.940> down<01:10:18.000> from<01:10:18.239> up 01:10:18.350 --> 01:10:18.360 align:start position:0% 000 URLs that we pulled down from up 01:10:18.360 --> 01:10:20.209 align:start position:0% 000 URLs that we pulled down from up here<01:10:18.540> and<01:10:18.960> it's<01:10:19.080> going<01:10:19.320> to<01:10:19.440> start<01:10:19.620> printing 01:10:20.209 --> 01:10:20.219 align:start position:0% here and it's going to start printing 01:10:20.219 --> 01:10:22.490 align:start position:0% here and it's going to start printing the<01:10:20.340> valid<01:10:20.699> ones<01:10:20.940> out<01:10:21.179> down<01:10:21.659> here<01:10:21.840> in<01:10:22.199> the 01:10:22.490 --> 01:10:22.500 align:start position:0% the valid ones out down here in the 01:10:22.500 --> 01:10:24.229 align:start position:0% the valid ones out down here in the terminal<01:10:22.800> for<01:10:23.520> us<01:10:23.640> I'm<01:10:23.940> going<01:10:24.060> to<01:10:24.120> go<01:10:24.179> ahead 01:10:24.229 --> 01:10:24.239 align:start position:0% terminal for us I'm going to go ahead 01:10:24.239 --> 01:10:25.729 align:start position:0% terminal for us I'm going to go ahead and<01:10:24.300> cancel<01:10:24.480> that<01:10:24.659> the<01:10:24.840> valid<01:10:25.080> URLs<01:10:25.560> are<01:10:25.620> going 01:10:25.729 --> 01:10:25.739 align:start position:0% and cancel that the valid URLs are going 01:10:25.739 --> 01:10:28.070 align:start position:0% and cancel that the valid URLs are going to<01:10:25.800> get<01:10:25.920> printed<01:10:26.280> out<01:10:26.460> just<01:10:27.060> like<01:10:27.300> this<01:10:27.540> into 01:10:28.070 --> 01:10:28.080 align:start position:0% to get printed out just like this into 01:10:28.080 --> 01:10:30.169 align:start position:0% to get printed out just like this into the<01:10:28.800> terminal<01:10:29.159> or<01:10:29.400> you<01:10:29.580> could<01:10:29.699> save<01:10:29.820> them<01:10:30.000> into 01:10:30.169 --> 01:10:30.179 align:start position:0% the terminal or you could save them into 01:10:30.179 --> 01:10:32.450 align:start position:0% the terminal or you could save them into an<01:10:30.360> out<01:10:30.480> file<01:10:30.780> and<01:10:31.320> then<01:10:31.440> once<01:10:31.920> you<01:10:32.040> have<01:10:32.219> the 01:10:32.450 --> 01:10:32.460 align:start position:0% an out file and then once you have the 01:10:32.460 --> 01:10:34.310 align:start position:0% an out file and then once you have the valid<01:10:32.760> URLs<01:10:33.120> you<01:10:33.300> can<01:10:33.420> start<01:10:33.600> to<01:10:33.840> look<01:10:34.020> through 01:10:34.310 --> 01:10:34.320 align:start position:0% valid URLs you can start to look through 01:10:34.320 --> 01:10:36.950 align:start position:0% valid URLs you can start to look through which<01:10:34.739> ones<01:10:35.100> you<01:10:35.699> think<01:10:35.940> are<01:10:36.179> juicy<01:10:36.540> and<01:10:36.780> you 01:10:36.950 --> 01:10:36.960 align:start position:0% which ones you think are juicy and you 01:10:36.960 --> 01:10:39.950 align:start position:0% which ones you think are juicy and you want<01:10:37.140> to<01:10:37.380> Target<01:10:37.880> one<01:10:38.880> other<01:10:39.000> thing<01:10:39.300> I<01:10:39.600> want<01:10:39.780> to 01:10:39.950 --> 01:10:39.960 align:start position:0% want to Target one other thing I want to 01:10:39.960 --> 01:10:44.270 align:start position:0% want to Target one other thing I want to show<01:10:40.440> you<01:10:40.560> is<01:10:40.860> if<01:10:41.040> we<01:10:41.219> type<01:10:41.400> in<01:10:41.640> our<01:10:42.239> HTTP<01:10:43.280> robe 01:10:44.270 --> 01:10:44.280 align:start position:0% show you is if we type in our HTTP robe 01:10:44.280 --> 01:10:47.030 align:start position:0% show you is if we type in our HTTP robe just<01:10:44.400> like<01:10:44.580> this<01:10:44.760> it'll<01:10:45.360> be<01:10:45.480> run<01:10:45.600> a<01:10:45.900> Das<01:10:46.320> H<01:10:46.560> just 01:10:47.030 --> 01:10:47.040 align:start position:0% just like this it'll be run a Das H just 01:10:47.040 --> 01:10:49.850 align:start position:0% just like this it'll be run a Das H just like<01:10:47.280> this<01:10:47.520> you<01:10:48.179> can<01:10:48.300> start<01:10:48.719> to<01:10:49.080> see<01:10:49.440> if<01:10:49.800> you 01:10:49.850 --> 01:10:49.860 align:start position:0% like this you can start to see if you 01:10:49.860 --> 01:10:51.590 align:start position:0% like this you can start to see if you want<01:10:49.980> to<01:10:50.159> give<01:10:50.219> them<01:10:50.460> a<01:10:50.820> timeout<01:10:51.179> in 01:10:51.590 --> 01:10:51.600 align:start position:0% want to give them a timeout in 01:10:51.600 --> 01:10:53.450 align:start position:0% want to give them a timeout in milliseconds<01:10:52.380> so<01:10:52.800> I<01:10:52.920> think<01:10:53.040> there's<01:10:53.280> a 01:10:53.450 --> 01:10:53.460 align:start position:0% milliseconds so I think there's a 01:10:53.460 --> 01:10:55.490 align:start position:0% milliseconds so I think there's a thousand<01:10:53.760> milliseconds<01:10:54.360> in<01:10:54.719> a<01:10:54.840> second<01:10:55.020> so<01:10:55.320> if 01:10:55.490 --> 01:10:55.500 align:start position:0% thousand milliseconds in a second so if 01:10:55.500 --> 01:10:57.950 align:start position:0% thousand milliseconds in a second so if you<01:10:55.679> wanted<01:10:55.860> to<01:10:56.040> run<01:10:56.219> an<01:10:56.460> HTTP<01:10:57.060> probe<01:10:57.540> and<01:10:57.780> you 01:10:57.950 --> 01:10:57.960 align:start position:0% you wanted to run an HTTP probe and you 01:10:57.960 --> 01:11:01.370 align:start position:0% you wanted to run an HTTP probe and you didn't<01:10:58.080> actually<01:10:58.440> want<01:10:58.860> to<01:10:59.280> wait<01:11:00.120> for<01:11:00.780> it<01:11:01.140> to 01:11:01.370 --> 01:11:01.380 align:start position:0% didn't actually want to wait for it to 01:11:01.380 --> 01:11:03.649 align:start position:0% didn't actually want to wait for it to try<01:11:01.679> and<01:11:01.800> resolve<01:11:02.219> each<01:11:02.400> one<01:11:02.580> for<01:11:03.000> the<01:11:03.300> default 01:11:03.649 --> 01:11:03.659 align:start position:0% try and resolve each one for the default 01:11:03.659 --> 01:11:05.390 align:start position:0% try and resolve each one for the default of<01:11:03.900> 10<01:11:04.140> seconds<01:11:04.380> which<01:11:04.739> is<01:11:04.800> kind<01:11:04.980> of<01:11:05.100> a<01:11:05.280> long 01:11:05.390 --> 01:11:05.400 align:start position:0% of 10 seconds which is kind of a long 01:11:05.400 --> 01:11:07.430 align:start position:0% of 10 seconds which is kind of a long time<01:11:05.580> you<01:11:06.120> could<01:11:06.179> change<01:11:06.420> this<01:11:06.719> and<01:11:07.020> see<01:11:07.199> if 01:11:07.430 --> 01:11:07.440 align:start position:0% time you could change this and see if 01:11:07.440 --> 01:11:10.189 align:start position:0% time you could change this and see if the<01:11:07.800> web<01:11:08.219> URL<01:11:08.940> resolves<01:11:09.540> in<01:11:09.780> like<01:11:09.900> a<01:11:10.080> second 01:11:10.189 --> 01:11:10.199 align:start position:0% the web URL resolves in like a second 01:11:10.199 --> 01:11:12.290 align:start position:0% the web URL resolves in like a second that's<01:11:10.620> probably<01:11:10.860> what<01:11:11.219> I<01:11:11.400> would<01:11:11.520> do<01:11:11.699> so<01:11:12.179> I 01:11:12.290 --> 01:11:12.300 align:start position:0% that's probably what I would do so I 01:11:12.300 --> 01:11:15.290 align:start position:0% that's probably what I would do so I would<01:11:12.420> run<01:11:12.600> a<01:11:13.140> dash<01:11:13.440> T<01:11:13.679> and<01:11:13.980> I<01:11:14.159> would<01:11:14.280> say<01:11:14.400> 1000 01:11:15.290 --> 01:11:15.300 align:start position:0% would run a dash T and I would say 1000 01:11:15.300 --> 01:11:16.910 align:start position:0% would run a dash T and I would say 1000 instead<01:11:15.600> of<01:11:15.719> ten<01:11:15.960> thousand<01:11:16.199> suddenly<01:11:16.679> it<01:11:16.800> only 01:11:16.910 --> 01:11:16.920 align:start position:0% instead of ten thousand suddenly it only 01:11:16.920 --> 01:11:19.010 align:start position:0% instead of ten thousand suddenly it only takes<01:11:17.159> a<01:11:17.340> second<01:11:17.460> before<01:11:18.060> it<01:11:18.300> moves<01:11:18.600> on<01:11:18.719> to<01:11:18.900> the 01:11:19.010 --> 01:11:19.020 align:start position:0% takes a second before it moves on to the 01:11:19.020 --> 01:11:21.470 align:start position:0% takes a second before it moves on to the next<01:11:19.199> URL<01:11:19.679> so<01:11:19.860> if<01:11:19.980> it<01:11:20.159> went<01:11:20.340> to<01:11:20.520> this<01:11:20.880> URL<01:11:21.239> and 01:11:21.470 --> 01:11:21.480 align:start position:0% next URL so if it went to this URL and 01:11:21.480 --> 01:11:23.870 align:start position:0% next URL so if it went to this URL and it<01:11:21.659> didn't<01:11:21.840> resolve<01:11:22.320> by<01:11:22.980> default<01:11:23.340> it's<01:11:23.699> going 01:11:23.870 --> 01:11:23.880 align:start position:0% it didn't resolve by default it's going 01:11:23.880 --> 01:11:26.390 align:start position:0% it didn't resolve by default it's going to<01:11:23.940> wait<01:11:24.060> 10<01:11:24.480> seconds<01:11:24.780> to<01:11:25.320> go<01:11:25.440> to<01:11:25.560> the<01:11:25.739> next<01:11:25.860> URL 01:11:26.390 --> 01:11:26.400 align:start position:0% to wait 10 seconds to go to the next URL 01:11:26.400 --> 01:11:28.490 align:start position:0% to wait 10 seconds to go to the next URL and<01:11:26.760> if<01:11:26.940> you're<01:11:27.060> running<01:11:27.239> over<01:11:27.600> a<01:11:28.080> million 01:11:28.490 --> 01:11:28.500 align:start position:0% and if you're running over a million 01:11:28.500 --> 01:11:30.530 align:start position:0% and if you're running over a million subdomains<01:11:29.159> that's<01:11:29.280> going<01:11:29.520> to<01:11:29.580> take<01:11:29.760> forever 01:11:30.530 --> 01:11:30.540 align:start position:0% subdomains that's going to take forever 01:11:30.540 --> 01:11:32.270 align:start position:0% subdomains that's going to take forever especially<01:11:31.260> because<01:11:31.440> a<01:11:31.739> lot<01:11:31.800> of<01:11:31.920> them<01:11:32.040> are 01:11:32.270 --> 01:11:32.280 align:start position:0% especially because a lot of them are 01:11:32.280 --> 01:11:34.010 align:start position:0% especially because a lot of them are really<01:11:32.460> old<01:11:32.640> and<01:11:33.000> are<01:11:33.120> not<01:11:33.300> going<01:11:33.480> to<01:11:33.600> resolve 01:11:34.010 --> 01:11:34.020 align:start position:0% really old and are not going to resolve 01:11:34.020 --> 01:11:36.110 align:start position:0% really old and are not going to resolve so<01:11:34.500> I<01:11:34.679> would<01:11:34.800> run<01:11:34.980> it<01:11:35.159> with<01:11:35.340> a<01:11:35.520> thousand<01:11:35.699> subtle 01:11:36.110 --> 01:11:36.120 align:start position:0% so I would run it with a thousand subtle 01:11:36.120 --> 01:11:38.330 align:start position:0% so I would run it with a thousand subtle way<01:11:36.239> to<01:11:36.360> one<01:11:36.600> second<01:11:36.780> so<01:11:37.260> if<01:11:37.560> this<01:11:37.920> did<01:11:38.159> not 01:11:38.330 --> 01:11:38.340 align:start position:0% way to one second so if this did not 01:11:38.340 --> 01:11:40.070 align:start position:0% way to one second so if this did not resolve<01:11:38.820> within<01:11:39.179> a<01:11:39.300> second<01:11:39.420> it's<01:11:39.719> going<01:11:39.900> to<01:11:39.960> go 01:11:40.070 --> 01:11:40.080 align:start position:0% resolve within a second it's going to go 01:11:40.080 --> 01:11:42.410 align:start position:0% resolve within a second it's going to go ahead<01:11:40.199> and<01:11:40.320> go<01:11:40.620> to<01:11:40.800> the<01:11:41.280> next<01:11:41.400> one<01:11:41.640> so<01:11:42.000> this<01:11:42.239> is 01:11:42.410 --> 01:11:42.420 align:start position:0% ahead and go to the next one so this is 01:11:42.420 --> 01:11:44.390 align:start position:0% ahead and go to the next one so this is one<01:11:42.659> of<01:11:42.780> the<01:11:42.840> most<01:11:43.140> comprehensive<01:11:43.800> ways<01:11:44.219> to 01:11:44.390 --> 01:11:44.400 align:start position:0% one of the most comprehensive ways to 01:11:44.400 --> 01:11:47.090 align:start position:0% one of the most comprehensive ways to pull<01:11:44.580> down<01:11:44.820> the<01:11:45.239> max<01:11:45.540> number<01:11:45.900> of<01:11:46.140> URLs<01:11:46.860> for<01:11:46.980> you 01:11:47.090 --> 01:11:47.100 align:start position:0% pull down the max number of URLs for you 01:11:47.100 --> 01:11:49.370 align:start position:0% pull down the max number of URLs for you to<01:11:47.219> Target<01:11:47.340> within<01:11:47.820> a<01:11:48.000> bug<01:11:48.239> Bounty<01:11:48.719> program<01:11:48.840> in 01:11:49.370 --> 01:11:49.380 align:start position:0% to Target within a bug Bounty program in 01:11:49.380 --> 01:11:50.450 align:start position:0% to Target within a bug Bounty program in this<01:11:49.440> video<01:11:49.560> I'm<01:11:49.800> going<01:11:49.920> to<01:11:49.980> show<01:11:50.100> you<01:11:50.159> how<01:11:50.340> to 01:11:50.450 --> 01:11:50.460 align:start position:0% this video I'm going to show you how to 01:11:50.460 --> 01:11:51.709 align:start position:0% this video I'm going to show you how to find<01:11:50.580> the<01:11:50.760> subdomains<01:11:51.300> which<01:11:51.480> are<01:11:51.600> going<01:11:51.659> to 01:11:51.709 --> 01:11:51.719 align:start position:0% find the subdomains which are going to 01:11:51.719 --> 01:11:53.270 align:start position:0% find the subdomains which are going to be<01:11:51.840> really<01:11:52.020> important<01:11:52.380> for<01:11:52.560> you<01:11:52.679> if<01:11:52.980> you<01:11:53.159> do 01:11:53.270 --> 01:11:53.280 align:start position:0% be really important for you if you do 01:11:53.280 --> 01:11:55.130 align:start position:0% be really important for you if you do any<01:11:53.580> kind<01:11:53.760> of<01:11:53.880> bug<01:11:54.300> money<01:11:54.540> hunting<01:11:54.960> or 01:11:55.130 --> 01:11:55.140 align:start position:0% any kind of bug money hunting or 01:11:55.140 --> 01:11:57.110 align:start position:0% any kind of bug money hunting or penetration<01:11:55.620> testing<01:11:56.100> because<01:11:56.340> subdomains 01:11:57.110 --> 01:11:57.120 align:start position:0% penetration testing because subdomains 01:11:57.120 --> 01:11:59.330 align:start position:0% penetration testing because subdomains are<01:11:57.239> usually<01:11:57.480> targeted<01:11:57.960> at<01:11:58.199> the<01:11:58.679> least<01:11:58.920> and 01:11:59.330 --> 01:11:59.340 align:start position:0% are usually targeted at the least and 01:11:59.340 --> 01:12:01.310 align:start position:0% are usually targeted at the least and usually<01:11:59.640> what<01:11:59.820> happens<01:12:00.000> is<01:12:00.540> beginners<01:12:01.140> just 01:12:01.310 --> 01:12:01.320 align:start position:0% usually what happens is beginners just 01:12:01.320 --> 01:12:03.410 align:start position:0% usually what happens is beginners just log<01:12:01.560> into<01:12:01.739> the<01:12:02.280> main<01:12:02.460> page<01:12:02.760> and<01:12:02.940> try<01:12:03.060> and<01:12:03.239> hack 01:12:03.410 --> 01:12:03.420 align:start position:0% log into the main page and try and hack 01:12:03.420 --> 01:12:05.270 align:start position:0% log into the main page and try and hack on<01:12:03.600> the<01:12:03.719> main<01:12:03.900> page<01:12:04.199> and<01:12:04.739> it<01:12:04.920> doesn't<01:12:05.040> really 01:12:05.270 --> 01:12:05.280 align:start position:0% on the main page and it doesn't really 01:12:05.280 --> 01:12:06.649 align:start position:0% on the main page and it doesn't really work<01:12:05.460> out<01:12:05.640> for<01:12:05.820> them<01:12:05.880> and<01:12:06.060> they<01:12:06.239> become<01:12:06.480> really 01:12:06.649 --> 01:12:06.659 align:start position:0% work out for them and they become really 01:12:06.659 --> 01:12:08.390 align:start position:0% work out for them and they become really frustrated<01:12:07.140> so<01:12:07.440> let's<01:12:07.560> go<01:12:07.739> ahead<01:12:07.860> and<01:12:08.100> jump 01:12:08.390 --> 01:12:08.400 align:start position:0% frustrated so let's go ahead and jump 01:12:08.400 --> 01:12:10.130 align:start position:0% frustrated so let's go ahead and jump into<01:12:08.580> it<01:12:08.760> okay<01:12:09.000> so<01:12:09.239> here<01:12:09.360> we<01:12:09.540> are<01:12:09.659> we<01:12:09.960> have 01:12:10.130 --> 01:12:10.140 align:start position:0% into it okay so here we are we have 01:12:10.140 --> 01:12:12.229 align:start position:0% into it okay so here we are we have opened<01:12:10.560> up<01:12:10.679> a<01:12:10.860> terminal<01:12:11.340> and<01:12:11.940> you're<01:12:12.060> going<01:12:12.179> to 01:12:12.229 --> 01:12:12.239 align:start position:0% opened up a terminal and you're going to 01:12:12.239 --> 01:12:14.510 align:start position:0% opened up a terminal and you're going to go<01:12:12.300> ahead<01:12:12.420> and<01:12:12.540> and<01:12:13.020> sudo<01:12:13.620> apt<01:12:13.920> update<01:12:14.280> and 01:12:14.510 --> 01:12:14.520 align:start position:0% go ahead and and sudo apt update and 01:12:14.520 --> 01:12:16.490 align:start position:0% go ahead and and sudo apt update and then<01:12:14.640> you're<01:12:14.760> going<01:12:14.880> to<01:12:15.120> type<01:12:15.300> in<01:12:15.540> sudo<01:12:16.140> apt 01:12:16.490 --> 01:12:16.500 align:start position:0% then you're going to type in sudo apt 01:12:16.500 --> 01:12:18.410 align:start position:0% then you're going to type in sudo apt install<01:12:16.679> sublister<01:12:17.520> I<01:12:17.880> just<01:12:18.060> want<01:12:18.239> to<01:12:18.300> show 01:12:18.410 --> 01:12:18.420 align:start position:0% install sublister I just want to show 01:12:18.420 --> 01:12:19.850 align:start position:0% install sublister I just want to show you<01:12:18.540> sublister<01:12:19.140> because<01:12:19.320> it's<01:12:19.620> really 01:12:19.850 --> 01:12:19.860 align:start position:0% you sublister because it's really 01:12:19.860 --> 01:12:22.310 align:start position:0% you sublister because it's really popular<01:12:20.219> and<01:12:20.820> I<01:12:20.940> used<01:12:21.060> to<01:12:21.239> use<01:12:21.360> it<01:12:21.540> a<01:12:21.900> lot<01:12:22.020> but 01:12:22.310 --> 01:12:22.320 align:start position:0% popular and I used to use it a lot but 01:12:22.320 --> 01:12:23.810 align:start position:0% popular and I used to use it a lot but I've<01:12:22.679> really<01:12:22.860> stopped<01:12:23.219> recently<01:12:23.580> because 01:12:23.810 --> 01:12:23.820 align:start position:0% I've really stopped recently because 01:12:23.820 --> 01:12:25.669 align:start position:0% I've really stopped recently because it's<01:12:24.120> not<01:12:24.239> pulling<01:12:24.600> down<01:12:24.719> as<01:12:24.900> many<01:12:25.080> domains<01:12:25.500> as 01:12:25.669 --> 01:12:25.679 align:start position:0% it's not pulling down as many domains as 01:12:25.679 --> 01:12:27.110 align:start position:0% it's not pulling down as many domains as I<01:12:25.980> would<01:12:26.100> like<01:12:26.219> so<01:12:26.460> if<01:12:26.580> we<01:12:26.699> just<01:12:26.820> type<01:12:26.940> in 01:12:27.110 --> 01:12:27.120 align:start position:0% I would like so if we just type in 01:12:27.120 --> 01:12:28.970 align:start position:0% I would like so if we just type in something<01:12:27.360> like<01:12:27.679> sublister<01:12:28.679> and<01:12:28.860> then 01:12:28.970 --> 01:12:28.980 align:start position:0% something like sublister and then 01:12:28.980 --> 01:12:31.310 align:start position:0% something like sublister and then yahoo.com<01:12:29.640> we'll<01:12:30.239> see<01:12:30.540> what<01:12:30.780> it<01:12:30.900> pulls<01:12:31.199> down 01:12:31.310 --> 01:12:31.320 align:start position:0% yahoo.com we'll see what it pulls down 01:12:31.320 --> 01:12:34.430 align:start position:0% yahoo.com we'll see what it pulls down so<01:12:31.739> you'll<01:12:31.980> type<01:12:32.100> in<01:12:32.280> sublister<01:12:33.120> Dash<01:12:33.900> D<01:12:34.140> for 01:12:34.430 --> 01:12:34.440 align:start position:0% so you'll type in sublister Dash D for 01:12:34.440 --> 01:12:36.110 align:start position:0% so you'll type in sublister Dash D for the<01:12:34.620> domain<01:12:34.920> actually<01:12:35.280> we<01:12:35.580> can<01:12:35.699> type<01:12:35.820> in<01:12:35.940> a 01:12:36.110 --> 01:12:36.120 align:start position:0% the domain actually we can type in a 01:12:36.120 --> 01:12:38.330 align:start position:0% the domain actually we can type in a dash<01:12:36.300> H<01:12:36.480> for<01:12:36.719> help<01:12:36.960> and<01:12:37.440> you<01:12:37.500> can<01:12:37.679> see<01:12:37.860> what<01:12:38.159> all 01:12:38.330 --> 01:12:38.340 align:start position:0% dash H for help and you can see what all 01:12:38.340 --> 01:12:39.770 align:start position:0% dash H for help and you can see what all it's<01:12:38.520> able<01:12:38.820> to<01:12:38.880> do<01:12:39.060> so<01:12:39.300> we're<01:12:39.420> going<01:12:39.540> to<01:12:39.600> type 01:12:39.770 --> 01:12:39.780 align:start position:0% it's able to do so we're going to type 01:12:39.780 --> 01:12:42.890 align:start position:0% it's able to do so we're going to type in<01:12:40.020> a<01:12:40.560> sublister<01:12:41.340> Dash<01:12:41.760> D<01:12:42.000> and<01:12:42.659> then<01:12:42.719> we'll 01:12:42.890 --> 01:12:42.900 align:start position:0% in a sublister Dash D and then we'll 01:12:42.900 --> 01:12:45.649 align:start position:0% in a sublister Dash D and then we'll just<01:12:43.020> type<01:12:43.199> in<01:12:43.400> yahoo.com<01:12:44.400> and<01:12:45.239> it's<01:12:45.420> going<01:12:45.600> to 01:12:45.649 --> 01:12:45.659 align:start position:0% just type in yahoo.com and it's going to 01:12:45.659 --> 01:12:47.270 align:start position:0% just type in yahoo.com and it's going to go<01:12:45.840> out<01:12:46.020> and<01:12:46.380> search<01:12:46.620> all<01:12:46.920> these<01:12:47.100> different 01:12:47.270 --> 01:12:47.280 align:start position:0% go out and search all these different 01:12:47.280 --> 01:12:49.729 align:start position:0% go out and search all these different search<01:12:47.520> engines<01:12:47.940> and<01:12:48.480> then<01:12:48.600> bring<01:12:49.020> back<01:12:49.260> the 01:12:49.729 --> 01:12:49.739 align:start position:0% search engines and then bring back the 01:12:49.739 --> 01:12:51.649 align:start position:0% search engines and then bring back the results<01:12:50.040> and<01:12:50.460> remember<01:12:50.640> when<01:12:51.000> you<01:12:51.179> see<01:12:51.360> all<01:12:51.540> of 01:12:51.649 --> 01:12:51.659 align:start position:0% results and remember when you see all of 01:12:51.659 --> 01:12:52.970 align:start position:0% results and remember when you see all of these<01:12:51.840> subdomains<01:12:52.380> that<01:12:52.500> it<01:12:52.620> brings<01:12:52.800> back 01:12:52.970 --> 01:12:52.980 align:start position:0% these subdomains that it brings back 01:12:52.980 --> 01:12:55.010 align:start position:0% these subdomains that it brings back that<01:12:53.640> you<01:12:53.820> need<01:12:53.880> to<01:12:54.120> check<01:12:54.420> to<01:12:54.659> make<01:12:54.780> sure 01:12:55.010 --> 01:12:55.020 align:start position:0% that you need to check to make sure 01:12:55.020 --> 01:12:56.990 align:start position:0% that you need to check to make sure they're<01:12:55.440> in<01:12:55.620> scope<01:12:55.920> sometimes<01:12:56.400> I'll<01:12:56.699> show<01:12:56.880> you 01:12:56.990 --> 01:12:57.000 align:start position:0% they're in scope sometimes I'll show you 01:12:57.000 --> 01:13:00.169 align:start position:0% they're in scope sometimes I'll show you what<01:12:57.120> I<01:12:57.300> do<01:12:57.420> is<01:12:57.960> I<01:12:58.500> just<01:12:58.679> open<01:12:59.219> this<01:12:59.520> up<01:12:59.760> and 01:13:00.169 --> 01:13:00.179 align:start position:0% what I do is I just open this up and 01:13:00.179 --> 01:13:01.669 align:start position:0% what I do is I just open this up and I'll<01:13:00.300> be<01:13:00.480> like<01:13:00.540> okay<01:13:00.719> here's<01:13:01.140> a<01:13:01.199> subdomain 01:13:01.669 --> 01:13:01.679 align:start position:0% I'll be like okay here's a subdomain 01:13:01.679 --> 01:13:03.169 align:start position:0% I'll be like okay here's a subdomain here's<01:13:01.980> a<01:13:02.100> subdomain<01:13:02.580> and<01:13:02.760> let's<01:13:02.880> go<01:13:03.060> through 01:13:03.169 --> 01:13:03.179 align:start position:0% here's a subdomain and let's go through 01:13:03.179 --> 01:13:06.410 align:start position:0% here's a subdomain and let's go through these<01:13:03.480> subdomains<01:13:04.199> and<01:13:04.920> I'll<01:13:05.100> show<01:13:05.400> you<01:13:05.580> what 01:13:06.410 --> 01:13:06.420 align:start position:0% these subdomains and I'll show you what 01:13:06.420 --> 01:13:08.570 align:start position:0% these subdomains and I'll show you what I<01:13:06.540> think<01:13:06.659> is<01:13:06.840> the<01:13:07.020> best<01:13:07.140> way<01:13:07.320> to<01:13:07.500> do<01:13:07.620> this<01:13:07.800> so<01:13:08.400> if 01:13:08.570 --> 01:13:08.580 align:start position:0% I think is the best way to do this so if 01:13:08.580 --> 01:13:09.890 align:start position:0% I think is the best way to do this so if you're<01:13:08.699> in<01:13:08.880> Firefox<01:13:09.300> you're<01:13:09.600> going<01:13:09.719> to<01:13:09.840> want 01:13:09.890 --> 01:13:09.900 align:start position:0% you're in Firefox you're going to want 01:13:09.900 --> 01:13:12.530 align:start position:0% you're in Firefox you're going to want to<01:13:10.020> download<01:13:10.260> something<01:13:10.620> called<01:13:11.040> open<01:13:11.940> list 01:13:12.530 --> 01:13:12.540 align:start position:0% to download something called open list 01:13:12.540 --> 01:13:16.370 align:start position:0% to download something called open list plugin<01:13:13.320> and<01:13:14.100> we<01:13:14.760> want<01:13:14.940> it<01:13:15.179> on 01:13:16.370 --> 01:13:16.380 align:start position:0% plugin and we want it on 01:13:16.380 --> 01:13:20.090 align:start position:0% plugin and we want it on Firefox 01:13:20.090 --> 01:13:20.100 align:start position:0% 01:13:20.100 --> 01:13:23.090 align:start position:0% so<01:13:20.400> we'll<01:13:20.580> just<01:13:20.760> go<01:13:20.880> ahead<01:13:21.120> and<01:13:22.020> add<01:13:22.380> this<01:13:22.679> and 01:13:23.090 --> 01:13:23.100 align:start position:0% so we'll just go ahead and add this and 01:13:23.100 --> 01:13:24.530 align:start position:0% so we'll just go ahead and add this and it's<01:13:23.340> telling<01:13:23.640> you<01:13:23.699> right<01:13:23.880> here<01:13:24.060> what<01:13:24.239> this<01:13:24.420> is 01:13:24.530 --> 01:13:24.540 align:start position:0% it's telling you right here what this is 01:13:24.540 --> 01:13:26.030 align:start position:0% it's telling you right here what this is going<01:13:24.659> to<01:13:24.719> do<01:13:24.840> it's<01:13:25.020> going<01:13:25.199> to<01:13:25.199> open<01:13:25.380> multiple 01:13:26.030 --> 01:13:26.040 align:start position:0% going to do it's going to open multiple 01:13:26.040 --> 01:13:28.970 align:start position:0% going to do it's going to open multiple URLs<01:13:26.880> at<01:13:27.480> a<01:13:27.600> time<01:13:27.780> which<01:13:28.140> becomes<01:13:28.679> really 01:13:28.970 --> 01:13:28.980 align:start position:0% URLs at a time which becomes really 01:13:28.980 --> 01:13:31.850 align:start position:0% URLs at a time which becomes really helpful<01:13:29.340> for<01:13:29.820> us<01:13:30.000> it<01:13:30.360> says<01:13:30.719> we<01:13:31.020> want<01:13:31.199> to<01:13:31.380> add 01:13:31.850 --> 01:13:31.860 align:start position:0% helpful for us it says we want to add 01:13:31.860 --> 01:13:34.490 align:start position:0% helpful for us it says we want to add we're<01:13:32.520> okay<01:13:32.760> with<01:13:33.000> adding<01:13:33.420> and<01:13:33.840> here<01:13:34.080> it<01:13:34.260> is<01:13:34.380> so 01:13:34.490 --> 01:13:34.500 align:start position:0% we're okay with adding and here it is so 01:13:34.500 --> 01:13:36.169 align:start position:0% we're okay with adding and here it is so we<01:13:34.679> now<01:13:34.800> have<01:13:34.980> this<01:13:35.159> right<01:13:35.400> here<01:13:35.580> and<01:13:36.000> what 01:13:36.169 --> 01:13:36.179 align:start position:0% we now have this right here and what 01:13:36.179 --> 01:13:38.510 align:start position:0% we now have this right here and what open<01:13:36.360> list<01:13:36.659> does<01:13:37.080> is<01:13:37.620> when<01:13:37.860> you<01:13:38.040> have<01:13:38.280> all 01:13:38.510 --> 01:13:38.520 align:start position:0% open list does is when you have all 01:13:38.520 --> 01:13:39.950 align:start position:0% open list does is when you have all these<01:13:38.760> subdomains<01:13:39.360> and<01:13:39.480> you<01:13:39.600> want<01:13:39.719> to<01:13:39.840> see 01:13:39.950 --> 01:13:39.960 align:start position:0% these subdomains and you want to see 01:13:39.960 --> 01:13:42.350 align:start position:0% these subdomains and you want to see what<01:13:40.140> happens<01:13:40.320> you<01:13:40.620> can<01:13:40.800> just<01:13:40.920> copy<01:13:41.340> these<01:13:41.640> and 01:13:42.350 --> 01:13:42.360 align:start position:0% what happens you can just copy these and 01:13:42.360 --> 01:13:44.810 align:start position:0% what happens you can just copy these and then<01:13:42.540> you<01:13:42.840> can<01:13:42.960> paste<01:13:43.679> them<01:13:43.800> in 01:13:44.810 --> 01:13:44.820 align:start position:0% then you can paste them in 01:13:44.820 --> 01:13:47.870 align:start position:0% then you can paste them in so<01:13:45.300> we'll<01:13:45.540> just<01:13:45.719> grab<01:13:46.140> this<01:13:46.620> one<01:13:46.800> because 01:13:47.870 --> 01:13:47.880 align:start position:0% so we'll just grab this one because 01:13:47.880 --> 01:13:49.430 align:start position:0% so we'll just grab this one because I<01:13:48.719> don't<01:13:48.840> think<01:13:48.960> it's<01:13:49.140> going<01:13:49.260> to<01:13:49.320> have 01:13:49.430 --> 01:13:49.440 align:start position:0% I don't think it's going to have 01:13:49.440 --> 01:13:51.290 align:start position:0% I don't think it's going to have anything<01:13:49.560> on<01:13:49.800> it<01:13:49.920> so<01:13:49.980> we'll<01:13:50.159> copy<01:13:50.460> this<01:13:50.580> one<01:13:50.880> we 01:13:51.290 --> 01:13:51.300 align:start position:0% anything on it so we'll copy this one we 01:13:51.300 --> 01:13:53.870 align:start position:0% anything on it so we'll copy this one we can<01:13:51.420> come<01:13:51.540> over<01:13:51.659> to<01:13:52.020> open<01:13:52.620> list<01:13:52.920> and<01:13:53.520> we<01:13:53.760> can 01:13:53.870 --> 01:13:53.880 align:start position:0% can come over to open list and we can 01:13:53.880 --> 01:13:56.990 align:start position:0% can come over to open list and we can just<01:13:54.000> paste<01:13:54.360> in<01:13:54.480> a<01:13:54.780> bunch<01:13:54.960> of<01:13:55.380> URLs<01:13:56.340> so<01:13:56.699> what<01:13:56.880> we 01:13:56.990 --> 01:13:57.000 align:start position:0% just paste in a bunch of URLs so what we 01:13:57.000 --> 01:13:58.430 align:start position:0% just paste in a bunch of URLs so what we would<01:13:57.120> do<01:13:57.239> is<01:13:57.420> you'd<01:13:57.719> really<01:13:57.840> just<01:13:58.020> copy<01:13:58.320> a 01:13:58.430 --> 01:13:58.440 align:start position:0% would do is you'd really just copy a 01:13:58.440 --> 01:13:59.810 align:start position:0% would do is you'd really just copy a bunch<01:13:58.560> of<01:13:58.679> these<01:13:58.920> instead<01:13:59.280> of<01:13:59.340> the<01:13:59.520> same<01:13:59.640> one 01:13:59.810 --> 01:13:59.820 align:start position:0% bunch of these instead of the same one 01:13:59.820 --> 01:14:01.550 align:start position:0% bunch of these instead of the same one over<01:14:00.060> and<01:14:00.239> over<01:14:00.420> and<01:14:00.840> then<01:14:00.960> when<01:14:01.140> you<01:14:01.260> hit<01:14:01.380> open 01:14:01.550 --> 01:14:01.560 align:start position:0% over and over and then when you hit open 01:14:01.560 --> 01:14:03.470 align:start position:0% over and over and then when you hit open URLs<01:14:02.100> it's<01:14:02.340> going<01:14:02.520> to<01:14:02.580> open<01:14:02.760> all<01:14:03.120> of<01:14:03.239> these 01:14:03.470 --> 01:14:03.480 align:start position:0% URLs it's going to open all of these 01:14:03.480 --> 01:14:05.149 align:start position:0% URLs it's going to open all of these tabs<01:14:03.780> for<01:14:03.960> you<01:14:04.140> it's<01:14:04.560> going<01:14:04.739> to<01:14:04.860> be<01:14:04.920> a<01:14:05.040> lot 01:14:05.149 --> 01:14:05.159 align:start position:0% tabs for you it's going to be a lot 01:14:05.159 --> 01:14:07.430 align:start position:0% tabs for you it's going to be a lot faster<01:14:05.460> than<01:14:05.760> having<01:14:06.060> to<01:14:06.360> open<01:14:06.600> one<01:14:06.960> at<01:14:07.140> a<01:14:07.320> time 01:14:07.430 --> 01:14:07.440 align:start position:0% faster than having to open one at a time 01:14:07.440 --> 01:14:09.530 align:start position:0% faster than having to open one at a time so<01:14:07.800> here<01:14:08.040> they<01:14:08.219> are<01:14:08.340> it<01:14:08.580> opened<01:14:08.880> all<01:14:09.000> those<01:14:09.239> for 01:14:09.530 --> 01:14:09.540 align:start position:0% so here they are it opened all those for 01:14:09.540 --> 01:14:11.390 align:start position:0% so here they are it opened all those for us<01:14:09.719> so<01:14:10.199> that's<01:14:10.380> one<01:14:10.560> way<01:14:10.739> to<01:14:10.860> check<01:14:10.980> out<01:14:11.159> the 01:14:11.390 --> 01:14:11.400 align:start position:0% us so that's one way to check out the 01:14:11.400 --> 01:14:12.950 align:start position:0% us so that's one way to check out the subdomains<01:14:12.000> you<01:14:12.060> do<01:14:12.179> find<01:14:12.360> but<01:14:12.600> that's<01:14:12.780> not 01:14:12.950 --> 01:14:12.960 align:start position:0% subdomains you do find but that's not 01:14:12.960 --> 01:14:14.390 align:start position:0% subdomains you do find but that's not the<01:14:13.080> purpose<01:14:13.320> of<01:14:13.440> this<01:14:13.560> video<01:14:13.679> that<01:14:14.100> was<01:14:14.219> kind 01:14:14.390 --> 01:14:14.400 align:start position:0% the purpose of this video that was kind 01:14:14.400 --> 01:14:15.709 align:start position:0% the purpose of this video that was kind of<01:14:14.520> just<01:14:14.640> an<01:14:14.760> afterthought<01:14:15.179> that<01:14:15.420> popped<01:14:15.659> in 01:14:15.709 --> 01:14:15.719 align:start position:0% of just an afterthought that popped in 01:14:15.719 --> 01:14:17.450 align:start position:0% of just an afterthought that popped in my<01:14:15.840> head<01:14:16.020> as<01:14:16.199> we<01:14:16.440> were<01:14:16.620> shooting<01:14:16.920> this<01:14:17.219> video 01:14:17.450 --> 01:14:17.460 align:start position:0% my head as we were shooting this video 01:14:17.460 --> 01:14:19.669 align:start position:0% my head as we were shooting this video so<01:14:17.880> you<01:14:18.000> have<01:14:18.179> sublister<01:14:18.900> and<01:14:19.140> here's<01:14:19.440> a<01:14:19.560> list 01:14:19.669 --> 01:14:19.679 align:start position:0% so you have sublister and here's a list 01:14:19.679 --> 01:14:21.890 align:start position:0% so you have sublister and here's a list of<01:14:19.920> subdomains<01:14:20.580> that<01:14:20.699> it's<01:14:20.820> brought<01:14:21.060> down<01:14:21.179> and 01:14:21.890 --> 01:14:21.900 align:start position:0% of subdomains that it's brought down and 01:14:21.900 --> 01:14:23.450 align:start position:0% of subdomains that it's brought down and you<01:14:22.140> might<01:14:22.260> be<01:14:22.380> able<01:14:22.440> to<01:14:22.560> say<01:14:22.739> well<01:14:22.920> that's<01:14:23.280> a 01:14:23.450 --> 01:14:23.460 align:start position:0% you might be able to say well that's a 01:14:23.460 --> 01:14:25.910 align:start position:0% you might be able to say well that's a that's<01:14:23.820> a<01:14:24.120> decent<01:14:24.420> sized<01:14:24.960> list<01:14:25.199> so<01:14:25.800> we'll 01:14:25.910 --> 01:14:25.920 align:start position:0% that's a decent sized list so we'll 01:14:25.920 --> 01:14:27.709 align:start position:0% that's a decent sized list so we'll scroll<01:14:26.159> through<01:14:26.400> it<01:14:26.520> here<01:14:26.699> it's<01:14:27.179> fine<01:14:27.420> but 01:14:27.709 --> 01:14:27.719 align:start position:0% scroll through it here it's fine but 01:14:27.719 --> 01:14:30.890 align:start position:0% scroll through it here it's fine but it's<01:14:27.960> it's<01:14:28.380> not<01:14:28.679> as<01:14:28.980> big<01:14:29.219> as<01:14:29.940> we<01:14:30.300> would<01:14:30.420> like<01:14:30.600> so 01:14:30.890 --> 01:14:30.900 align:start position:0% it's it's not as big as we would like so 01:14:30.900 --> 01:14:32.209 align:start position:0% it's it's not as big as we would like so one<01:14:31.020> of<01:14:31.140> the<01:14:31.199> tools<01:14:31.440> I've<01:14:31.560> been<01:14:31.739> using<01:14:31.980> here 01:14:32.209 --> 01:14:32.219 align:start position:0% one of the tools I've been using here 01:14:32.219 --> 01:14:34.070 align:start position:0% one of the tools I've been using here recently<01:14:32.699> is<01:14:32.940> amass<01:14:33.540> and<01:14:33.659> you<01:14:33.780> can<01:14:33.900> just<01:14:33.960> type 01:14:34.070 --> 01:14:34.080 align:start position:0% recently is amass and you can just type 01:14:34.080 --> 01:14:36.530 align:start position:0% recently is amass and you can just type in<01:14:34.199> amass<01:14:34.679> H<01:14:35.159> and<01:14:35.400> you<01:14:35.580> can<01:14:35.699> see<01:14:35.940> exactly<01:14:36.420> what 01:14:36.530 --> 01:14:36.540 align:start position:0% in amass H and you can see exactly what 01:14:36.540 --> 01:14:38.149 align:start position:0% in amass H and you can see exactly what it<01:14:36.719> does<01:14:36.900> and<01:14:37.380> it's<01:14:37.500> going<01:14:37.679> to<01:14:37.800> tell<01:14:37.860> you<01:14:37.980> it's 01:14:38.149 --> 01:14:38.159 align:start position:0% it does and it's going to tell you it's 01:14:38.159 --> 01:14:40.850 align:start position:0% it does and it's going to tell you it's an<01:14:38.400> in-depth<01:14:38.820> attack<01:14:39.140> surface<01:14:40.140> mapping<01:14:40.620> and 01:14:40.850 --> 01:14:40.860 align:start position:0% an in-depth attack surface mapping and 01:14:40.860 --> 01:14:43.550 align:start position:0% an in-depth attack surface mapping and asset<01:14:41.219> directory<01:14:41.699> a<01:14:42.179> mass<01:14:42.480> is<01:14:42.719> really<01:14:43.020> cool<01:14:43.140> if 01:14:43.550 --> 01:14:43.560 align:start position:0% asset directory a mass is really cool if 01:14:43.560 --> 01:14:45.830 align:start position:0% asset directory a mass is really cool if you<01:14:43.739> can<01:14:43.800> get<01:14:43.980> it<01:14:44.100> to<01:14:44.219> work<01:14:44.460> so<01:14:45.120> sometimes 01:14:45.830 --> 01:14:45.840 align:start position:0% you can get it to work so sometimes 01:14:45.840 --> 01:14:47.450 align:start position:0% you can get it to work so sometimes amass<01:14:46.320> can<01:14:46.500> be<01:14:46.560> a<01:14:46.679> little<01:14:46.739> bit<01:14:46.800> finicky<01:14:47.280> but 01:14:47.450 --> 01:14:47.460 align:start position:0% amass can be a little bit finicky but 01:14:47.460 --> 01:14:48.890 align:start position:0% amass can be a little bit finicky but it'll<01:14:47.580> work<01:14:47.699> for<01:14:47.820> us<01:14:48.300> for<01:14:48.540> what<01:14:48.659> we're<01:14:48.780> about 01:14:48.890 --> 01:14:48.900 align:start position:0% it'll work for us for what we're about 01:14:48.900 --> 01:14:50.990 align:start position:0% it'll work for us for what we're about to<01:14:49.080> do<01:14:49.140> you<01:14:49.320> just<01:14:49.500> type<01:14:49.679> in<01:14:49.860> a<01:14:50.219> mass<01:14:50.460> and<01:14:50.880> then 01:14:50.990 --> 01:14:51.000 align:start position:0% to do you just type in a mass and then 01:14:51.000 --> 01:14:53.149 align:start position:0% to do you just type in a mass and then we<01:14:51.179> want<01:14:51.360> to<01:14:51.540> use<01:14:51.780> enum<01:14:52.560> because<01:14:52.860> we're<01:14:53.040> going 01:14:53.149 --> 01:14:53.159 align:start position:0% we want to use enum because we're going 01:14:53.159 --> 01:14:54.830 align:start position:0% we want to use enum because we're going to<01:14:53.219> do<01:14:53.340> enumeration<01:14:54.060> right<01:14:54.300> here<01:14:54.420> and<01:14:54.600> then<01:14:54.719> if 01:14:54.830 --> 01:14:54.840 align:start position:0% to do enumeration right here and then if 01:14:54.840 --> 01:14:56.990 align:start position:0% to do enumeration right here and then if you<01:14:54.960> hit<01:14:55.140> a<01:14:55.320> dash<01:14:55.560> if<01:14:56.340> you<01:14:56.520> just<01:14:56.640> hit<01:14:56.820> enter 01:14:56.990 --> 01:14:57.000 align:start position:0% you hit a dash if you just hit enter 01:14:57.000 --> 01:14:58.669 align:start position:0% you hit a dash if you just hit enter with<01:14:57.480> amass<01:14:57.900> enum<01:14:58.199> it'll<01:14:58.500> tell<01:14:58.620> you 01:14:58.669 --> 01:14:58.679 align:start position:0% with amass enum it'll tell you 01:14:58.679 --> 01:15:00.050 align:start position:0% with amass enum it'll tell you everything<01:14:58.980> you<01:14:59.219> can<01:14:59.340> do<01:14:59.520> with<01:14:59.820> the 01:15:00.050 --> 01:15:00.060 align:start position:0% everything you can do with the 01:15:00.060 --> 01:15:02.390 align:start position:0% everything you can do with the enumeration<01:15:00.600> and<01:15:01.380> we're<01:15:01.679> actually<01:15:01.980> going<01:15:02.219> to 01:15:02.390 --> 01:15:02.400 align:start position:0% enumeration and we're actually going to 01:15:02.400 --> 01:15:05.030 align:start position:0% enumeration and we're actually going to scroll<01:15:02.640> up<01:15:03.000> and<01:15:03.659> we're<01:15:03.780> going<01:15:03.900> to<01:15:04.020> run<01:15:04.199> a<01:15:04.620> Dash 01:15:05.030 --> 01:15:05.040 align:start position:0% scroll up and we're going to run a Dash 01:15:05.040 --> 01:15:06.290 align:start position:0% scroll up and we're going to run a Dash D<01:15:05.280> and<01:15:05.520> we're<01:15:05.580> just<01:15:05.760> going<01:15:05.820> to<01:15:05.940> give<01:15:06.000> it<01:15:06.179> a 01:15:06.290 --> 01:15:06.300 align:start position:0% D and we're just going to give it a 01:15:06.300 --> 01:15:09.410 align:start position:0% D and we're just going to give it a domain<01:15:07.020> and<01:15:07.500> sometimes<01:15:07.980> I<01:15:08.340> like<01:15:08.520> to<01:15:08.760> run<01:15:09.060> a 01:15:09.410 --> 01:15:09.420 align:start position:0% domain and sometimes I like to run a 01:15:09.420 --> 01:15:12.350 align:start position:0% domain and sometimes I like to run a dash<01:15:09.659> IP<01:15:10.140> to<01:15:10.620> grab<01:15:10.860> the<01:15:11.100> IP<01:15:11.400> addresses<01:15:11.880> for<01:15:12.179> the 01:15:12.350 --> 01:15:12.360 align:start position:0% dash IP to grab the IP addresses for the 01:15:12.360 --> 01:15:13.850 align:start position:0% dash IP to grab the IP addresses for the discovered<01:15:12.780> names<01:15:12.960> which<01:15:13.320> can<01:15:13.560> be<01:15:13.679> really 01:15:13.850 --> 01:15:13.860 align:start position:0% discovered names which can be really 01:15:13.860 --> 01:15:16.729 align:start position:0% discovered names which can be really helpful<01:15:14.219> so<01:15:15.120> we're<01:15:15.300> just<01:15:15.480> going<01:15:15.600> to<01:15:15.659> run<01:15:15.840> amass 01:15:16.729 --> 01:15:16.739 align:start position:0% helpful so we're just going to run amass 01:15:16.739 --> 01:15:20.149 align:start position:0% helpful so we're just going to run amass enum<01:15:17.460> Dash<01:15:18.300> D<01:15:18.620> and<01:15:19.620> then<01:15:19.679> we'll<01:15:19.920> just<01:15:20.040> run 01:15:20.149 --> 01:15:20.159 align:start position:0% enum Dash D and then we'll just run 01:15:20.159 --> 01:15:23.209 align:start position:0% enum Dash D and then we'll just run yahoo.com<01:15:21.120> actually<01:15:21.900> now<01:15:22.380> that<01:15:22.560> I<01:15:22.739> see<01:15:22.920> this 01:15:23.209 --> 01:15:23.219 align:start position:0% yahoo.com actually now that I see this 01:15:23.219 --> 01:15:24.590 align:start position:0% yahoo.com actually now that I see this is<01:15:23.400> running<01:15:23.640> and<01:15:23.880> it's<01:15:24.060> actually<01:15:24.179> taking<01:15:24.420> a 01:15:24.590 --> 01:15:24.600 align:start position:0% is running and it's actually taking a 01:15:24.600 --> 01:15:26.570 align:start position:0% is running and it's actually taking a little<01:15:24.719> while<01:15:24.900> let's<01:15:25.440> go<01:15:25.800> ahead<01:15:25.980> and<01:15:26.340> close 01:15:26.570 --> 01:15:26.580 align:start position:0% little while let's go ahead and close 01:15:26.580 --> 01:15:29.229 align:start position:0% little while let's go ahead and close out<01:15:26.880> of<01:15:27.000> this<01:15:27.120> I<01:15:27.420> want<01:15:27.540> to<01:15:27.659> run<01:15:27.780> an<01:15:28.080> a<01:15:28.320> mass 01:15:29.229 --> 01:15:29.239 align:start position:0% out of this I want to run an a mass 01:15:29.239 --> 01:15:31.850 align:start position:0% out of this I want to run an a mass enumeration<01:15:30.239> and<01:15:30.719> I<01:15:30.840> want<01:15:30.900> to<01:15:31.080> run<01:15:31.199> a<01:15:31.560> dash 01:15:31.850 --> 01:15:31.860 align:start position:0% enumeration and I want to run a dash 01:15:31.860 --> 01:15:33.169 align:start position:0% enumeration and I want to run a dash passive 01:15:33.169 --> 01:15:33.179 align:start position:0% passive 01:15:33.179 --> 01:15:35.330 align:start position:0% passive and<01:15:33.780> then<01:15:33.900> the<01:15:34.260> domain<01:15:34.560> right<01:15:34.800> here<01:15:34.980> and<01:15:35.219> then 01:15:35.330 --> 01:15:35.340 align:start position:0% and then the domain right here and then 01:15:35.340 --> 01:15:36.890 align:start position:0% and then the domain right here and then run<01:15:35.520> this<01:15:35.699> and<01:15:35.940> this<01:15:36.060> should<01:15:36.239> run<01:15:36.480> a<01:15:36.780> little 01:15:36.890 --> 01:15:36.900 align:start position:0% run this and this should run a little 01:15:36.900 --> 01:15:38.390 align:start position:0% run this and this should run a little bit<01:15:37.020> faster<01:15:37.320> than<01:15:37.560> what<01:15:37.739> we<01:15:37.800> did<01:15:37.980> have<01:15:38.159> going 01:15:38.390 --> 01:15:38.400 align:start position:0% bit faster than what we did have going 01:15:38.400 --> 01:15:40.910 align:start position:0% bit faster than what we did have going okay<01:15:38.940> so<01:15:39.239> amass<01:15:39.780> is<01:15:39.960> still<01:15:40.320> running<01:15:40.500> but<01:15:40.800> I 01:15:40.910 --> 01:15:40.920 align:start position:0% okay so amass is still running but I 01:15:40.920 --> 01:15:42.770 align:start position:0% okay so amass is still running but I want<01:15:41.040> to<01:15:41.159> show<01:15:41.280> you<01:15:41.400> look<01:15:41.699> at<01:15:41.940> all<01:15:42.179> of<01:15:42.360> these 01:15:42.770 --> 01:15:42.780 align:start position:0% want to show you look at all of these 01:15:42.780 --> 01:15:45.590 align:start position:0% want to show you look at all of these subdomains<01:15:43.679> that<01:15:44.280> it<01:15:44.460> has<01:15:44.760> pulled<01:15:45.239> down<01:15:45.360> for 01:15:45.590 --> 01:15:45.600 align:start position:0% subdomains that it has pulled down for 01:15:45.600 --> 01:15:48.709 align:start position:0% subdomains that it has pulled down for us<01:15:45.780> this<01:15:46.080> is<01:15:46.320> going<01:15:46.500> to<01:15:46.679> be<01:15:46.980> way<01:15:47.640> more<01:15:47.880> it's<01:15:48.239> so 01:15:48.709 --> 01:15:48.719 align:start position:0% us this is going to be way more it's so 01:15:48.719 --> 01:15:50.450 align:start position:0% us this is going to be way more it's so many<01:15:48.840> that<01:15:49.320> my<01:15:49.620> terminal<01:15:49.920> is<01:15:50.219> actually 01:15:50.450 --> 01:15:50.460 align:start position:0% many that my terminal is actually 01:15:50.460 --> 01:15:53.090 align:start position:0% many that my terminal is actually lagging<01:15:51.120> so<01:15:51.659> we'll<01:15:51.780> go<01:15:51.960> ahead<01:15:52.140> and<01:15:52.560> close<01:15:52.860> out 01:15:53.090 --> 01:15:53.100 align:start position:0% lagging so we'll go ahead and close out 01:15:53.100 --> 01:15:54.770 align:start position:0% lagging so we'll go ahead and close out of<01:15:53.219> this<01:15:53.340> so<01:15:53.520> that<01:15:53.640> the<01:15:53.760> way<01:15:53.880> it<01:15:54.060> stops<01:15:54.360> and<01:15:54.600> if 01:15:54.770 --> 01:15:54.780 align:start position:0% of this so that the way it stops and if 01:15:54.780 --> 01:15:56.990 align:start position:0% of this so that the way it stops and if we<01:15:54.960> just<01:15:55.140> scroll<01:15:55.440> through<01:15:55.679> here<01:15:55.980> look<01:15:56.580> at<01:15:56.760> all 01:15:56.990 --> 01:15:57.000 align:start position:0% we just scroll through here look at all 01:15:57.000 --> 01:16:00.290 align:start position:0% we just scroll through here look at all of<01:15:57.120> these<01:15:57.360> subdomains<01:15:58.020> this<01:15:58.860> has<01:15:59.159> way<01:16:00.060> more 01:16:00.290 --> 01:16:00.300 align:start position:0% of these subdomains this has way more 01:16:00.300 --> 01:16:03.890 align:start position:0% of these subdomains this has way more subdomains<01:16:01.020> than<01:16:01.679> we<01:16:01.980> had<01:16:02.219> with<01:16:02.940> sublister<01:16:03.659> it 01:16:03.890 --> 01:16:03.900 align:start position:0% subdomains than we had with sublister it 01:16:03.900 --> 01:16:06.770 align:start position:0% subdomains than we had with sublister it is<01:16:04.080> an<01:16:04.620> insane<01:16:05.100> amount<01:16:05.580> so<01:16:06.239> all<01:16:06.480> of<01:16:06.600> these 01:16:06.770 --> 01:16:06.780 align:start position:0% is an insane amount so all of these 01:16:06.780 --> 01:16:08.270 align:start position:0% is an insane amount so all of these subdomains<01:16:07.380> you'll<01:16:07.560> want<01:16:07.679> to<01:16:07.739> check<01:16:07.860> to<01:16:08.159> make 01:16:08.270 --> 01:16:08.280 align:start position:0% subdomains you'll want to check to make 01:16:08.280 --> 01:16:10.189 align:start position:0% subdomains you'll want to check to make sure<01:16:08.520> that<01:16:08.940> they're<01:16:09.120> in<01:16:09.420> scope<01:16:09.719> but<01:16:09.900> look<01:16:10.020> at 01:16:10.189 --> 01:16:10.199 align:start position:0% sure that they're in scope but look at 01:16:10.199 --> 01:16:14.390 align:start position:0% sure that they're in scope but look at all<01:16:10.440> these<01:16:10.739> yahoos<01:16:11.360> like<01:16:12.440> this<01:16:13.440> is<01:16:13.679> a<01:16:14.159> crazy 01:16:14.390 --> 01:16:14.400 align:start position:0% all these yahoos like this is a crazy 01:16:14.400 --> 01:16:17.510 align:start position:0% all these yahoos like this is a crazy attack<01:16:14.880> surface<01:16:15.480> if<01:16:16.080> you<01:16:16.260> can<01:16:16.380> find<01:16:16.739> a<01:16:17.219> program 01:16:17.510 --> 01:16:17.520 align:start position:0% attack surface if you can find a program 01:16:17.520 --> 01:16:20.270 align:start position:0% attack surface if you can find a program that<01:16:17.820> has<01:16:18.000> a<01:16:18.239> really<01:16:18.360> wide<01:16:18.780> scope<01:16:19.199> then<01:16:19.800> you 01:16:20.270 --> 01:16:20.280 align:start position:0% that has a really wide scope then you 01:16:20.280 --> 01:16:22.310 align:start position:0% that has a really wide scope then you will<01:16:20.460> then<01:16:21.000> on<01:16:21.239> most<01:16:21.420> of<01:16:21.540> the<01:16:21.659> subdomains<01:16:22.199> you 01:16:22.310 --> 01:16:22.320 align:start position:0% will then on most of the subdomains you 01:16:22.320 --> 01:16:24.590 align:start position:0% will then on most of the subdomains you find<01:16:22.500> will<01:16:23.219> be<01:16:23.460> in<01:16:23.699> scope<01:16:23.940> but<01:16:24.179> make<01:16:24.300> sure<01:16:24.480> to 01:16:24.590 --> 01:16:24.600 align:start position:0% find will be in scope but make sure to 01:16:24.600 --> 01:16:26.209 align:start position:0% find will be in scope but make sure to always<01:16:24.719> check<01:16:25.140> if<01:16:25.440> I<01:16:25.739> can't<01:16:25.800> believe<01:16:25.980> I'm 01:16:26.209 --> 01:16:26.219 align:start position:0% always check if I can't believe I'm 01:16:26.219 --> 01:16:28.189 align:start position:0% always check if I can't believe I'm still<01:16:26.400> scrolling<01:16:26.760> there<01:16:27.000> has<01:16:27.239> got<01:16:27.420> to<01:16:27.659> be<01:16:27.780> like 01:16:28.189 --> 01:16:28.199 align:start position:0% still scrolling there has got to be like 01:16:28.199 --> 01:16:30.709 align:start position:0% still scrolling there has got to be like nearly<01:16:29.040> a<01:16:29.219> thousand<01:16:29.640> sub<01:16:29.940> domains<01:16:30.480> right 01:16:30.709 --> 01:16:30.719 align:start position:0% nearly a thousand sub domains right 01:16:30.719 --> 01:16:32.510 align:start position:0% nearly a thousand sub domains right there<01:16:30.900> so<01:16:31.320> amass<01:16:31.800> is<01:16:31.980> something<01:16:32.100> you'll<01:16:32.400> want 01:16:32.510 --> 01:16:32.520 align:start position:0% there so amass is something you'll want 01:16:32.520 --> 01:16:35.149 align:start position:0% there so amass is something you'll want to<01:16:32.640> check<01:16:32.940> out<01:16:33.120> I<01:16:33.659> love<01:16:33.840> amass<01:16:34.380> enum<01:16:34.739> and<01:16:35.040> then 01:16:35.149 --> 01:16:35.159 align:start position:0% to check out I love amass enum and then 01:16:35.159 --> 01:16:36.290 align:start position:0% to check out I love amass enum and then I<01:16:35.280> run<01:16:35.460> the<01:16:35.640> passive<01:16:35.880> because<01:16:36.060> I<01:16:36.179> think<01:16:36.239> it 01:16:36.290 --> 01:16:36.300 align:start position:0% I run the passive because I think it 01:16:36.300 --> 01:16:38.510 align:start position:0% I run the passive because I think it runs<01:16:36.540> a<01:16:36.659> little<01:16:36.719> faster<01:16:36.960> and<01:16:37.560> then<01:16:37.679> Yahoo<01:16:37.980> in 01:16:38.510 --> 01:16:38.520 align:start position:0% runs a little faster and then Yahoo in 01:16:38.520 --> 01:16:39.649 align:start position:0% runs a little faster and then Yahoo in this<01:16:38.640> video<01:16:38.760> I'm<01:16:38.940> going<01:16:39.120> to<01:16:39.120> show<01:16:39.239> you<01:16:39.360> some 01:16:39.649 --> 01:16:39.659 align:start position:0% this video I'm going to show you some 01:16:39.659 --> 01:16:41.570 align:start position:0% this video I'm going to show you some cool<01:16:39.960> Recon<01:16:40.440> tools<01:16:40.980> that<01:16:41.219> are<01:16:41.340> going<01:16:41.400> to<01:16:41.460> be 01:16:41.570 --> 01:16:41.580 align:start position:0% cool Recon tools that are going to be 01:16:41.580 --> 01:16:42.770 align:start position:0% cool Recon tools that are going to be able<01:16:41.640> to<01:16:41.760> help<01:16:41.880> you<01:16:42.000> figure<01:16:42.179> out<01:16:42.300> what<01:16:42.540> kind<01:16:42.659> of 01:16:42.770 --> 01:16:42.780 align:start position:0% able to help you figure out what kind of 01:16:42.780 --> 01:16:44.450 align:start position:0% able to help you figure out what kind of technology<01:16:43.080> is<01:16:43.440> running<01:16:43.620> on<01:16:43.980> a<01:16:44.159> specific 01:16:44.450 --> 01:16:44.460 align:start position:0% technology is running on a specific 01:16:44.460 --> 01:16:46.490 align:start position:0% technology is running on a specific website<01:16:44.880> that<01:16:45.179> you<01:16:45.300> may<01:16:45.480> be<01:16:45.600> trying<01:16:45.900> to<01:16:46.140> Target 01:16:46.490 --> 01:16:46.500 align:start position:0% website that you may be trying to Target 01:16:46.500 --> 01:16:48.770 align:start position:0% website that you may be trying to Target and<01:16:46.920> an<01:16:47.159> easy<01:16:47.280> way<01:16:47.520> to<01:16:47.640> find<01:16:47.820> out<01:16:48.000> some<01:16:48.360> version 01:16:48.770 --> 01:16:48.780 align:start position:0% and an easy way to find out some version 01:16:48.780 --> 01:16:50.689 align:start position:0% and an easy way to find out some version numbers<01:16:49.140> and<01:16:49.679> search<01:16:49.920> for<01:16:50.159> vulnerabilities 01:16:50.689 --> 01:16:50.699 align:start position:0% numbers and search for vulnerabilities 01:16:50.699 --> 01:16:52.910 align:start position:0% numbers and search for vulnerabilities this<01:16:51.179> can<01:16:51.360> be<01:16:51.600> really<01:16:51.960> helpful<01:16:52.320> for<01:16:52.560> you<01:16:52.679> to 01:16:52.910 --> 01:16:52.920 align:start position:0% this can be really helpful for you to 01:16:52.920 --> 01:16:54.770 align:start position:0% this can be really helpful for you to know<01:16:53.100> what<01:16:53.520> is<01:16:53.699> being<01:16:54.060> used<01:16:54.300> and<01:16:54.540> what 01:16:54.770 --> 01:16:54.780 align:start position:0% know what is being used and what 01:16:54.780 --> 01:16:56.390 align:start position:0% know what is being used and what technologies<01:16:55.199> are<01:16:55.440> running<01:16:55.620> on<01:16:55.980> a<01:16:56.159> specific 01:16:56.390 --> 01:16:56.400 align:start position:0% technologies are running on a specific 01:16:56.400 --> 01:16:58.189 align:start position:0% technologies are running on a specific website<01:16:56.820> so<01:16:57.060> that<01:16:57.179> way<01:16:57.300> you<01:16:57.480> know<01:16:57.659> what<01:16:58.020> kind 01:16:58.189 --> 01:16:58.199 align:start position:0% website so that way you know what kind 01:16:58.199 --> 01:17:00.590 align:start position:0% website so that way you know what kind of<01:16:58.380> attacks<01:16:58.860> you<01:16:58.980> should<01:16:59.219> be<01:16:59.340> looking<01:16:59.699> for<01:17:00.060> so 01:17:00.590 --> 01:17:00.600 align:start position:0% of attacks you should be looking for so 01:17:00.600 --> 01:17:02.270 align:start position:0% of attacks you should be looking for so with<01:17:00.780> that<01:17:00.960> let's<01:17:01.140> go<01:17:01.380> ahead<01:17:01.560> and<01:17:01.800> jump<01:17:02.100> into 01:17:02.270 --> 01:17:02.280 align:start position:0% with that let's go ahead and jump into 01:17:02.280 --> 01:17:05.689 align:start position:0% with that let's go ahead and jump into it<01:17:02.520> alright<01:17:02.940> so<01:17:03.060> here<01:17:03.360> we<01:17:03.540> are<01:17:03.719> at<01:17:04.699> tenet.hdb 01:17:05.689 --> 01:17:05.699 align:start position:0% it alright so here we are at tenet.hdb 01:17:05.699 --> 01:17:08.510 align:start position:0% it alright so here we are at tenet.hdb this<01:17:06.060> is<01:17:06.239> a<01:17:06.719> box<01:17:06.900> from<01:17:07.260> hack<01:17:07.500> the<01:17:07.739> box<01:17:07.920> I 01:17:08.510 --> 01:17:08.520 align:start position:0% this is a box from hack the box I 01:17:08.520 --> 01:17:10.550 align:start position:0% this is a box from hack the box I decided<01:17:08.940> to<01:17:09.000> use<01:17:09.179> this<01:17:09.420> because<01:17:09.719> if<01:17:10.199> there<01:17:10.380> was 01:17:10.550 --> 01:17:10.560 align:start position:0% decided to use this because if there was 01:17:10.560 --> 01:17:12.229 align:start position:0% decided to use this because if there was something<01:17:10.739> vulnerable<01:17:11.219> on<01:17:11.580> a<01:17:11.820> live<01:17:12.000> web 01:17:12.229 --> 01:17:12.239 align:start position:0% something vulnerable on a live web 01:17:12.239 --> 01:17:13.430 align:start position:0% something vulnerable on a live web application<01:17:12.659> I<01:17:13.020> didn't<01:17:13.080> want<01:17:13.320> to 01:17:13.430 --> 01:17:13.440 align:start position:0% application I didn't want to 01:17:13.440 --> 01:17:15.890 align:start position:0% application I didn't want to accidentally<01:17:13.860> show<01:17:14.340> any<01:17:14.580> information<01:17:14.880> so<01:17:15.600> a 01:17:15.890 --> 01:17:15.900 align:start position:0% accidentally show any information so a 01:17:15.900 --> 01:17:18.470 align:start position:0% accidentally show any information so a few<01:17:16.020> ways<01:17:16.380> to<01:17:16.800> find<01:17:17.159> out<01:17:17.400> what<01:17:17.699> tech<01:17:17.820> stack<01:17:18.239> is 01:17:18.470 --> 01:17:18.480 align:start position:0% few ways to find out what tech stack is 01:17:18.480 --> 01:17:20.810 align:start position:0% few ways to find out what tech stack is being<01:17:18.719> used<01:17:19.020> is<01:17:19.620> with<01:17:19.980> a<01:17:20.219> tool<01:17:20.520> called 01:17:20.810 --> 01:17:20.820 align:start position:0% being used is with a tool called 01:17:20.820 --> 01:17:23.090 align:start position:0% being used is with a tool called wapalizer<01:17:21.780> and<01:17:21.960> it<01:17:22.140> is<01:17:22.320> right<01:17:22.620> here<01:17:22.739> I<01:17:22.980> already 01:17:23.090 --> 01:17:23.100 align:start position:0% wapalizer and it is right here I already 01:17:23.100 --> 01:17:25.790 align:start position:0% wapalizer and it is right here I already have<01:17:23.400> the<01:17:23.699> extension<01:17:24.199> installed<01:17:25.199> and<01:17:25.620> you 01:17:25.790 --> 01:17:25.800 align:start position:0% have the extension installed and you 01:17:25.800 --> 01:17:27.229 align:start position:0% have the extension installed and you just<01:17:25.920> come<01:17:26.100> up<01:17:26.280> here<01:17:26.400> and<01:17:26.580> you<01:17:26.760> can<01:17:26.820> click<01:17:27.120> this 01:17:27.229 --> 01:17:27.239 align:start position:0% just come up here and you can click this 01:17:27.239 --> 01:17:29.330 align:start position:0% just come up here and you can click this extension<01:17:27.719> and<01:17:27.960> it'll<01:17:28.199> show<01:17:28.380> you<01:17:28.560> what<01:17:29.100> it<01:17:29.219> is 01:17:29.330 --> 01:17:29.340 align:start position:0% extension and it'll show you what it is 01:17:29.340 --> 01:17:30.890 align:start position:0% extension and it'll show you what it is running<01:17:29.520> so<01:17:29.699> you're<01:17:29.880> running<01:17:30.060> WordPress<01:17:30.540> A 01:17:30.890 --> 01:17:30.900 align:start position:0% running so you're running WordPress A 01:17:30.900 --> 01:17:33.070 align:start position:0% running so you're running WordPress A 5.6<01:17:31.500> so<01:17:31.679> to<01:17:31.920> Google<01:17:32.040> and<01:17:32.400> type<01:17:32.580> in<01:17:32.760> where 01:17:33.070 --> 01:17:33.080 align:start position:0% 5.6 so to Google and type in where 01:17:33.080 --> 01:17:34.810 align:start position:0% 5.6 so to Google and type in where WordPress 01:17:34.810 --> 01:17:34.820 align:start position:0% WordPress 01:17:34.820 --> 01:17:38.270 align:start position:0% WordPress 5.6<01:17:35.820> and<01:17:36.300> then<01:17:36.420> you<01:17:36.540> can<01:17:36.659> type<01:17:36.840> in<01:17:37.080> exploit<01:17:37.739> or 01:17:38.270 --> 01:17:38.280 align:start position:0% 5.6 and then you can type in exploit or 01:17:38.280 --> 01:17:41.270 align:start position:0% 5.6 and then you can type in exploit or vulnerability<01:17:39.000> and<01:17:39.900> just<01:17:40.080> read<01:17:40.320> to<01:17:40.620> it<01:17:40.800> see<01:17:40.980> if 01:17:41.270 --> 01:17:41.280 align:start position:0% vulnerability and just read to it see if 01:17:41.280 --> 01:17:42.649 align:start position:0% vulnerability and just read to it see if there<01:17:41.520> are<01:17:41.640> any<01:17:41.820> vulnerabilities<01:17:42.360> or 01:17:42.649 --> 01:17:42.659 align:start position:0% there are any vulnerabilities or 01:17:42.659 --> 01:17:44.630 align:start position:0% there are any vulnerabilities or anything<01:17:42.840> that<01:17:43.140> needs<01:17:43.440> to<01:17:43.560> be<01:17:43.800> patched<01:17:44.280> with 01:17:44.630 --> 01:17:44.640 align:start position:0% anything that needs to be patched with 01:17:44.640 --> 01:17:46.610 align:start position:0% anything that needs to be patched with this<01:17:45.060> specific<01:17:45.300> vulnerability<01:17:45.840> sometimes 01:17:46.610 --> 01:17:46.620 align:start position:0% this specific vulnerability sometimes 01:17:46.620 --> 01:17:48.649 align:start position:0% this specific vulnerability sometimes inside<01:17:47.040> of<01:17:47.400> here<01:17:47.580> you'll<01:17:48.000> see<01:17:48.179> something<01:17:48.420> like 01:17:48.649 --> 01:17:48.659 align:start position:0% inside of here you'll see something like 01:17:48.659 --> 01:17:51.290 align:start position:0% inside of here you'll see something like this<01:17:48.900> database<01:17:49.320> this<01:17:49.620> is<01:17:49.739> really<01:17:50.040> helpful<01:17:50.460> for 01:17:51.290 --> 01:17:51.300 align:start position:0% this database this is really helpful for 01:17:51.300 --> 01:17:53.689 align:start position:0% this database this is really helpful for targeting<01:17:51.780> SQL<01:17:52.260> injection<01:17:52.560> so<01:17:52.860> you<01:17:53.040> have<01:17:53.400> a 01:17:53.689 --> 01:17:53.699 align:start position:0% targeting SQL injection so you have a 01:17:53.699 --> 01:17:56.090 align:start position:0% targeting SQL injection so you have a mySQL<01:17:54.420> database<01:17:54.719> so<01:17:54.960> if<01:17:55.199> you<01:17:55.320> find<01:17:55.560> any<01:17:55.800> places 01:17:56.090 --> 01:17:56.100 align:start position:0% mySQL database so if you find any places 01:17:56.100 --> 01:17:58.850 align:start position:0% mySQL database so if you find any places for<01:17:56.880> any<01:17:57.120> inputs<01:17:57.600> which<01:17:57.840> I'm<01:17:58.080> not<01:17:58.320> sure<01:17:58.560> if 01:17:58.850 --> 01:17:58.860 align:start position:0% for any inputs which I'm not sure if 01:17:58.860 --> 01:18:01.490 align:start position:0% for any inputs which I'm not sure if there<01:17:59.040> are<01:17:59.219> or<01:17:59.340> not<01:17:59.520> you<01:18:00.000> can<01:18:00.120> try<01:18:00.420> to<01:18:00.960> pull<01:18:01.260> off 01:18:01.490 --> 01:18:01.500 align:start position:0% there are or not you can try to pull off 01:18:01.500 --> 01:18:03.470 align:start position:0% there are or not you can try to pull off some<01:18:01.739> kind<01:18:01.920> of<01:18:02.040> a<01:18:02.280> SQL<01:18:02.640> injection<01:18:02.940> the 01:18:03.470 --> 01:18:03.480 align:start position:0% some kind of a SQL injection the 01:18:03.480 --> 01:18:05.570 align:start position:0% some kind of a SQL injection the wapilizer<01:18:04.260> tool<01:18:04.560> is<01:18:04.800> really<01:18:05.100> helpful<01:18:05.340> in 01:18:05.570 --> 01:18:05.580 align:start position:0% wapilizer tool is really helpful in 01:18:05.580 --> 01:18:07.370 align:start position:0% wapilizer tool is really helpful in giving<01:18:05.820> you<01:18:06.000> the<01:18:06.239> programming<01:18:06.719> language<01:18:06.900> so 01:18:07.370 --> 01:18:07.380 align:start position:0% giving you the programming language so 01:18:07.380 --> 01:18:09.590 align:start position:0% giving you the programming language so if<01:18:07.620> we're<01:18:07.739> on<01:18:07.920> a<01:18:08.040> web<01:18:08.159> application<01:18:08.580> and<01:18:09.239> we<01:18:09.420> are 01:18:09.590 --> 01:18:09.600 align:start position:0% if we're on a web application and we are 01:18:09.600 --> 01:18:11.750 align:start position:0% if we're on a web application and we are testing<01:18:10.140> it<01:18:10.260> if<01:18:10.800> there<01:18:11.159> is<01:18:11.280> something<01:18:11.520> like 01:18:11.750 --> 01:18:11.760 align:start position:0% testing it if there is something like 01:18:11.760 --> 01:18:13.910 align:start position:0% testing it if there is something like the<01:18:11.940> programming<01:18:12.420> language<01:18:12.659> of<01:18:13.020> PHP<01:18:13.500> there 01:18:13.910 --> 01:18:13.920 align:start position:0% the programming language of PHP there 01:18:13.920 --> 01:18:16.510 align:start position:0% the programming language of PHP there are<01:18:14.040> some<01:18:14.340> very<01:18:14.520> specific<01:18:15.000> ways<01:18:15.840> to<01:18:16.020> go<01:18:16.199> about 01:18:16.510 --> 01:18:16.520 align:start position:0% are some very specific ways to go about 01:18:16.520 --> 01:18:20.510 align:start position:0% are some very specific ways to go about manipulating<01:18:17.540> PHP<01:18:18.540> or<01:18:19.140> checking<01:18:19.739> for<01:18:19.980> PHP 01:18:20.510 --> 01:18:20.520 align:start position:0% manipulating PHP or checking for PHP 01:18:20.520 --> 01:18:22.189 align:start position:0% manipulating PHP or checking for PHP type<01:18:20.760> juggling<01:18:21.179> there's<01:18:21.719> different<01:18:21.960> things 01:18:22.189 --> 01:18:22.199 align:start position:0% type juggling there's different things 01:18:22.199 --> 01:18:24.169 align:start position:0% type juggling there's different things you<01:18:22.380> can<01:18:22.500> do<01:18:22.620> knowing<01:18:23.219> just<01:18:23.520> the<01:18:23.760> programming 01:18:24.169 --> 01:18:24.179 align:start position:0% you can do knowing just the programming 01:18:24.179 --> 01:18:26.090 align:start position:0% you can do knowing just the programming language<01:18:24.420> and<01:18:25.140> then<01:18:25.199> something<01:18:25.560> like<01:18:25.860> this 01:18:26.090 --> 01:18:26.100 align:start position:0% language and then something like this 01:18:26.100 --> 01:18:27.709 align:start position:0% language and then something like this right<01:18:26.340> here<01:18:26.460> we<01:18:26.699> have<01:18:26.760> the<01:18:26.940> web<01:18:27.060> server<01:18:27.420> is 01:18:27.709 --> 01:18:27.719 align:start position:0% right here we have the web server is 01:18:27.719 --> 01:18:29.689 align:start position:0% right here we have the web server is Apache<01:18:28.440> and<01:18:28.679> you<01:18:28.800> can<01:18:28.860> do<01:18:28.980> the<01:18:29.100> same<01:18:29.280> thing<01:18:29.400> we 01:18:29.689 --> 01:18:29.699 align:start position:0% Apache and you can do the same thing we 01:18:29.699 --> 01:18:32.570 align:start position:0% Apache and you can do the same thing we did<01:18:29.820> with<01:18:30.300> the<01:18:30.840> WordPress<01:18:31.260> 5.6<01:18:31.980> and<01:18:32.219> we<01:18:32.400> can<01:18:32.460> go 01:18:32.570 --> 01:18:32.580 align:start position:0% did with the WordPress 5.6 and we can go 01:18:32.580 --> 01:18:33.649 align:start position:0% did with the WordPress 5.6 and we can go out<01:18:32.699> and<01:18:32.820> see<01:18:32.880> if<01:18:33.000> there's<01:18:33.480> any 01:18:33.649 --> 01:18:33.659 align:start position:0% out and see if there's any 01:18:33.659 --> 01:18:35.870 align:start position:0% out and see if there's any vulnerabilities<01:18:34.260> here<01:18:34.560> that<01:18:35.100> maybe<01:18:35.340> have<01:18:35.699> not 01:18:35.870 --> 01:18:35.880 align:start position:0% vulnerabilities here that maybe have not 01:18:35.880 --> 01:18:38.330 align:start position:0% vulnerabilities here that maybe have not been<01:18:36.120> patched<01:18:36.540> for<01:18:36.780> this<01:18:37.440> specific<01:18:37.860> website 01:18:38.330 --> 01:18:38.340 align:start position:0% been patched for this specific website 01:18:38.340 --> 01:18:41.270 align:start position:0% been patched for this specific website so<01:18:38.820> appalyzer<01:18:39.719> is<01:18:39.960> a<01:18:40.320> really<01:18:40.440> great<01:18:40.679> way<01:18:41.040> to 01:18:41.270 --> 01:18:41.280 align:start position:0% so appalyzer is a really great way to 01:18:41.280 --> 01:18:43.430 align:start position:0% so appalyzer is a really great way to find<01:18:41.460> out<01:18:41.640> what<01:18:42.000> kind<01:18:42.179> of<01:18:42.360> Technology<01:18:42.780> a<01:18:43.260> web 01:18:43.430 --> 01:18:43.440 align:start position:0% find out what kind of Technology a web 01:18:43.440 --> 01:18:44.930 align:start position:0% find out what kind of Technology a web application<01:18:43.920> is<01:18:44.159> running<01:18:44.280> and<01:18:44.520> so<01:18:44.699> if<01:18:44.820> you 01:18:44.930 --> 01:18:44.940 align:start position:0% application is running and so if you 01:18:44.940 --> 01:18:46.370 align:start position:0% application is running and so if you wanted<01:18:45.120> to<01:18:45.300> install<01:18:45.540> this<01:18:45.840> you<01:18:46.020> can<01:18:46.140> just<01:18:46.260> go 01:18:46.370 --> 01:18:46.380 align:start position:0% wanted to install this you can just go 01:18:46.380 --> 01:18:49.250 align:start position:0% wanted to install this you can just go to<01:18:46.500> Google<01:18:46.679> type<01:18:47.280> in<01:18:47.460> wapalyzer<01:18:48.239> and<01:18:48.780> you<01:18:49.199> can 01:18:49.250 --> 01:18:49.260 align:start position:0% to Google type in wapalyzer and you can 01:18:49.260 --> 01:18:52.130 align:start position:0% to Google type in wapalyzer and you can type<01:18:49.440> in<01:18:49.620> wapa<01:18:50.219> laser<01:18:50.580> and<01:18:50.880> we<01:18:51.120> want<01:18:51.300> I'm<01:18:51.900> on 01:18:52.130 --> 01:18:52.140 align:start position:0% type in wapa laser and we want I'm on 01:18:52.140 --> 01:18:53.930 align:start position:0% type in wapa laser and we want I'm on Firefox<01:18:52.620> you<01:18:52.920> might<01:18:53.040> be<01:18:53.159> on<01:18:53.340> Chrome<01:18:53.520> and<01:18:53.820> we 01:18:53.930 --> 01:18:53.940 align:start position:0% Firefox you might be on Chrome and we 01:18:53.940 --> 01:18:55.490 align:start position:0% Firefox you might be on Chrome and we can<01:18:54.060> do<01:18:54.179> Firefox<01:18:54.600> and<01:18:54.960> then<01:18:55.080> here's<01:18:55.380> the 01:18:55.490 --> 01:18:55.500 align:start position:0% can do Firefox and then here's the 01:18:55.500 --> 01:18:57.110 align:start position:0% can do Firefox and then here's the extension<01:18:55.980> and<01:18:56.520> you<01:18:56.640> can<01:18:56.760> just<01:18:56.880> come<01:18:57.000> over 01:18:57.110 --> 01:18:57.120 align:start position:0% extension and you can just come over 01:18:57.120 --> 01:18:58.910 align:start position:0% extension and you can just come over here<01:18:57.360> instead<01:18:57.900> of<01:18:57.960> remove<01:18:58.140> you<01:18:58.440> will<01:18:58.620> click 01:18:58.910 --> 01:18:58.920 align:start position:0% here instead of remove you will click 01:18:58.920 --> 01:19:01.370 align:start position:0% here instead of remove you will click install<01:18:59.239> and<01:19:00.239> the<01:19:00.540> second<01:19:00.659> one<01:19:00.900> I<01:19:01.140> want<01:19:01.260> to 01:19:01.370 --> 01:19:01.380 align:start position:0% install and the second one I want to 01:19:01.380 --> 01:19:03.470 align:start position:0% install and the second one I want to show<01:19:01.500> you<01:19:01.620> is<01:19:01.980> the<01:19:02.340> react<01:19:02.699> developer<01:19:03.179> tools 01:19:03.470 --> 01:19:03.480 align:start position:0% show you is the react developer tools 01:19:03.480 --> 01:19:06.290 align:start position:0% show you is the react developer tools this<01:19:04.140> is<01:19:04.440> a<01:19:04.800> really<01:19:05.040> cool<01:19:05.219> extension<01:19:05.820> it<01:19:06.179> will 01:19:06.290 --> 01:19:06.300 align:start position:0% this is a really cool extension it will 01:19:06.300 --> 01:19:08.090 align:start position:0% this is a really cool extension it will be<01:19:06.600> right<01:19:06.960> here<01:19:07.199> and<01:19:07.380> whenever<01:19:07.679> you're<01:19:07.860> using 01:19:08.090 --> 01:19:08.100 align:start position:0% be right here and whenever you're using 01:19:08.100 --> 01:19:09.530 align:start position:0% be right here and whenever you're using something<01:19:08.280> that's<01:19:08.580> using<01:19:08.880> the<01:19:09.120> react 01:19:09.530 --> 01:19:09.540 align:start position:0% something that's using the react 01:19:09.540 --> 01:19:11.750 align:start position:0% something that's using the react framework<01:19:09.960> it<01:19:10.380> will<01:19:10.500> light<01:19:10.860> up<01:19:11.100> for<01:19:11.340> you<01:19:11.460> so<01:19:11.640> I 01:19:11.750 --> 01:19:11.760 align:start position:0% framework it will light up for you so I 01:19:11.760 --> 01:19:13.250 align:start position:0% framework it will light up for you so I went<01:19:11.880> ahead<01:19:12.060> and<01:19:12.120> opened<01:19:12.420> up<01:19:12.540> Instagram<01:19:12.780> and 01:19:13.250 --> 01:19:13.260 align:start position:0% went ahead and opened up Instagram and 01:19:13.260 --> 01:19:14.750 align:start position:0% went ahead and opened up Instagram and you<01:19:13.380> can<01:19:13.440> see<01:19:13.620> a<01:19:13.739> light<01:19:13.920> up<01:19:14.100> blue<01:19:14.280> right<01:19:14.520> here 01:19:14.750 --> 01:19:14.760 align:start position:0% you can see a light up blue right here 01:19:14.760 --> 01:19:16.850 align:start position:0% you can see a light up blue right here and<01:19:15.179> it'll<01:19:15.360> tell<01:19:15.540> you<01:19:15.659> this<01:19:16.140> page<01:19:16.380> is<01:19:16.560> using 01:19:16.850 --> 01:19:16.860 align:start position:0% and it'll tell you this page is using 01:19:16.860 --> 01:19:19.490 align:start position:0% and it'll tell you this page is using the<01:19:17.040> production<01:19:17.340> build<01:19:18.000> of<01:19:18.360> react<01:19:18.900> and<01:19:19.140> so<01:19:19.320> we 01:19:19.490 --> 01:19:19.500 align:start position:0% the production build of react and so we 01:19:19.500 --> 01:19:21.470 align:start position:0% the production build of react and so we know<01:19:19.620> Instagram<01:19:19.860> is<01:19:20.520> using<01:19:20.940> react<01:19:21.300> and 01:19:21.470 --> 01:19:21.480 align:start position:0% know Instagram is using react and 01:19:21.480 --> 01:19:22.490 align:start position:0% know Instagram is using react and there's<01:19:21.600> actually<01:19:21.840> a<01:19:22.080> lot<01:19:22.199> of<01:19:22.320> popular 01:19:22.490 --> 01:19:22.500 align:start position:0% there's actually a lot of popular 01:19:22.500 --> 01:19:24.709 align:start position:0% there's actually a lot of popular websites<01:19:23.100> that<01:19:23.340> use<01:19:23.699> reacts<01:19:24.300> such<01:19:24.540> as 01:19:24.709 --> 01:19:24.719 align:start position:0% websites that use reacts such as 01:19:24.719 --> 01:19:27.050 align:start position:0% websites that use reacts such as ubereats<01:19:25.440> Discord<01:19:25.860> Instagram<01:19:26.219> Skype 01:19:27.050 --> 01:19:27.060 align:start position:0% ubereats Discord Instagram Skype 01:19:27.060 --> 01:19:29.810 align:start position:0% ubereats Discord Instagram Skype Pinterest<01:19:27.480> and<01:19:28.380> many<01:19:28.679> others<01:19:29.100> so<01:19:29.340> knowing 01:19:29.810 --> 01:19:29.820 align:start position:0% Pinterest and many others so knowing 01:19:29.820 --> 01:19:32.090 align:start position:0% Pinterest and many others so knowing what<01:19:30.239> is<01:19:30.420> running<01:19:30.780> such<01:19:31.199> as<01:19:31.380> react<01:19:31.860> you're 01:19:32.090 --> 01:19:32.100 align:start position:0% what is running such as react you're 01:19:32.100 --> 01:19:33.590 align:start position:0% what is running such as react you're going<01:19:32.219> to<01:19:32.340> know<01:19:32.400> that<01:19:32.580> there's<01:19:32.640> a<01:19:32.940> JavaScript 01:19:33.590 --> 01:19:33.600 align:start position:0% going to know that there's a JavaScript 01:19:33.600 --> 01:19:35.689 align:start position:0% going to know that there's a JavaScript and<01:19:33.900> then<01:19:34.020> there<01:19:34.260> are<01:19:34.800> a<01:19:34.980> lot<01:19:35.159> of<01:19:35.340> common 01:19:35.689 --> 01:19:35.699 align:start position:0% and then there are a lot of common 01:19:35.699 --> 01:19:38.209 align:start position:0% and then there are a lot of common Frameworks<01:19:36.540> that<01:19:36.780> are<01:19:36.960> used<01:19:37.140> within<01:19:37.739> react 01:19:38.209 --> 01:19:38.219 align:start position:0% Frameworks that are used within react 01:19:38.219 --> 01:19:40.010 align:start position:0% Frameworks that are used within react and<01:19:38.699> you<01:19:38.880> can<01:19:39.000> Google<01:19:39.239> those<01:19:39.540> we're<01:19:39.780> not<01:19:39.900> going 01:19:40.010 --> 01:19:40.020 align:start position:0% and you can Google those we're not going 01:19:40.020 --> 01:19:42.530 align:start position:0% and you can Google those we're not going to<01:19:40.080> go<01:19:40.260> into<01:19:40.500> those<01:19:40.800> in<01:19:41.219> too<01:19:41.400> much<01:19:41.580> detail<01:19:42.120> and 01:19:42.530 --> 01:19:42.540 align:start position:0% to go into those in too much detail and 01:19:42.540 --> 01:19:44.330 align:start position:0% to go into those in too much detail and then<01:19:42.600> one<01:19:42.840> of<01:19:42.960> my<01:19:43.020> favorite<01:19:43.199> websites<01:19:43.920> is 01:19:44.330 --> 01:19:44.340 align:start position:0% then one of my favorite websites is 01:19:44.340 --> 01:19:47.330 align:start position:0% then one of my favorite websites is right<01:19:44.820> here<01:19:45.060> the<01:19:45.420> W3<01:19:46.020> text<01:19:46.440> this<01:19:47.040> is<01:19:47.159> going<01:19:47.280> to 01:19:47.330 --> 01:19:47.340 align:start position:0% right here the W3 text this is going to 01:19:47.340 --> 01:19:49.729 align:start position:0% right here the W3 text this is going to do<01:19:47.460> something<01:19:47.640> very<01:19:48.000> similar<01:19:48.420> to<01:19:48.840> appalyzer 01:19:49.729 --> 01:19:49.739 align:start position:0% do something very similar to appalyzer 01:19:49.739 --> 01:19:51.770 align:start position:0% do something very similar to appalyzer so<01:19:50.280> right<01:19:50.460> here<01:19:50.640> you<01:19:50.820> can<01:19:50.940> just<01:19:51.060> enter<01:19:51.300> a 01:19:51.770 --> 01:19:51.780 align:start position:0% so right here you can just enter a 01:19:51.780 --> 01:19:53.689 align:start position:0% so right here you can just enter a specific<01:19:52.199> URL<01:19:52.679> and<01:19:52.920> it's<01:19:53.040> going<01:19:53.340> to<01:19:53.460> tell<01:19:53.580> you 01:19:53.689 --> 01:19:53.699 align:start position:0% specific URL and it's going to tell you 01:19:53.699 --> 01:19:56.030 align:start position:0% specific URL and it's going to tell you what<01:19:54.239> is<01:19:54.420> being<01:19:54.659> used<01:19:54.900> very<01:19:55.320> similar<01:19:55.679> to 01:19:56.030 --> 01:19:56.040 align:start position:0% what is being used very similar to 01:19:56.040 --> 01:19:59.930 align:start position:0% what is being used very similar to waplizer<01:19:56.940> so<01:19:57.120> if<01:19:57.239> we<01:19:57.480> just<01:19:57.719> type<01:19:58.199> in<01:19:58.940> yahoo.com 01:19:59.930 --> 01:19:59.940 align:start position:0% waplizer so if we just type in yahoo.com 01:19:59.940 --> 01:20:03.169 align:start position:0% waplizer so if we just type in yahoo.com it<01:20:00.600> will<01:20:00.780> pull<01:20:01.020> back<01:20:01.199> for<01:20:01.500> us<01:20:01.620> all<01:20:02.340> of<01:20:02.640> the 01:20:03.169 --> 01:20:03.179 align:start position:0% it will pull back for us all of the 01:20:03.179 --> 01:20:05.209 align:start position:0% it will pull back for us all of the technology<01:20:03.600> that<01:20:04.020> is<01:20:04.140> being<01:20:04.380> used<01:20:04.560> so<01:20:04.800> it<01:20:04.980> says 01:20:05.209 --> 01:20:05.219 align:start position:0% technology that is being used so it says 01:20:05.219 --> 01:20:07.550 align:start position:0% technology that is being used so it says it<01:20:05.460> has<01:20:05.640> some<01:20:06.120> server-side<01:20:06.659> programming<01:20:07.260> with 01:20:07.550 --> 01:20:07.560 align:start position:0% it has some server-side programming with 01:20:07.560 --> 01:20:11.209 align:start position:0% it has some server-side programming with Java<01:20:08.219> JavaScript<01:20:09.140> jQuery<01:20:10.140> so<01:20:10.739> you<01:20:10.920> have<01:20:11.040> this 01:20:11.209 --> 01:20:11.219 align:start position:0% Java JavaScript jQuery so you have this 01:20:11.219 --> 01:20:13.189 align:start position:0% Java JavaScript jQuery so you have this really<01:20:11.340> old<01:20:11.580> library<01:20:11.940> right<01:20:12.480> here<01:20:12.659> and<01:20:13.020> it 01:20:13.189 --> 01:20:13.199 align:start position:0% really old library right here and it 01:20:13.199 --> 01:20:15.590 align:start position:0% really old library right here and it tells<01:20:13.500> you<01:20:13.620> there<01:20:14.280> is<01:20:14.460> a<01:20:14.760> newer<01:20:15.060> version<01:20:15.239> and 01:20:15.590 --> 01:20:15.600 align:start position:0% tells you there is a newer version and 01:20:15.600 --> 01:20:17.570 align:start position:0% tells you there is a newer version and so<01:20:15.719> there's<01:20:15.900> a<01:20:16.260> lot<01:20:16.440> of<01:20:16.679> information<01:20:16.920> in<01:20:17.400> here 01:20:17.570 --> 01:20:17.580 align:start position:0% so there's a lot of information in here 01:20:17.580 --> 01:20:19.010 align:start position:0% so there's a lot of information in here and<01:20:17.880> if<01:20:18.060> you<01:20:18.179> have<01:20:18.300> any<01:20:18.480> questions<01:20:18.659> about 01:20:19.010 --> 01:20:19.020 align:start position:0% and if you have any questions about 01:20:19.020 --> 01:20:20.630 align:start position:0% and if you have any questions about something<01:20:19.260> like<01:20:19.560> JavaScript<01:20:20.040> you<01:20:20.340> can<01:20:20.460> click 01:20:20.630 --> 01:20:20.640 align:start position:0% something like JavaScript you can click 01:20:20.640 --> 01:20:22.130 align:start position:0% something like JavaScript you can click on<01:20:20.760> it<01:20:20.880> and<01:20:21.000> it'll<01:20:21.179> tell<01:20:21.360> you<01:20:21.480> what<01:20:21.719> JavaScript 01:20:22.130 --> 01:20:22.140 align:start position:0% on it and it'll tell you what JavaScript 01:20:22.140 --> 01:20:26.510 align:start position:0% on it and it'll tell you what JavaScript is<01:20:22.440> or<01:20:22.739> jQuery<01:20:23.280> and<01:20:24.120> how<01:20:24.420> it<01:20:24.659> is<01:20:24.960> used<01:20:25.440> so<01:20:26.159> there 01:20:26.510 --> 01:20:26.520 align:start position:0% is or jQuery and how it is used so there 01:20:26.520 --> 01:20:28.729 align:start position:0% is or jQuery and how it is used so there is<01:20:26.760> one<01:20:27.239> other<01:20:27.360> way<01:20:27.719> to<01:20:28.199> kind<01:20:28.320> of<01:20:28.380> find<01:20:28.560> out 01:20:28.729 --> 01:20:28.739 align:start position:0% is one other way to kind of find out 01:20:28.739 --> 01:20:30.770 align:start position:0% is one other way to kind of find out what<01:20:29.040> kind<01:20:29.219> of<01:20:29.340> a<01:20:29.640> tech<01:20:29.820> stack<01:20:30.179> is<01:20:30.360> being<01:20:30.600> used 01:20:30.770 --> 01:20:30.780 align:start position:0% what kind of a tech stack is being used 01:20:30.780 --> 01:20:32.390 align:start position:0% what kind of a tech stack is being used so<01:20:31.199> if<01:20:31.440> you<01:20:31.500> come<01:20:31.679> in<01:20:31.800> here<01:20:31.980> and<01:20:32.219> you<01:20:32.340> have 01:20:32.390 --> 01:20:32.400 align:start position:0% so if you come in here and you have 01:20:32.400 --> 01:20:34.490 align:start position:0% so if you come in here and you have vapilizer<01:20:32.880> when<01:20:33.239> we<01:20:33.420> look<01:20:33.540> at<01:20:33.659> this<01:20:33.840> we<01:20:34.380> can 01:20:34.490 --> 01:20:34.500 align:start position:0% vapilizer when we look at this we can 01:20:34.500 --> 01:20:36.590 align:start position:0% vapilizer when we look at this we can also<01:20:34.860> come<01:20:35.159> in<01:20:35.340> and<01:20:35.580> try<01:20:35.760> to<01:20:35.880> figure<01:20:36.000> out<01:20:36.239> what 01:20:36.590 --> 01:20:36.600 align:start position:0% also come in and try to figure out what 01:20:36.600 --> 01:20:39.830 align:start position:0% also come in and try to figure out what is<01:20:36.719> being<01:20:37.080> used<01:20:37.320> within<01:20:38.280> the<01:20:39.120> JavaScript 01:20:39.830 --> 01:20:39.840 align:start position:0% is being used within the JavaScript 01:20:39.840 --> 01:20:42.290 align:start position:0% is being used within the JavaScript sometimes<01:20:40.500> you'll<01:20:40.920> be<01:20:41.040> able<01:20:41.159> to<01:20:41.340> see<01:20:41.760> comments 01:20:42.290 --> 01:20:42.300 align:start position:0% sometimes you'll be able to see comments 01:20:42.300 --> 01:20:44.750 align:start position:0% sometimes you'll be able to see comments or<01:20:42.719> be<01:20:43.199> able<01:20:43.380> to<01:20:43.500> work<01:20:43.860> out<01:20:44.040> what<01:20:44.340> is<01:20:44.520> being 01:20:44.750 --> 01:20:44.760 align:start position:0% or be able to work out what is being 01:20:44.760 --> 01:20:47.270 align:start position:0% or be able to work out what is being used<01:20:45.060> on<01:20:45.840> the<01:20:46.080> website<01:20:46.500> by<01:20:46.739> coming<01:20:46.920> in<01:20:47.100> here 01:20:47.270 --> 01:20:47.280 align:start position:0% used on the website by coming in here 01:20:47.280 --> 01:20:50.090 align:start position:0% used on the website by coming in here and<01:20:47.640> clicking<01:20:48.120> on<01:20:48.659> the<01:20:49.140> debugger<01:20:49.679> right<01:20:49.920> here 01:20:50.090 --> 01:20:50.100 align:start position:0% and clicking on the debugger right here 01:20:50.100 --> 01:20:53.330 align:start position:0% and clicking on the debugger right here and<01:20:50.340> it'll<01:20:50.520> tell<01:20:50.699> you<01:20:50.880> here<01:20:51.300> is<01:20:51.600> the<01:20:51.960> JS<01:20:52.440> and<01:20:53.040> we 01:20:53.330 --> 01:20:53.340 align:start position:0% and it'll tell you here is the JS and we 01:20:53.340 --> 01:20:55.070 align:start position:0% and it'll tell you here is the JS and we have<01:20:53.520> the<01:20:54.000> JavaScript<01:20:54.480> and<01:20:54.719> then<01:20:54.840> you<01:20:54.960> can 01:20:55.070 --> 01:20:55.080 align:start position:0% have the JavaScript and then you can 01:20:55.080 --> 01:20:56.689 align:start position:0% have the JavaScript and then you can click<01:20:55.320> the<01:20:55.560> pretty<01:20:55.860> print<01:20:56.100> down<01:20:56.460> at<01:20:56.580> the 01:20:56.689 --> 01:20:56.699 align:start position:0% click the pretty print down at the 01:20:56.699 --> 01:20:58.669 align:start position:0% click the pretty print down at the bottom<01:20:56.940> and<01:20:57.179> you<01:20:57.360> can<01:20:57.420> look<01:20:57.659> through<01:20:57.960> this 01:20:58.669 --> 01:20:58.679 align:start position:0% bottom and you can look through this 01:20:58.679 --> 01:21:01.189 align:start position:0% bottom and you can look through this JavaScript<01:20:59.219> and<01:20:59.640> see<01:20:59.820> what<01:21:00.239> you<01:21:00.420> are<01:21:00.600> able<01:21:00.900> to 01:21:01.189 --> 01:21:01.199 align:start position:0% JavaScript and see what you are able to 01:21:01.199 --> 01:21:03.590 align:start position:0% JavaScript and see what you are able to find<01:21:01.679> inside<01:21:02.280> of<01:21:02.640> here<01:21:02.820> so<01:21:03.060> these<01:21:03.300> are<01:21:03.360> some<01:21:03.480> of 01:21:03.590 --> 01:21:03.600 align:start position:0% find inside of here so these are some of 01:21:03.600 --> 01:21:04.729 align:start position:0% find inside of here so these are some of the common<01:21:03.780> ways<01:21:04.140> to<01:21:04.199> find<01:21:04.320> out<01:21:04.500> what 01:21:04.729 --> 01:21:04.739 align:start position:0% the common ways to find out what 01:21:04.739 --> 01:21:07.130 align:start position:0% the common ways to find out what technologies<01:21:05.159> are<01:21:05.400> being<01:21:05.640> used<01:21:05.940> on<01:21:06.480> websites 01:21:07.130 --> 01:21:07.140 align:start position:0% technologies are being used on websites 01:21:07.140 --> 01:21:09.050 align:start position:0% technologies are being used on websites they<01:21:07.560> can<01:21:07.739> be<01:21:07.980> really<01:21:08.159> helpful<01:21:08.460> for<01:21:08.699> you<01:21:08.820> to 01:21:09.050 --> 01:21:09.060 align:start position:0% they can be really helpful for you to 01:21:09.060 --> 01:21:11.030 align:start position:0% they can be really helpful for you to know<01:21:09.239> what's<01:21:09.480> going<01:21:09.659> on<01:21:09.900> and<01:21:10.260> exactly<01:21:10.620> how<01:21:10.920> to 01:21:11.030 --> 01:21:11.040 align:start position:0% know what's going on and exactly how to 01:21:11.040 --> 01:21:13.070 align:start position:0% know what's going on and exactly how to attack<01:21:11.460> a<01:21:11.880> website<01:21:12.179> and<01:21:12.540> these<01:21:12.719> can<01:21:12.840> be<01:21:12.960> really 01:21:13.070 --> 01:21:13.080 align:start position:0% attack a website and these can be really 01:21:13.080 --> 01:21:15.649 align:start position:0% attack a website and these can be really helpful<01:21:13.440> for<01:21:13.800> you<01:21:13.920> in<01:21:14.219> your<01:21:14.400> recon<01:21:14.940> phase<01:21:15.360> and 01:21:15.649 --> 01:21:15.659 align:start position:0% helpful for you in your recon phase and 01:21:15.659 --> 01:21:17.390 align:start position:0% helpful for you in your recon phase and maybe<01:21:15.840> even<01:21:16.080> lead<01:21:16.320> you<01:21:16.500> to<01:21:16.739> some<01:21:17.159> kind<01:21:17.280> of 01:21:17.390 --> 01:21:17.400 align:start position:0% maybe even lead you to some kind of 01:21:17.400 --> 01:21:19.610 align:start position:0% maybe even lead you to some kind of vulnerabilities<01:21:18.000> just<01:21:18.600> because<01:21:18.780> you<01:21:19.199> have<01:21:19.320> a 01:21:19.610 --> 01:21:19.620 align:start position:0% vulnerabilities just because you have a 01:21:19.620 --> 01:21:21.770 align:start position:0% vulnerabilities just because you have a version<01:21:19.860> number<01:21:20.159> given<01:21:20.699> to<01:21:20.820> you<01:21:21.000> okay<01:21:21.360> so<01:21:21.600> now 01:21:21.770 --> 01:21:21.780 align:start position:0% version number given to you okay so now 01:21:21.780 --> 01:21:23.750 align:start position:0% version number given to you okay so now I<01:21:21.900> want<01:21:22.020> to<01:21:22.140> show<01:21:22.260> you<01:21:22.440> the<01:21:22.739> tool<01:21:23.040> and<01:21:23.159> map<01:21:23.460> and 01:21:23.750 --> 01:21:23.760 align:start position:0% I want to show you the tool and map and 01:21:23.760 --> 01:21:25.189 align:start position:0% I want to show you the tool and map and if<01:21:23.940> you<01:21:24.120> followed<01:21:24.420> my<01:21:24.659> channel<01:21:24.780> for<01:21:25.020> any 01:21:25.189 --> 01:21:25.199 align:start position:0% if you followed my channel for any 01:21:25.199 --> 01:21:26.810 align:start position:0% if you followed my channel for any length<01:21:25.679> of<01:21:25.800> time<01:21:25.980> you're<01:21:26.219> familiar<01:21:26.520> with<01:21:26.699> the 01:21:26.810 --> 01:21:26.820 align:start position:0% length of time you're familiar with the 01:21:26.820 --> 01:21:28.790 align:start position:0% length of time you're familiar with the tool<01:21:27.060> in<01:21:27.179> map<01:21:27.360> but<01:21:27.780> I<01:21:27.900> want<01:21:27.960> to<01:21:28.140> show<01:21:28.260> you<01:21:28.380> how<01:21:28.679> I 01:21:28.790 --> 01:21:28.800 align:start position:0% tool in map but I want to show you how I 01:21:28.800 --> 01:21:30.050 align:start position:0% tool in map but I want to show you how I like<01:21:28.920> to<01:21:29.100> run<01:21:29.219> this<01:21:29.400> tool<01:21:29.699> and<01:21:29.820> the 01:21:30.050 --> 01:21:30.060 align:start position:0% like to run this tool and the 01:21:30.060 --> 01:21:31.910 align:start position:0% like to run this tool and the information<01:21:30.239> I<01:21:30.780> like<01:21:30.960> to<01:21:31.080> look<01:21:31.260> at<01:21:31.380> and<01:21:31.679> pull 01:21:31.910 --> 01:21:31.920 align:start position:0% information I like to look at and pull 01:21:31.920 --> 01:21:34.310 align:start position:0% information I like to look at and pull back<01:21:32.100> from<01:21:32.400> my<01:21:32.580> target<01:21:32.820> Target<01:21:33.120> so<01:21:33.420> nmap<01:21:33.840> is<01:21:34.080> a 01:21:34.310 --> 01:21:34.320 align:start position:0% back from my target Target so nmap is a 01:21:34.320 --> 01:21:36.890 align:start position:0% back from my target Target so nmap is a port<01:21:34.440> scanner<01:21:34.920> and<01:21:35.040> if<01:21:35.219> we<01:21:35.400> run<01:21:35.640> in<01:21:36.179> map<01:21:36.420> Dash<01:21:36.780> H 01:21:36.890 --> 01:21:36.900 align:start position:0% port scanner and if we run in map Dash H 01:21:36.900 --> 01:21:40.189 align:start position:0% port scanner and if we run in map Dash H it's<01:21:37.560> going<01:21:37.800> to<01:21:37.980> spit<01:21:38.460> out<01:21:38.640> for<01:21:38.940> us<01:21:39.120> all<01:21:39.900> of<01:21:40.080> the 01:21:40.189 --> 01:21:40.199 align:start position:0% it's going to spit out for us all of the 01:21:40.199 --> 01:21:42.530 align:start position:0% it's going to spit out for us all of the things<01:21:40.440> that<01:21:40.679> we<01:21:40.860> can<01:21:40.980> do<01:21:41.159> with<01:21:41.640> nmap<01:21:42.179> one<01:21:42.420> of 01:21:42.530 --> 01:21:42.540 align:start position:0% things that we can do with nmap one of 01:21:42.540 --> 01:21:44.149 align:start position:0% things that we can do with nmap one of my<01:21:42.659> favorite<01:21:42.960> things<01:21:43.199> to<01:21:43.380> do<01:21:43.500> is<01:21:43.679> run<01:21:43.860> the<01:21:44.040> dash 01:21:44.149 --> 01:21:44.159 align:start position:0% my favorite things to do is run the dash 01:21:44.159 --> 01:21:46.669 align:start position:0% my favorite things to do is run the dash V<01:21:44.460> with<01:21:44.880> a<01:21:45.120> dash<01:21:45.540> a<01:21:45.780> this<01:21:46.140> is<01:21:46.260> going<01:21:46.380> to<01:21:46.500> tell<01:21:46.560> us 01:21:46.669 --> 01:21:46.679 align:start position:0% V with a dash a this is going to tell us 01:21:46.679 --> 01:21:48.290 align:start position:0% V with a dash a this is going to tell us about<01:21:46.800> the<01:21:47.040> open<01:21:47.100> ports<01:21:47.580> as<01:21:47.760> they<01:21:47.940> come<01:21:48.120> back 01:21:48.290 --> 01:21:48.300 align:start position:0% about the open ports as they come back 01:21:48.300 --> 01:21:49.729 align:start position:0% about the open ports as they come back and<01:21:48.540> this<01:21:48.659> is<01:21:48.780> going<01:21:48.900> to<01:21:49.020> give<01:21:49.080> us<01:21:49.260> all<01:21:49.560> the 01:21:49.729 --> 01:21:49.739 align:start position:0% and this is going to give us all the 01:21:49.739 --> 01:21:50.930 align:start position:0% and this is going to give us all the information<01:21:49.920> so<01:21:50.340> it's<01:21:50.460> going<01:21:50.640> to<01:21:50.699> tell<01:21:50.820> us 01:21:50.930 --> 01:21:50.940 align:start position:0% information so it's going to tell us 01:21:50.940 --> 01:21:53.390 align:start position:0% information so it's going to tell us right<01:21:51.060> here<01:21:51.239> enable<01:21:51.659> OS<01:21:52.500> detection<01:21:52.920> it's 01:21:53.390 --> 01:21:53.400 align:start position:0% right here enable OS detection it's 01:21:53.400 --> 01:21:55.189 align:start position:0% right here enable OS detection it's going<01:21:53.580> to<01:21:53.699> do<01:21:53.820> script<01:21:54.239> scanning<01:21:54.719> and<01:21:55.020> it's 01:21:55.189 --> 01:21:55.199 align:start position:0% going to do script scanning and it's 01:21:55.199 --> 01:21:58.370 align:start position:0% going to do script scanning and it's going<01:21:55.500> to<01:21:55.679> look<01:21:56.400> for<01:21:56.760> different<01:21:57.300> versions<01:21:57.900> as 01:21:58.370 --> 01:21:58.380 align:start position:0% going to look for different versions as 01:21:58.380 --> 01:22:01.189 align:start position:0% going to look for different versions as well<01:21:58.560> so<01:21:59.280> we<01:21:59.520> can<01:21:59.640> go<01:22:00.060> ahead<01:22:00.239> and<01:22:00.540> type<01:22:00.780> in<01:22:00.960> an 01:22:01.189 --> 01:22:01.199 align:start position:0% well so we can go ahead and type in an 01:22:01.199 --> 01:22:05.270 align:start position:0% well so we can go ahead and type in an nmap<01:22:01.739> Dash<01:22:02.219> a<01:22:02.400> and<01:22:03.360> usually<01:22:04.140> you<01:22:04.500> would<01:22:04.620> run<01:22:04.860> a 01:22:05.270 --> 01:22:05.280 align:start position:0% nmap Dash a and usually you would run a 01:22:05.280 --> 01:22:07.010 align:start position:0% nmap Dash a and usually you would run a dash<01:22:05.640> p<01:22:05.820> dash<01:22:06.179> if<01:22:06.360> you're<01:22:06.480> doing<01:22:06.659> like<01:22:06.840> some 01:22:07.010 --> 01:22:07.020 align:start position:0% dash p dash if you're doing like some 01:22:07.020 --> 01:22:09.290 align:start position:0% dash p dash if you're doing like some kind<01:22:07.140> of<01:22:07.260> CTF<01:22:07.679> but<01:22:08.159> if<01:22:08.340> you<01:22:08.460> were<01:22:08.580> doing<01:22:08.760> a<01:22:09.120> bug 01:22:09.290 --> 01:22:09.300 align:start position:0% kind of CTF but if you were doing a bug 01:22:09.300 --> 01:22:11.330 align:start position:0% kind of CTF but if you were doing a bug Bonnie<01:22:09.780> program<01:22:09.960> and<01:22:10.440> you're<01:22:10.620> not<01:22:10.800> wanting<01:22:11.159> to 01:22:11.330 --> 01:22:11.340 align:start position:0% Bonnie program and you're not wanting to 01:22:11.340 --> 01:22:13.430 align:start position:0% Bonnie program and you're not wanting to knock<01:22:11.699> on<01:22:11.880> the<01:22:12.060> doors<01:22:12.300> of<01:22:12.420> all<01:22:12.600> the<01:22:12.719> ports<01:22:13.020> you 01:22:13.430 --> 01:22:13.440 align:start position:0% knock on the doors of all the ports you 01:22:13.440 --> 01:22:15.169 align:start position:0% knock on the doors of all the ports you would<01:22:13.560> just<01:22:13.739> run<01:22:13.860> the<01:22:14.100> specific<01:22:14.400> ports<01:22:14.820> that 01:22:15.169 --> 01:22:15.179 align:start position:0% would just run the specific ports that 01:22:15.179 --> 01:22:17.870 align:start position:0% would just run the specific ports that you<01:22:15.420> would<01:22:15.600> like<01:22:15.780> to<01:22:16.199> see<01:22:16.800> if<01:22:17.280> they<01:22:17.460> are<01:22:17.640> open 01:22:17.870 --> 01:22:17.880 align:start position:0% you would like to see if they are open 01:22:17.880 --> 01:22:19.729 align:start position:0% you would like to see if they are open and<01:22:18.300> so<01:22:18.420> I've<01:22:18.540> gone<01:22:18.780> ahead<01:22:18.960> and<01:22:19.080> opened<01:22:19.380> up<01:22:19.500> a 01:22:19.729 --> 01:22:19.739 align:start position:0% and so I've gone ahead and opened up a 01:22:19.739 --> 01:22:21.890 align:start position:0% and so I've gone ahead and opened up a hack<01:22:19.920> the<01:22:20.100> box<01:22:20.280> and<01:22:20.760> so<01:22:20.940> if<01:22:21.060> we<01:22:21.179> run<01:22:21.360> this<01:22:21.600> this 01:22:21.890 --> 01:22:21.900 align:start position:0% hack the box and so if we run this this 01:22:21.900 --> 01:22:23.209 align:start position:0% hack the box and so if we run this this is<01:22:22.080> what<01:22:22.199> it's<01:22:22.320> going<01:22:22.440> to<01:22:22.500> look<01:22:22.679> like<01:22:22.800> and<01:22:23.040> the 01:22:23.209 --> 01:22:23.219 align:start position:0% is what it's going to look like and the 01:22:23.219 --> 01:22:25.490 align:start position:0% is what it's going to look like and the dash<01:22:23.400> V<01:22:23.640> is<01:22:24.000> going<01:22:24.239> to<01:22:24.420> give<01:22:24.840> us<01:22:25.020> back<01:22:25.199> the 01:22:25.490 --> 01:22:25.500 align:start position:0% dash V is going to give us back the 01:22:25.500 --> 01:22:28.070 align:start position:0% dash V is going to give us back the ports<01:22:25.800> as<01:22:26.400> it<01:22:26.580> finds<01:22:26.880> them<01:22:27.000> so<01:22:27.179> it<01:22:27.300> says<01:22:27.540> a<01:22:27.659> 480 01:22:28.070 --> 01:22:28.080 align:start position:0% ports as it finds them so it says a 480 01:22:28.080 --> 01:22:30.709 align:start position:0% ports as it finds them so it says a 480 is<01:22:28.320> open<01:22:28.500> and<01:22:29.280> it<01:22:29.640> has<01:22:29.820> finished<01:22:30.060> and<01:22:30.300> it<01:22:30.480> tells 01:22:30.709 --> 01:22:30.719 align:start position:0% is open and it has finished and it tells 01:22:30.719 --> 01:22:32.570 align:start position:0% is open and it has finished and it tells us<01:22:30.780> about<01:22:31.140> the<01:22:31.500> open<01:22:31.620> ports<01:22:32.100> and<01:22:32.219> one<01:22:32.340> thing<01:22:32.460> to 01:22:32.570 --> 01:22:32.580 align:start position:0% us about the open ports and one thing to 01:22:32.580 --> 01:22:34.729 align:start position:0% us about the open ports and one thing to note<01:22:32.760> about<01:22:33.179> hack<01:22:33.420> the<01:22:33.659> box<01:22:33.840> is<01:22:34.140> it<01:22:34.380> says<01:22:34.560> it 01:22:34.729 --> 01:22:34.739 align:start position:0% note about hack the box is it says it 01:22:34.739 --> 01:22:36.709 align:start position:0% note about hack the box is it says it did<01:22:34.860> not<01:22:34.980> follow<01:22:35.159> the<01:22:35.460> redirect<01:22:35.760> so<01:22:36.360> it<01:22:36.480> went 01:22:36.709 --> 01:22:36.719 align:start position:0% did not follow the redirect so it went 01:22:36.719 --> 01:22:38.689 align:start position:0% did not follow the redirect so it went out<01:22:36.840> to<01:22:37.020> see<01:22:37.140> if<01:22:37.320> Port<01:22:37.440> 80<01:22:37.620> was<01:22:37.920> open<01:22:38.040> we<01:22:38.520> were 01:22:38.689 --> 01:22:38.699 align:start position:0% out to see if Port 80 was open we were 01:22:38.699 --> 01:22:41.570 align:start position:0% out to see if Port 80 was open we were redirected<01:22:39.300> to<01:22:39.800> academy.htb<01:22:40.800> and<01:22:41.219> if<01:22:41.400> I 01:22:41.570 --> 01:22:41.580 align:start position:0% redirected to academy.htb and if I 01:22:41.580 --> 01:22:43.010 align:start position:0% redirected to academy.htb and if I actually<01:22:41.760> wanted<01:22:42.000> to<01:22:42.239> open<01:22:42.420> that<01:22:42.600> up<01:22:42.780> and<01:22:42.900> I 01:22:43.010 --> 01:22:43.020 align:start position:0% actually wanted to open that up and I 01:22:43.020 --> 01:22:44.510 align:start position:0% actually wanted to open that up and I keep<01:22:43.140> getting<01:22:43.320> this<01:22:43.560> not<01:22:43.860> found<01:22:44.040> right<01:22:44.340> here 01:22:44.510 --> 01:22:44.520 align:start position:0% keep getting this not found right here 01:22:44.520 --> 01:22:48.649 align:start position:0% keep getting this not found right here that<01:22:45.420> is<01:22:45.600> because<01:22:45.960> I<01:22:46.620> need<01:22:46.739> to<01:22:46.980> add<01:22:47.400> this<01:22:48.000> to<01:22:48.300> my 01:22:48.649 --> 01:22:48.659 align:start position:0% that is because I need to add this to my 01:22:48.659 --> 01:22:50.750 align:start position:0% that is because I need to add this to my Etsy<01:22:48.840> host<01:22:49.080> file<01:22:49.500> but<01:22:49.980> we're<01:22:50.159> not<01:22:50.340> going<01:22:50.460> to<01:22:50.640> do 01:22:50.750 --> 01:22:50.760 align:start position:0% Etsy host file but we're not going to do 01:22:50.760 --> 01:22:51.950 align:start position:0% Etsy host file but we're not going to do that<01:22:50.880> right<01:22:51.060> now<01:22:51.179> that's<01:22:51.420> not<01:22:51.600> the<01:22:51.719> point<01:22:51.840> of 01:22:51.950 --> 01:22:51.960 align:start position:0% that right now that's not the point of 01:22:51.960 --> 01:22:54.290 align:start position:0% that right now that's not the point of the<01:22:52.080> video<01:22:52.199> and<01:22:52.679> we<01:22:53.159> are<01:22:53.340> told<01:22:53.580> we<01:22:53.880> have<01:22:54.000> the 01:22:54.290 --> 01:22:54.300 align:start position:0% the video and we are told we have the 01:22:54.300 --> 01:22:56.149 align:start position:0% the video and we are told we have the Apache<01:22:54.780> version<01:22:54.960> and<01:22:55.320> it<01:22:55.560> tells<01:22:55.860> us<01:22:55.920> our 01:22:56.149 --> 01:22:56.159 align:start position:0% Apache version and it tells us our 01:22:56.159 --> 01:22:58.550 align:start position:0% Apache version and it tells us our methods<01:22:56.699> and<01:22:57.000> it<01:22:57.239> gives<01:22:57.420> us<01:22:57.600> these<01:22:58.080> ports<01:22:58.380> are 01:22:58.550 --> 01:22:58.560 align:start position:0% methods and it gives us these ports are 01:22:58.560 --> 01:23:02.030 align:start position:0% methods and it gives us these ports are open<01:22:58.800> as<01:22:59.340> well<01:22:59.520> so<01:23:00.239> this<01:23:00.719> is<01:23:01.020> how<01:23:01.440> I<01:23:01.679> like<01:23:01.800> to 01:23:02.030 --> 01:23:02.040 align:start position:0% open as well so this is how I like to 01:23:02.040 --> 01:23:04.370 align:start position:0% open as well so this is how I like to run<01:23:02.340> in<01:23:02.580> map<01:23:02.820> and<01:23:03.120> so<01:23:03.300> we<01:23:03.540> will<01:23:03.719> continue<01:23:04.020> on 01:23:04.370 --> 01:23:04.380 align:start position:0% run in map and so we will continue on 01:23:04.380 --> 01:23:06.649 align:start position:0% run in map and so we will continue on there<01:23:04.800> is<01:23:04.980> a<01:23:05.159> one<01:23:05.340> last<01:23:05.520> way<01:23:05.820> to<01:23:06.179> search<01:23:06.420> for 01:23:06.649 --> 01:23:06.659 align:start position:0% there is a one last way to search for 01:23:06.659 --> 01:23:08.450 align:start position:0% there is a one last way to search for subdomains<01:23:07.320> and<01:23:07.560> directories<01:23:08.040> that<01:23:08.219> I<01:23:08.340> think 01:23:08.450 --> 01:23:08.460 align:start position:0% subdomains and directories that I think 01:23:08.460 --> 01:23:10.330 align:start position:0% subdomains and directories that I think will<01:23:08.640> be<01:23:08.820> helpful<01:23:09.120> for<01:23:09.420> you<01:23:09.480> to<01:23:09.780> know 01:23:10.330 --> 01:23:10.340 align:start position:0% will be helpful for you to know 01:23:10.340 --> 01:23:12.770 align:start position:0% will be helpful for you to know specifically<01:23:11.340> subdomains<01:23:12.239> we've<01:23:12.480> seen<01:23:12.600> this 01:23:12.770 --> 01:23:12.780 align:start position:0% specifically subdomains we've seen this 01:23:12.780 --> 01:23:15.169 align:start position:0% specifically subdomains we've seen this before<01:23:13.020> dealing<01:23:13.800> with<01:23:14.159> directories<01:23:14.880> but 01:23:15.169 --> 01:23:15.179 align:start position:0% before dealing with directories but 01:23:15.179 --> 01:23:16.910 align:start position:0% before dealing with directories but we're<01:23:15.360> going<01:23:15.540> to<01:23:15.659> use<01:23:15.719> the<01:23:15.960> tool<01:23:16.199> fuff<01:23:16.560> and 01:23:16.910 --> 01:23:16.920 align:start position:0% we're going to use the tool fuff and 01:23:16.920 --> 01:23:18.470 align:start position:0% we're going to use the tool fuff and this<01:23:17.219> is<01:23:17.340> the<01:23:17.640> syntax<01:23:17.940> that<01:23:18.179> we're<01:23:18.300> going<01:23:18.420> to 01:23:18.470 --> 01:23:18.480 align:start position:0% this is the syntax that we're going to 01:23:18.480 --> 01:23:20.450 align:start position:0% this is the syntax that we're going to use<01:23:18.600> we're<01:23:18.780> going<01:23:18.960> to<01:23:19.080> go<01:23:19.260> ahead<01:23:19.440> and<01:23:19.800> fuzz<01:23:20.280> for 01:23:20.450 --> 01:23:20.460 align:start position:0% use we're going to go ahead and fuzz for 01:23:20.460 --> 01:23:23.030 align:start position:0% use we're going to go ahead and fuzz for subdomains<01:23:21.300> on<01:23:21.480> yahoo.com<01:23:22.140> so<01:23:22.500> the<01:23:22.800> tool<01:23:22.980> is 01:23:23.030 --> 01:23:23.040 align:start position:0% subdomains on yahoo.com so the tool is 01:23:23.040 --> 01:23:24.470 align:start position:0% subdomains on yahoo.com so the tool is pretty<01:23:23.219> simple<01:23:23.400> to<01:23:23.640> use<01:23:23.760> we<01:23:24.000> just<01:23:24.179> type<01:23:24.300> in 01:23:24.470 --> 01:23:24.480 align:start position:0% pretty simple to use we just type in 01:23:24.480 --> 01:23:27.830 align:start position:0% pretty simple to use we just type in fluff<01:23:24.900> the<01:23:25.560> URL<01:23:26.159> which<01:23:26.400> is<01:23:26.520> going<01:23:26.699> to<01:23:26.820> be<01:23:27.120> right 01:23:27.830 --> 01:23:27.840 align:start position:0% fluff the URL which is going to be right 01:23:27.840 --> 01:23:29.450 align:start position:0% fluff the URL which is going to be right here<01:23:28.020> and<01:23:28.320> the<01:23:28.500> location<01:23:28.679> that<01:23:29.040> we<01:23:29.219> want<01:23:29.340> to 01:23:29.450 --> 01:23:29.460 align:start position:0% here and the location that we want to 01:23:29.460 --> 01:23:31.250 align:start position:0% here and the location that we want to fuzz<01:23:29.820> which<01:23:30.060> is<01:23:30.179> for<01:23:30.360> subdomains<01:23:31.020> before 01:23:31.250 --> 01:23:31.260 align:start position:0% fuzz which is for subdomains before 01:23:31.260 --> 01:23:34.370 align:start position:0% fuzz which is for subdomains before yahoo.com<01:23:32.159> and<01:23:32.699> and<01:23:33.120> this<01:23:33.600> is<01:23:33.840> going<01:23:34.020> to<01:23:34.140> a 01:23:34.370 --> 01:23:34.380 align:start position:0% yahoo.com and and this is going to a 01:23:34.380 --> 01:23:36.470 align:start position:0% yahoo.com and and this is going to a Brute<01:23:34.679> Force<01:23:34.980> for<01:23:35.159> us<01:23:35.280> any<01:23:35.640> subdomains<01:23:36.360> that 01:23:36.470 --> 01:23:36.480 align:start position:0% Brute Force for us any subdomains that 01:23:36.480 --> 01:23:38.630 align:start position:0% Brute Force for us any subdomains that come<01:23:36.600> back<01:23:36.719> with<01:23:36.900> the<01:23:37.080> status<01:23:37.199> code<01:23:37.500> 200<01:23:38.040> and 01:23:38.630 --> 01:23:38.640 align:start position:0% come back with the status code 200 and 01:23:38.640 --> 01:23:39.709 align:start position:0% come back with the status code 200 and then<01:23:38.760> we're<01:23:38.880> going<01:23:39.000> to<01:23:39.060> use<01:23:39.179> our<01:23:39.360> word<01:23:39.540> list 01:23:39.709 --> 01:23:39.719 align:start position:0% then we're going to use our word list 01:23:39.719 --> 01:23:41.450 align:start position:0% then we're going to use our word list which<01:23:40.020> is<01:23:40.199> right<01:23:40.500> here<01:23:40.739> and<01:23:40.980> then<01:23:41.100> we're<01:23:41.340> going 01:23:41.450 --> 01:23:41.460 align:start position:0% which is right here and then we're going 01:23:41.460 --> 01:23:44.630 align:start position:0% which is right here and then we're going to<01:23:41.640> use<01:23:41.820> a<01:23:42.420> Slowdown<01:23:42.960> of<01:23:43.500> one<01:23:43.920> second<01:23:44.100> so<01:23:44.460> we 01:23:44.630 --> 01:23:44.640 align:start position:0% to use a Slowdown of one second so we 01:23:44.640 --> 01:23:46.610 align:start position:0% to use a Slowdown of one second so we can<01:23:44.820> go<01:23:44.940> ahead<01:23:45.060> and<01:23:45.300> run<01:23:45.480> this<01:23:45.719> and<01:23:46.320> you<01:23:46.440> should 01:23:46.610 --> 01:23:46.620 align:start position:0% can go ahead and run this and you should 01:23:46.620 --> 01:23:49.010 align:start position:0% can go ahead and run this and you should be<01:23:46.739> able<01:23:46.860> to<01:23:47.040> see<01:23:47.580> subdomains<01:23:48.420> start<01:23:48.600> spitting 01:23:49.010 --> 01:23:49.020 align:start position:0% be able to see subdomains start spitting 01:23:49.020 --> 01:23:51.649 align:start position:0% be able to see subdomains start spitting out<01:23:49.140> as<01:23:49.380> it<01:23:49.560> finds<01:23:49.860> them<01:23:49.980> and<01:23:50.460> here<01:23:50.820> are<01:23:51.060> a<01:23:51.420> few 01:23:51.649 --> 01:23:51.659 align:start position:0% out as it finds them and here are a few 01:23:51.659 --> 01:23:53.450 align:start position:0% out as it finds them and here are a few different<01:23:51.840> subdomains<01:23:52.560> and<01:23:52.920> I<01:23:53.100> want<01:23:53.219> to<01:23:53.340> just 01:23:53.450 --> 01:23:53.460 align:start position:0% different subdomains and I want to just 01:23:53.460 --> 01:23:55.010 align:start position:0% different subdomains and I want to just we'll<01:23:53.760> stop<01:23:53.940> this<01:23:54.179> right<01:23:54.360> here<01:23:54.540> I<01:23:54.719> want<01:23:54.900> to 01:23:55.010 --> 01:23:55.020 align:start position:0% we'll stop this right here I want to 01:23:55.020 --> 01:23:58.130 align:start position:0% we'll stop this right here I want to show<01:23:55.260> you<01:23:55.440> so<01:23:56.159> we<01:23:56.520> got<01:23:56.699> this<01:23:56.820> 301<01:23:57.360> which<01:23:57.840> I 01:23:58.130 --> 01:23:58.140 align:start position:0% show you so we got this 301 which I 01:23:58.140 --> 01:24:00.770 align:start position:0% show you so we got this 301 which I believe<01:23:58.260> is<01:23:58.620> going<01:23:58.800> to<01:23:58.980> be<01:23:59.159> a<01:23:59.520> redirect<01:23:59.940> but<01:24:00.600> we 01:24:00.770 --> 01:24:00.780 align:start position:0% believe is going to be a redirect but we 01:24:00.780 --> 01:24:02.810 align:start position:0% believe is going to be a redirect but we have<01:24:00.960> different<01:24:01.380> sizes<01:24:02.100> different<01:24:02.520> word 01:24:02.810 --> 01:24:02.820 align:start position:0% have different sizes different word 01:24:02.820 --> 01:24:05.090 align:start position:0% have different sizes different word sizes<01:24:03.300> so<01:24:03.600> you<01:24:03.780> might<01:24:03.960> want<01:24:04.199> to<01:24:04.380> go<01:24:04.739> and<01:24:04.980> check 01:24:05.090 --> 01:24:05.100 align:start position:0% sizes so you might want to go and check 01:24:05.100 --> 01:24:07.250 align:start position:0% sizes so you might want to go and check these<01:24:05.400> out<01:24:05.520> anyway<01:24:05.820> but<01:24:06.540> just<01:24:06.780> in<01:24:06.900> case<01:24:07.020> we 01:24:07.250 --> 01:24:07.260 align:start position:0% these out anyway but just in case we 01:24:07.260 --> 01:24:09.709 align:start position:0% these out anyway but just in case we didn't<01:24:07.380> want<01:24:07.560> to<01:24:07.679> see<01:24:07.800> these<01:24:08.400> 301s<01:24:09.179> what<01:24:09.420> we 01:24:09.709 --> 01:24:09.719 align:start position:0% didn't want to see these 301s what we 01:24:09.719 --> 01:24:13.490 align:start position:0% didn't want to see these 301s what we can<01:24:09.900> do<01:24:10.320> is<01:24:10.620> I<01:24:10.920> think<01:24:11.100> it<01:24:11.460> is<01:24:11.760> a<01:24:12.179> dash<01:24:12.480> FC<01:24:12.960> and<01:24:13.260> we 01:24:13.490 --> 01:24:13.500 align:start position:0% can do is I think it is a dash FC and we 01:24:13.500 --> 01:24:16.010 align:start position:0% can do is I think it is a dash FC and we can<01:24:13.620> say<01:24:13.800> 301<01:24:14.580> and<01:24:14.820> now<01:24:15.060> it<01:24:15.239> won't<01:24:15.420> show<01:24:15.600> us<01:24:15.780> any 01:24:16.010 --> 01:24:16.020 align:start position:0% can say 301 and now it won't show us any 01:24:16.020 --> 01:24:18.950 align:start position:0% can say 301 and now it won't show us any of<01:24:16.199> those<01:24:16.520> 301s<01:24:17.520> sometimes<01:24:18.179> that<01:24:18.540> comes<01:24:18.840> in 01:24:18.950 --> 01:24:18.960 align:start position:0% of those 301s sometimes that comes in 01:24:18.960 --> 01:24:21.350 align:start position:0% of those 301s sometimes that comes in handy<01:24:19.260> when<01:24:19.679> you<01:24:20.100> are<01:24:20.340> fuzzing<01:24:20.940> and<01:24:21.060> you<01:24:21.239> keep 01:24:21.350 --> 01:24:21.360 align:start position:0% handy when you are fuzzing and you keep 01:24:21.360 --> 01:24:24.050 align:start position:0% handy when you are fuzzing and you keep getting<01:24:21.600> 401<01:24:22.440> or<01:24:22.679> 403<01:24:23.280> and<01:24:23.580> we<01:24:23.760> really<01:24:23.880> don't 01:24:24.050 --> 01:24:24.060 align:start position:0% getting 401 or 403 and we really don't 01:24:24.060 --> 01:24:25.790 align:start position:0% getting 401 or 403 and we really don't want<01:24:24.239> to<01:24:24.360> see<01:24:24.480> those<01:24:24.719> and<01:24:25.320> so<01:24:25.440> you<01:24:25.560> can<01:24:25.679> see 01:24:25.790 --> 01:24:25.800 align:start position:0% want to see those and so you can see 01:24:25.800 --> 01:24:28.610 align:start position:0% want to see those and so you can see here<01:24:26.100> are<01:24:26.340> some<01:24:26.580> 200s<01:24:27.239> so<01:24:27.480> if<01:24:27.659> we<01:24:27.780> wanted<01:24:27.960> to<01:24:28.260> we 01:24:28.610 --> 01:24:28.620 align:start position:0% here are some 200s so if we wanted to we 01:24:28.620 --> 01:24:31.130 align:start position:0% here are some 200s so if we wanted to we could<01:24:28.739> go<01:24:29.159> out<01:24:29.280> and<01:24:29.640> look<01:24:30.000> for<01:24:30.300> these 01:24:31.130 --> 01:24:31.140 align:start position:0% could go out and look for these 01:24:31.140 --> 01:24:33.530 align:start position:0% could go out and look for these subdomains<01:24:31.860> and<01:24:32.100> see<01:24:32.219> if<01:24:32.340> any<01:24:32.460> of<01:24:32.520> them<01:24:32.640> look 01:24:33.530 --> 01:24:33.540 align:start position:0% subdomains and see if any of them look 01:24:33.540 --> 01:24:36.350 align:start position:0% subdomains and see if any of them look interesting<01:24:34.020> to<01:24:34.380> us<01:24:34.560> now<01:24:35.460> I<01:24:35.940> have<01:24:36.060> mentioned 01:24:36.350 --> 01:24:36.360 align:start position:0% interesting to us now I have mentioned 01:24:36.360 --> 01:24:38.570 align:start position:0% interesting to us now I have mentioned this<01:24:36.540> before<01:24:36.719> you<01:24:37.199> can<01:24:37.320> also<01:24:37.620> fuzz<01:24:38.159> for 01:24:38.570 --> 01:24:38.580 align:start position:0% this before you can also fuzz for 01:24:38.580 --> 01:24:42.709 align:start position:0% this before you can also fuzz for directories<01:24:39.420> and<01:24:40.320> you<01:24:40.800> can<01:24:40.980> use<01:24:41.820> the<01:24:42.300> fuzz 01:24:42.709 --> 01:24:42.719 align:start position:0% directories and you can use the fuzz 01:24:42.719 --> 01:24:46.010 align:start position:0% directories and you can use the fuzz like<01:24:43.500> this<01:24:43.860> and<01:24:44.460> this<01:24:44.820> location<01:24:45.000> and<01:24:45.780> now<01:24:45.900> if 01:24:46.010 --> 01:24:46.020 align:start position:0% like this and this location and now if 01:24:46.020 --> 01:24:47.330 align:start position:0% like this and this location and now if we<01:24:46.080> run<01:24:46.260> it<01:24:46.440> it's<01:24:46.620> going<01:24:46.800> to<01:24:46.860> look<01:24:47.040> for 01:24:47.330 --> 01:24:47.340 align:start position:0% we run it it's going to look for 01:24:47.340 --> 01:24:50.390 align:start position:0% we run it it's going to look for directories<01:24:48.060> and<01:24:48.480> lastly<01:24:49.080> one<01:24:49.500> thing<01:24:49.739> I<01:24:50.159> also 01:24:50.390 --> 01:24:50.400 align:start position:0% directories and lastly one thing I also 01:24:50.400 --> 01:24:52.610 align:start position:0% directories and lastly one thing I also want<01:24:50.580> to<01:24:50.760> mention<01:24:50.880> is<01:24:51.360> when<01:24:51.659> you<01:24:51.900> are<01:24:52.020> fuzzing 01:24:52.610 --> 01:24:52.620 align:start position:0% want to mention is when you are fuzzing 01:24:52.620 --> 01:24:56.270 align:start position:0% want to mention is when you are fuzzing for<01:24:52.860> apis<01:24:53.520> fuff<01:24:54.480> is<01:24:54.780> also<01:24:55.140> a<01:24:55.620> really<01:24:55.980> great 01:24:56.270 --> 01:24:56.280 align:start position:0% for apis fuff is also a really great 01:24:56.280 --> 01:24:58.370 align:start position:0% for apis fuff is also a really great tool<01:24:56.820> for<01:24:57.060> this<01:24:57.239> so<01:24:57.600> we'll<01:24:57.719> go<01:24:57.840> ahead<01:24:58.020> and 01:24:58.370 --> 01:24:58.380 align:start position:0% tool for this so we'll go ahead and 01:24:58.380 --> 01:25:00.950 align:start position:0% tool for this so we'll go ahead and delete<01:24:58.679> this<01:24:59.040> and<01:24:59.340> if<01:24:59.520> we<01:24:59.760> were<01:25:00.179> going<01:25:00.600> to<01:25:00.780> be 01:25:00.950 --> 01:25:00.960 align:start position:0% delete this and if we were going to be 01:25:00.960 --> 01:25:03.530 align:start position:0% delete this and if we were going to be looking<01:25:01.199> for<01:25:01.739> let's<01:25:02.280> say<01:25:02.460> there's<01:25:02.820> an<01:25:03.060> API 01:25:03.530 --> 01:25:03.540 align:start position:0% looking for let's say there's an API 01:25:03.540 --> 01:25:05.830 align:start position:0% looking for let's say there's an API that<01:25:04.080> looks<01:25:04.380> like<01:25:04.500> this 01:25:05.830 --> 01:25:05.840 align:start position:0% that looks like this 01:25:05.840 --> 01:25:08.209 align:start position:0% that looks like this api.yahoo.com<01:25:06.840> and<01:25:07.199> we<01:25:07.380> wanted<01:25:07.500> to<01:25:07.679> fuzz<01:25:07.980> for 01:25:08.209 --> 01:25:08.219 align:start position:0% api.yahoo.com and we wanted to fuzz for 01:25:08.219 --> 01:25:09.830 align:start position:0% api.yahoo.com and we wanted to fuzz for valid<01:25:08.699> endpoints<01:25:09.239> and<01:25:09.360> see<01:25:09.480> what<01:25:09.600> we<01:25:09.719> could 01:25:09.830 --> 01:25:09.840 align:start position:0% valid endpoints and see what we could 01:25:09.840 --> 01:25:11.270 align:start position:0% valid endpoints and see what we could find<01:25:10.020> we<01:25:10.500> would<01:25:10.679> just<01:25:10.800> go<01:25:10.920> ahead<01:25:11.040> and<01:25:11.159> run 01:25:11.270 --> 01:25:11.280 align:start position:0% find we would just go ahead and run 01:25:11.280 --> 01:25:13.550 align:start position:0% find we would just go ahead and run fluff<01:25:11.640> like<01:25:11.880> this<01:25:12.060> and<01:25:12.480> look<01:25:12.719> for<01:25:12.900> endpoints 01:25:13.550 --> 01:25:13.560 align:start position:0% fluff like this and look for endpoints 01:25:13.560 --> 01:25:15.169 align:start position:0% fluff like this and look for endpoints and<01:25:13.739> then<01:25:13.860> go<01:25:14.040> out<01:25:14.159> to<01:25:14.280> the<01:25:14.340> web<01:25:14.460> page<01:25:14.699> if<01:25:15.060> we 01:25:15.169 --> 01:25:15.179 align:start position:0% and then go out to the web page if we 01:25:15.179 --> 01:25:17.990 align:start position:0% and then go out to the web page if we are<01:25:15.300> able<01:25:15.600> to<01:25:15.719> and<01:25:16.080> look<01:25:16.380> at<01:25:16.560> the<01:25:16.800> Json<01:25:17.100> if<01:25:17.820> not 01:25:17.990 --> 01:25:18.000 align:start position:0% are able to and look at the Json if not 01:25:18.000 --> 01:25:21.229 align:start position:0% are able to and look at the Json if not I<01:25:18.300> have<01:25:18.480> a<01:25:18.719> tool<01:25:19.140> that<01:25:19.440> will<01:25:19.620> fuzz<01:25:20.219> apis<01:25:20.760> for<01:25:21.120> us 01:25:21.229 --> 01:25:21.239 align:start position:0% I have a tool that will fuzz apis for us 01:25:21.239 --> 01:25:23.030 align:start position:0% I have a tool that will fuzz apis for us and<01:25:21.420> actually<01:25:21.600> give<01:25:21.780> us<01:25:21.900> the<01:25:22.080> Json<01:25:22.380> right<01:25:22.800> here 01:25:23.030 --> 01:25:23.040 align:start position:0% and actually give us the Json right here 01:25:23.040 --> 01:25:26.450 align:start position:0% and actually give us the Json right here in<01:25:23.940> our<01:25:24.239> terminal<01:25:24.780> and<01:25:25.560> you<01:25:25.739> can<01:25:25.860> go<01:25:26.219> check 01:25:26.450 --> 01:25:26.460 align:start position:0% in our terminal and you can go check 01:25:26.460 --> 01:25:28.010 align:start position:0% in our terminal and you can go check that<01:25:26.640> video<01:25:26.880> out<01:25:27.120> I'll<01:25:27.300> link<01:25:27.480> it<01:25:27.659> in<01:25:27.840> the 01:25:28.010 --> 01:25:28.020 align:start position:0% that video out I'll link it in the 01:25:28.020 --> 01:25:29.630 align:start position:0% that video out I'll link it in the description<01:25:28.260> if<01:25:28.620> you<01:25:28.739> would<01:25:28.920> like<01:25:29.040> to<01:25:29.280> build 01:25:29.630 --> 01:25:29.640 align:start position:0% description if you would like to build 01:25:29.640 --> 01:25:32.090 align:start position:0% description if you would like to build that<01:25:29.880> tool<01:25:30.179> it'll<01:25:30.719> save<01:25:30.960> you<01:25:31.140> some<01:25:31.739> time 01:25:32.090 --> 01:25:32.100 align:start position:0% that tool it'll save you some time 01:25:32.100 --> 01:25:34.970 align:start position:0% that tool it'll save you some time having<01:25:32.400> to<01:25:32.580> to<01:25:33.060> go<01:25:33.420> out<01:25:33.600> and<01:25:34.020> look<01:25:34.380> at<01:25:34.560> the<01:25:34.739> Json 01:25:34.970 --> 01:25:34.980 align:start position:0% having to to go out and look at the Json 01:25:34.980 --> 01:25:36.590 align:start position:0% having to to go out and look at the Json itself<01:25:35.400> and<01:25:35.699> it'll<01:25:35.880> just<01:25:36.060> print<01:25:36.179> it<01:25:36.360> right 01:25:36.590 --> 01:25:36.600 align:start position:0% itself and it'll just print it right 01:25:36.600 --> 01:25:38.510 align:start position:0% itself and it'll just print it right here<01:25:36.780> in<01:25:37.020> the<01:25:37.199> terminal<01:25:37.440> for<01:25:37.679> you<01:25:37.860> so<01:25:38.280> with 01:25:38.510 --> 01:25:38.520 align:start position:0% here in the terminal for you so with 01:25:38.520 --> 01:25:41.510 align:start position:0% here in the terminal for you so with that<01:25:38.699> that<01:25:39.060> is<01:25:39.360> fuff<01:25:39.960> and<01:25:40.380> how<01:25:40.620> we<01:25:40.739> fuzz<01:25:41.159> for 01:25:41.510 --> 01:25:41.520 align:start position:0% that that is fuff and how we fuzz for 01:25:41.520 --> 01:25:43.970 align:start position:0% that that is fuff and how we fuzz for subdomains<01:25:42.239> and<01:25:42.540> directories<01:25:43.199> all<01:25:43.500> right<01:25:43.679> so 01:25:43.970 --> 01:25:43.980 align:start position:0% subdomains and directories all right so 01:25:43.980 --> 01:25:46.790 align:start position:0% subdomains and directories all right so it<01:25:44.219> is<01:25:44.340> always<01:25:44.580> good<01:25:45.000> to<01:25:45.360> have<01:25:45.900> a<01:25:46.260> couple<01:25:46.560> of 01:25:46.790 --> 01:25:46.800 align:start position:0% it is always good to have a couple of 01:25:46.800 --> 01:25:49.790 align:start position:0% it is always good to have a couple of tools<01:25:47.400> in<01:25:48.300> your<01:25:48.600> tool<01:25:48.960> belt<01:25:49.199> so<01:25:49.380> you<01:25:49.500> can<01:25:49.620> go 01:25:49.790 --> 01:25:49.800 align:start position:0% tools in your tool belt so you can go 01:25:49.800 --> 01:25:52.250 align:start position:0% tools in your tool belt so you can go ahead<01:25:49.980> and<01:25:50.460> run<01:25:50.760> derb<01:25:51.420> like<01:25:51.600> this<01:25:51.780> and<01:25:52.020> we<01:25:52.140> can 01:25:52.250 --> 01:25:52.260 align:start position:0% ahead and run derb like this and we can 01:25:52.260 --> 01:25:56.149 align:start position:0% ahead and run derb like this and we can run<01:25:52.440> a<01:25:53.239> yahoo.com<01:25:54.260> and<01:25:55.260> we<01:25:55.500> don't<01:25:55.620> really<01:25:55.800> need 01:25:56.149 --> 01:25:56.159 align:start position:0% run a yahoo.com and we don't really need 01:25:56.159 --> 01:25:58.490 align:start position:0% run a yahoo.com and we don't really need any<01:25:56.580> more<01:25:56.880> than<01:25:57.300> just<01:25:57.540> this<01:25:57.840> right<01:25:58.020> here<01:25:58.199> so 01:25:58.490 --> 01:25:58.500 align:start position:0% any more than just this right here so 01:25:58.500 --> 01:26:02.810 align:start position:0% any more than just this right here so it's<01:25:58.860> just<01:25:59.040> an<01:25:59.219> HTTP<01:26:00.260> s<01:26:01.260> and<01:26:02.159> then<01:26:02.280> we'll<01:26:02.580> run 01:26:02.810 --> 01:26:02.820 align:start position:0% it's just an HTTP s and then we'll run 01:26:02.820 --> 01:26:04.970 align:start position:0% it's just an HTTP s and then we'll run yahoo.com<01:26:03.540> and<01:26:03.960> it'll<01:26:04.199> automatically<01:26:04.679> start 01:26:04.970 --> 01:26:04.980 align:start position:0% yahoo.com and it'll automatically start 01:26:04.980 --> 01:26:07.310 align:start position:0% yahoo.com and it'll automatically start fuzzing<01:26:05.639> for<01:26:06.239> us<01:26:06.420> just<01:26:06.600> like<01:26:06.780> that<01:26:06.960> it's 01:26:07.310 --> 01:26:07.320 align:start position:0% fuzzing for us just like that it's 01:26:07.320 --> 01:26:09.590 align:start position:0% fuzzing for us just like that it's really<01:26:07.620> simple<01:26:07.860> to<01:26:08.159> use<01:26:08.280> so<01:26:08.760> sometimes<01:26:09.179> fuff 01:26:09.590 --> 01:26:09.600 align:start position:0% really simple to use so sometimes fuff 01:26:09.600 --> 01:26:10.910 align:start position:0% really simple to use so sometimes fuff might<01:26:09.840> give<01:26:10.020> you<01:26:10.080> some<01:26:10.260> errors<01:26:10.560> or<01:26:10.679> it's<01:26:10.860> not 01:26:10.910 --> 01:26:10.920 align:start position:0% might give you some errors or it's not 01:26:10.920 --> 01:26:12.229 align:start position:0% might give you some errors or it's not working<01:26:11.100> quite<01:26:11.340> right<01:26:11.520> and<01:26:11.760> it's<01:26:11.880> always<01:26:12.000> good 01:26:12.229 --> 01:26:12.239 align:start position:0% working quite right and it's always good 01:26:12.239 --> 01:26:14.689 align:start position:0% working quite right and it's always good to<01:26:12.420> know<01:26:12.600> of<01:26:12.960> other<01:26:13.260> tools<01:26:13.739> one<01:26:14.340> of<01:26:14.460> the<01:26:14.520> cool 01:26:14.689 --> 01:26:14.699 align:start position:0% to know of other tools one of the cool 01:26:14.699 --> 01:26:16.910 align:start position:0% to know of other tools one of the cool things<01:26:14.940> about<01:26:15.239> derb<01:26:15.840> is<01:26:16.199> you<01:26:16.500> can<01:26:16.620> run<01:26:16.739> it 01:26:16.910 --> 01:26:16.920 align:start position:0% things about derb is you can run it 01:26:16.920 --> 01:26:18.709 align:start position:0% things about derb is you can run it recursively<01:26:17.520> it's<01:26:17.760> so<01:26:17.940> once<01:26:18.179> it<01:26:18.239> runs<01:26:18.540> all<01:26:18.659> the 01:26:18.709 --> 01:26:18.719 align:start position:0% recursively it's so once it runs all the 01:26:18.719 --> 01:26:20.629 align:start position:0% recursively it's so once it runs all the way<01:26:18.780> through<01:26:18.960> your<01:26:19.139> word<01:26:19.320> list<01:26:19.560> and<01:26:20.219> it<01:26:20.460> let's 01:26:20.629 --> 01:26:20.639 align:start position:0% way through your word list and it let's 01:26:20.639 --> 01:26:24.110 align:start position:0% way through your word list and it let's say<01:26:20.880> it<01:26:21.060> found<01:26:21.239> yahoo.com<01:26:22.040> football<01:26:23.040> the<01:26:23.940> next 01:26:24.110 --> 01:26:24.120 align:start position:0% say it found yahoo.com football the next 01:26:24.120 --> 01:26:26.030 align:start position:0% say it found yahoo.com football the next time<01:26:24.360> it<01:26:24.600> runs<01:26:24.780> it'll<01:26:25.080> run<01:26:25.260> yahoo.com 01:26:26.030 --> 01:26:26.040 align:start position:0% time it runs it'll run yahoo.com 01:26:26.040 --> 01:26:28.910 align:start position:0% time it runs it'll run yahoo.com football<01:26:26.699> and<01:26:27.120> then<01:26:27.239> it<01:26:27.420> will<01:26:27.600> look<01:26:27.780> for<01:26:28.080> more 01:26:28.910 --> 01:26:28.920 align:start position:0% football and then it will look for more 01:26:28.920 --> 01:26:30.290 align:start position:0% football and then it will look for more directories<01:26:29.520> within<01:26:29.940> that<01:26:30.120> football 01:26:30.290 --> 01:26:30.300 align:start position:0% directories within that football 01:26:30.300 --> 01:26:32.810 align:start position:0% directories within that football directory<01:26:30.960> which<01:26:31.199> is<01:26:31.380> really<01:26:31.920> cool 01:26:32.810 --> 01:26:32.820 align:start position:0% directory which is really cool 01:26:32.820 --> 01:26:36.110 align:start position:0% directory which is really cool so<01:26:33.300> derb<01:26:33.840> is<01:26:34.080> also<01:26:34.500> a<01:26:34.860> backup<01:26:35.219> fuzzer<01:26:35.699> just<01:26:36.000> in 01:26:36.110 --> 01:26:36.120 align:start position:0% so derb is also a backup fuzzer just in 01:26:36.120 --> 01:26:37.970 align:start position:0% so derb is also a backup fuzzer just in case<01:26:36.239> fuff<01:26:36.659> isn't<01:26:36.960> working<01:26:37.139> for<01:26:37.380> you<01:26:37.500> another 01:26:37.970 --> 01:26:37.980 align:start position:0% case fuff isn't working for you another 01:26:37.980 --> 01:26:40.010 align:start position:0% case fuff isn't working for you another helpful<01:26:38.340> tool<01:26:38.699> that<01:26:39.120> you're<01:26:39.360> going<01:26:39.659> to<01:26:39.840> use 01:26:40.010 --> 01:26:40.020 align:start position:0% helpful tool that you're going to use 01:26:40.020 --> 01:26:44.209 align:start position:0% helpful tool that you're going to use especially<01:26:40.739> inside<01:26:41.340> of<01:26:41.880> ctfs<01:26:42.659> is<01:26:43.020> a<01:26:43.320> WP<01:26:43.800> scan 01:26:44.209 --> 01:26:44.219 align:start position:0% especially inside of ctfs is a WP scan 01:26:44.219 --> 01:26:46.070 align:start position:0% especially inside of ctfs is a WP scan and<01:26:44.520> you're<01:26:44.639> going<01:26:44.760> to<01:26:44.880> use<01:26:45.060> this<01:26:45.659> with 01:26:46.070 --> 01:26:46.080 align:start position:0% and you're going to use this with 01:26:46.080 --> 01:26:48.169 align:start position:0% and you're going to use this with WordPress<01:26:46.620> sites<01:26:47.040> so<01:26:47.159> I've<01:26:47.340> gone<01:26:47.580> ahead<01:26:47.820> and 01:26:48.169 --> 01:26:48.179 align:start position:0% WordPress sites so I've gone ahead and 01:26:48.179 --> 01:26:50.870 align:start position:0% WordPress sites so I've gone ahead and opened<01:26:48.540> up<01:26:48.659> hack<01:26:48.840> the<01:26:49.080> box<01:26:49.260> and<01:26:50.219> I<01:26:50.460> have<01:26:50.639> a 01:26:50.870 --> 01:26:50.880 align:start position:0% opened up hack the box and I have a 01:26:50.880 --> 01:26:53.870 align:start position:0% opened up hack the box and I have a tenant<01:26:51.239> running<01:26:51.480> here<01:26:51.780> and<01:26:52.199> if<01:26:52.560> you<01:26:52.920> have<01:26:53.580> a 01:26:53.870 --> 01:26:53.880 align:start position:0% tenant running here and if you have a 01:26:53.880 --> 01:26:55.189 align:start position:0% tenant running here and if you have a hack<01:26:54.120> the<01:26:54.239> box<01:26:54.420> subscription<01:26:54.840> and<01:26:55.080> you're 01:26:55.189 --> 01:26:55.199 align:start position:0% hack the box subscription and you're 01:26:55.199 --> 01:26:56.870 align:start position:0% hack the box subscription and you're wanting<01:26:55.440> to<01:26:55.560> follow<01:26:55.679> along<01:26:55.860> you<01:26:56.219> will<01:26:56.340> need<01:26:56.580> to 01:26:56.870 --> 01:26:56.880 align:start position:0% wanting to follow along you will need to 01:26:56.880 --> 01:27:00.410 align:start position:0% wanting to follow along you will need to add<01:26:57.800> tenant.htb<01:26:58.800> to<01:26:58.980> your<01:26:59.400> Etsy<01:26:59.580> host<01:26:59.880> to<01:27:00.120> file 01:27:00.410 --> 01:27:00.420 align:start position:0% add tenant.htb to your Etsy host to file 01:27:00.420 --> 01:27:04.610 align:start position:0% add tenant.htb to your Etsy host to file which<01:27:01.199> I<01:27:01.440> have<01:27:01.560> already<01:27:01.739> done<01:27:02.040> so<01:27:02.820> the<01:27:03.300> wp<01:27:03.840> scan 01:27:04.610 --> 01:27:04.620 align:start position:0% which I have already done so the wp scan 01:27:04.620 --> 01:27:07.070 align:start position:0% which I have already done so the wp scan tool<01:27:05.159> is<01:27:05.340> going<01:27:05.520> to<01:27:05.639> go<01:27:05.760> out<01:27:05.880> and<01:27:06.239> look<01:27:06.480> at<01:27:06.719> all 01:27:07.070 --> 01:27:07.080 align:start position:0% tool is going to go out and look at all 01:27:07.080 --> 01:27:10.550 align:start position:0% tool is going to go out and look at all of<01:27:07.380> the<01:27:08.040> plugins<01:27:08.760> on<01:27:09.300> the<01:27:09.540> WordPress<01:27:09.900> site<01:27:10.260> and 01:27:10.550 --> 01:27:10.560 align:start position:0% of the plugins on the WordPress site and 01:27:10.560 --> 01:27:12.110 align:start position:0% of the plugins on the WordPress site and see<01:27:10.679> if<01:27:10.800> any<01:27:10.920> of<01:27:11.100> them<01:27:11.219> are<01:27:11.340> vulnerable<01:27:11.699> if<01:27:12.000> any 01:27:12.110 --> 01:27:12.120 align:start position:0% see if any of them are vulnerable if any 01:27:12.120 --> 01:27:14.090 align:start position:0% see if any of them are vulnerable if any of<01:27:12.300> them<01:27:12.420> are<01:27:12.600> out<01:27:12.719> of<01:27:12.900> date<01:27:13.020> it's<01:27:13.620> going<01:27:13.800> to 01:27:14.090 --> 01:27:14.100 align:start position:0% of them are out of date it's going to 01:27:14.100 --> 01:27:16.790 align:start position:0% of them are out of date it's going to check<01:27:14.580> the<01:27:15.120> actual<01:27:15.480> theme<01:27:15.960> and<01:27:16.380> see<01:27:16.500> how<01:27:16.679> old 01:27:16.790 --> 01:27:16.800 align:start position:0% check the actual theme and see how old 01:27:16.800 --> 01:27:18.290 align:start position:0% check the actual theme and see how old it<01:27:16.980> is<01:27:17.100> and<01:27:17.340> how<01:27:17.460> long<01:27:17.580> it's<01:27:17.760> been<01:27:17.940> since<01:27:18.120> it's 01:27:18.290 --> 01:27:18.300 align:start position:0% it is and how long it's been since it's 01:27:18.300 --> 01:27:19.910 align:start position:0% it is and how long it's been since it's had<01:27:18.540> updates<01:27:18.960> and<01:27:19.320> we<01:27:19.500> can<01:27:19.620> go<01:27:19.679> ahead<01:27:19.800> and 01:27:19.910 --> 01:27:19.920 align:start position:0% had updates and we can go ahead and 01:27:19.920 --> 01:27:22.490 align:start position:0% had updates and we can go ahead and check<01:27:20.219> out<01:27:20.400> WordPress<01:27:21.120> scan<01:27:21.900> right<01:27:22.139> here<01:27:22.260> the 01:27:22.490 --> 01:27:22.500 align:start position:0% check out WordPress scan right here the 01:27:22.500 --> 01:27:25.129 align:start position:0% check out WordPress scan right here the wp<01:27:22.860> scan<01:27:23.280> Dash<01:27:23.580> help<01:27:23.760> and<01:27:24.420> it<01:27:24.600> will<01:27:24.719> tell<01:27:24.960> us 01:27:25.129 --> 01:27:25.139 align:start position:0% wp scan Dash help and it will tell us 01:27:25.139 --> 01:27:26.810 align:start position:0% wp scan Dash help and it will tell us all<01:27:25.620> of<01:27:25.739> the<01:27:25.980> different<01:27:26.159> flags<01:27:26.639> and 01:27:26.810 --> 01:27:26.820 align:start position:0% all of the different flags and 01:27:26.820 --> 01:27:29.629 align:start position:0% all of the different flags and everything<01:27:27.000> that<01:27:27.780> we<01:27:27.960> are<01:27:28.080> able<01:27:28.380> to<01:27:28.500> use<01:27:28.800> and 01:27:29.629 --> 01:27:29.639 align:start position:0% everything that we are able to use and 01:27:29.639 --> 01:27:32.270 align:start position:0% everything that we are able to use and one<01:27:29.940> thing<01:27:30.120> that<01:27:30.360> I<01:27:30.600> can<01:27:30.719> never<01:27:30.840> remember<01:27:31.280> what 01:27:32.270 --> 01:27:32.280 align:start position:0% one thing that I can never remember what 01:27:32.280 --> 01:27:34.129 align:start position:0% one thing that I can never remember what it<01:27:32.460> actually<01:27:32.760> looks<01:27:33.360> like<01:27:33.420> is<01:27:33.719> this<01:27:33.960> right 01:27:34.129 --> 01:27:34.139 align:start position:0% it actually looks like is this right 01:27:34.139 --> 01:27:36.590 align:start position:0% it actually looks like is this right here<01:27:34.320> is<01:27:34.620> the<01:27:35.100> dash<01:27:35.520> dash<01:27:35.820> plug-in<01:27:36.179> detection 01:27:36.590 --> 01:27:36.600 align:start position:0% here is the dash dash plug-in detection 01:27:36.600 --> 01:27:39.350 align:start position:0% here is the dash dash plug-in detection so<01:27:37.080> what<01:27:37.320> we<01:27:37.560> will<01:27:37.860> do<01:27:38.159> is<01:27:38.340> we'll<01:27:38.460> type<01:27:38.639> in<01:27:38.820> WP 01:27:39.350 --> 01:27:39.360 align:start position:0% so what we will do is we'll type in WP 01:27:39.360 --> 01:27:43.629 align:start position:0% so what we will do is we'll type in WP scan<01:27:40.159> dash<01:27:41.159> dash<01:27:41.520> URL 01:27:43.629 --> 01:27:43.639 align:start position:0% scan dash dash URL 01:27:43.639 --> 01:27:48.070 align:start position:0% scan dash dash URL HTTP<01:27:44.639> slash<01:27:45.679> and<01:27:46.679> then<01:27:46.800> we're<01:27:46.920> going<01:27:47.040> to<01:27:47.159> go 01:27:48.070 --> 01:27:48.080 align:start position:0% HTTP slash and then we're going to go 01:27:48.080 --> 01:27:51.050 align:start position:0% HTTP slash and then we're going to go tenant.htb<01:27:49.080> and<01:27:49.739> then<01:27:49.860> this<01:27:50.100> Dash<01:27:50.580> e<01:27:50.820> right 01:27:51.050 --> 01:27:51.060 align:start position:0% tenant.htb and then this Dash e right 01:27:51.060 --> 01:27:52.490 align:start position:0% tenant.htb and then this Dash e right here<01:27:51.239> is<01:27:51.300> going<01:27:51.540> to<01:27:51.600> tell<01:27:51.719> it<01:27:51.840> that<01:27:52.020> we<01:27:52.199> want<01:27:52.320> to 01:27:52.490 --> 01:27:52.500 align:start position:0% here is going to tell it that we want to 01:27:52.500 --> 01:27:56.510 align:start position:0% here is going to tell it that we want to check<01:27:52.920> all<01:27:53.460> of<01:27:53.940> the<01:27:54.360> plugins<01:27:54.980> I<01:27:55.980> sometimes 01:27:56.510 --> 01:27:56.520 align:start position:0% check all of the plugins I sometimes 01:27:56.520 --> 01:27:58.370 align:start position:0% check all of the plugins I sometimes call<01:27:56.699> it<01:27:56.880> all<01:27:57.000> ports<01:27:57.420> out<01:27:57.600> of<01:27:57.780> habit<01:27:58.080> but<01:27:58.260> I 01:27:58.370 --> 01:27:58.380 align:start position:0% call it all ports out of habit but I 01:27:58.380 --> 01:27:59.870 align:start position:0% call it all ports out of habit but I think<01:27:58.500> it's<01:27:58.620> all<01:27:58.800> plugins<01:27:59.159> so<01:27:59.460> we<01:27:59.760> can 01:27:59.870 --> 01:27:59.880 align:start position:0% think it's all plugins so we can 01:27:59.880 --> 01:28:03.169 align:start position:0% think it's all plugins so we can actually<01:28:00.179> just<01:28:00.600> look<01:28:01.199> if<01:28:01.560> we<01:28:01.800> scroll<01:28:02.219> up<01:28:02.460> we're 01:28:03.169 --> 01:28:03.179 align:start position:0% actually just look if we scroll up we're 01:28:03.179 --> 01:28:06.410 align:start position:0% actually just look if we scroll up we're going<01:28:03.420> to<01:28:03.540> enumerate<01:28:04.460> all<01:28:05.460> plugins<01:28:05.880> right 01:28:06.410 --> 01:28:06.420 align:start position:0% going to enumerate all plugins right 01:28:06.420 --> 01:28:10.070 align:start position:0% going to enumerate all plugins right here<01:28:06.659> and<01:28:07.380> we<01:28:07.920> want<01:28:08.159> to<01:28:08.460> use<01:28:08.760> the<01:28:09.179> dash<01:28:09.600> dash 01:28:10.070 --> 01:28:10.080 align:start position:0% here and we want to use the dash dash 01:28:10.080 --> 01:28:13.729 align:start position:0% here and we want to use the dash dash and<01:28:10.440> then<01:28:10.560> we<01:28:10.800> want<01:28:10.980> plugins<01:28:12.020> Dash<01:28:13.020> detection 01:28:13.729 --> 01:28:13.739 align:start position:0% and then we want plugins Dash detection 01:28:13.739 --> 01:28:17.270 align:start position:0% and then we want plugins Dash detection and<01:28:14.699> then<01:28:14.820> we<01:28:15.179> want<01:28:15.360> to<01:28:15.480> use<01:28:16.040> aggressive<01:28:17.040> and 01:28:17.270 --> 01:28:17.280 align:start position:0% and then we want to use aggressive and 01:28:17.280 --> 01:28:19.790 align:start position:0% and then we want to use aggressive and then<01:28:17.400> you<01:28:17.580> can<01:28:17.699> do<01:28:17.880> a<01:28:18.239> dash<01:28:18.719> o<01:28:19.020> if<01:28:19.380> you<01:28:19.500> want<01:28:19.620> to 01:28:19.790 --> 01:28:19.800 align:start position:0% then you can do a dash o if you want to 01:28:19.800 --> 01:28:22.490 align:start position:0% then you can do a dash o if you want to save<01:28:19.920> this<01:28:20.219> in<01:28:20.520> an<01:28:20.699> in<01:28:20.880> a<01:28:21.120> file<01:28:21.360> I<01:28:22.139> pretty<01:28:22.320> much 01:28:22.490 --> 01:28:22.500 align:start position:0% save this in an in a file I pretty much 01:28:22.500 --> 01:28:24.290 align:start position:0% save this in an in a file I pretty much never<01:28:22.739> do<01:28:22.980> that<01:28:23.100> I'll<01:28:23.400> just<01:28:23.639> open<01:28:23.760> a<01:28:23.940> new<01:28:24.060> tab 01:28:24.290 --> 01:28:24.300 align:start position:0% never do that I'll just open a new tab 01:28:24.300 --> 01:28:26.330 align:start position:0% never do that I'll just open a new tab and<01:28:24.420> come<01:28:24.600> back<01:28:24.800> sometimes<01:28:25.800> I'll<01:28:26.040> have<01:28:26.219> a 01:28:26.330 --> 01:28:26.340 align:start position:0% and come back sometimes I'll have a 01:28:26.340 --> 01:28:27.590 align:start position:0% and come back sometimes I'll have a whole<01:28:26.400> bunch<01:28:26.580> of<01:28:26.699> tabs<01:28:27.000> open<01:28:27.120> up<01:28:27.300> here<01:28:27.480> and 01:28:27.590 --> 01:28:27.600 align:start position:0% whole bunch of tabs open up here and 01:28:27.600 --> 01:28:30.470 align:start position:0% whole bunch of tabs open up here and it's<01:28:27.780> not<01:28:27.960> always<01:28:28.139> that<01:28:28.920> helpful<01:28:29.280> so<01:28:30.120> it<01:28:30.360> will 01:28:30.470 --> 01:28:30.480 align:start position:0% it's not always that helpful so it will 01:28:30.480 --> 01:28:33.050 align:start position:0% it's not always that helpful so it will flag<01:28:31.020> things<01:28:31.620> like<01:28:31.920> this<01:28:32.159> and<01:28:32.520> tell<01:28:32.699> you<01:28:32.820> that 01:28:33.050 --> 01:28:33.060 align:start position:0% flag things like this and tell you that 01:28:33.060 --> 01:28:36.709 align:start position:0% flag things like this and tell you that a<01:28:33.239> version<01:28:33.600> is<01:28:34.199> out<01:28:34.560> of<01:28:34.739> date<01:28:34.980> and<01:28:35.940> I<01:28:36.420> told<01:28:36.540> you 01:28:36.709 --> 01:28:36.719 align:start position:0% a version is out of date and I told you 01:28:36.719 --> 01:28:39.590 align:start position:0% a version is out of date and I told you this<01:28:37.020> in<01:28:37.500> the<01:28:37.800> last<01:28:37.920> video<01:28:38.219> but<01:28:38.699> I<01:28:39.120> especially 01:28:39.590 --> 01:28:39.600 align:start position:0% this in the last video but I especially 01:28:39.600 --> 01:28:42.530 align:start position:0% this in the last video but I especially am<01:28:39.960> really<01:28:40.199> bad<01:28:40.560> with<01:28:41.400> WP<01:28:41.880> scan<01:28:42.179> because<01:28:42.360> you 01:28:42.530 --> 01:28:42.540 align:start position:0% am really bad with WP scan because you 01:28:42.540 --> 01:28:45.110 align:start position:0% am really bad with WP scan because you get<01:28:42.659> a<01:28:42.719> lot<01:28:42.780> of<01:28:42.900> information<01:28:43.440> but<01:28:44.280> you<01:28:44.699> should 01:28:45.110 --> 01:28:45.120 align:start position:0% get a lot of information but you should 01:28:45.120 --> 01:28:47.870 align:start position:0% get a lot of information but you should read<01:28:45.960> all<01:28:46.560> the<01:28:46.679> way<01:28:46.800> through<01:28:47.040> all<01:28:47.280> of<01:28:47.400> this<01:28:47.580> I 01:28:47.870 --> 01:28:47.880 align:start position:0% read all the way through all of this I 01:28:47.880 --> 01:28:49.910 align:start position:0% read all the way through all of this I remember<01:28:48.060> doing<01:28:48.300> a<01:28:48.540> CTF<01:28:49.020> about<01:28:49.320> six<01:28:49.620> months 01:28:49.910 --> 01:28:49.920 align:start position:0% remember doing a CTF about six months 01:28:49.920 --> 01:28:53.270 align:start position:0% remember doing a CTF about six months ago<01:28:50.100> and<01:28:50.639> I<01:28:50.820> ran<01:28:51.060> a<01:28:51.300> WP<01:28:51.840> scan<01:28:52.260> and<01:28:52.800> I<01:28:52.980> just<01:28:53.100> like 01:28:53.270 --> 01:28:53.280 align:start position:0% ago and I ran a WP scan and I just like 01:28:53.280 --> 01:28:55.550 align:start position:0% ago and I ran a WP scan and I just like skimmed<01:28:53.699> through<01:28:53.880> it<01:28:54.060> and<01:28:54.780> I<01:28:55.199> ended<01:28:55.380> up 01:28:55.550 --> 01:28:55.560 align:start position:0% skimmed through it and I ended up 01:28:55.560 --> 01:28:58.729 align:start position:0% skimmed through it and I ended up missing<01:28:56.100> a<01:28:56.580> vulnerability<01:28:57.239> that<01:28:58.020> gave<01:28:58.500> me 01:28:58.729 --> 01:28:58.739 align:start position:0% missing a vulnerability that gave me 01:28:58.739 --> 01:29:00.890 align:start position:0% missing a vulnerability that gave me remote<01:28:59.100> code<01:28:59.400> execution<01:28:59.940> and<01:29:00.239> I<01:29:00.480> wasted 01:29:00.890 --> 01:29:00.900 align:start position:0% remote code execution and I wasted 01:29:00.900 --> 01:29:03.110 align:start position:0% remote code execution and I wasted several<01:29:01.440> hours<01:29:01.560> of<01:29:01.860> my<01:29:02.100> time<01:29:02.280> enumerating 01:29:03.110 --> 01:29:03.120 align:start position:0% several hours of my time enumerating 01:29:03.120 --> 01:29:05.330 align:start position:0% several hours of my time enumerating when<01:29:03.659> I<01:29:04.139> should<01:29:04.320> have<01:29:04.440> just<01:29:04.620> read<01:29:04.860> the<01:29:05.100> entire 01:29:05.330 --> 01:29:05.340 align:start position:0% when I should have just read the entire 01:29:05.340 --> 01:29:09.169 align:start position:0% when I should have just read the entire scan<01:29:05.760> so<01:29:06.179> make<01:29:06.480> sure<01:29:06.659> you<01:29:07.620> read<01:29:08.040> the<01:29:08.760> entire 01:29:09.169 --> 01:29:09.179 align:start position:0% scan so make sure you read the entire 01:29:09.179 --> 01:29:12.050 align:start position:0% scan so make sure you read the entire scan<01:29:09.659> when<01:29:10.139> you<01:29:10.320> run<01:29:10.560> one<01:29:10.800> it<01:29:11.400> might<01:29:11.580> take<01:29:11.880> you 01:29:12.050 --> 01:29:12.060 align:start position:0% scan when you run one it might take you 01:29:12.060 --> 01:29:14.990 align:start position:0% scan when you run one it might take you a<01:29:12.480> little<01:29:12.600> bit<01:29:13.020> of<01:29:13.260> extra<01:29:13.500> time<01:29:13.800> but<01:29:14.520> it<01:29:14.880> will 01:29:14.990 --> 01:29:15.000 align:start position:0% a little bit of extra time but it will 01:29:15.000 --> 01:29:16.910 align:start position:0% a little bit of extra time but it will always<01:29:15.179> be<01:29:15.420> worth<01:29:15.659> it<01:29:15.840> because<01:29:16.139> it<01:29:16.560> will<01:29:16.679> give 01:29:16.910 --> 01:29:16.920 align:start position:0% always be worth it because it will give 01:29:16.920 --> 01:29:19.430 align:start position:0% always be worth it because it will give you<01:29:17.100> information<01:29:17.580> even<01:29:18.420> if<01:29:18.840> you<01:29:19.080> think<01:29:19.260> it 01:29:19.430 --> 01:29:19.440 align:start position:0% you information even if you think it 01:29:19.440 --> 01:29:21.649 align:start position:0% you information even if you think it might<01:29:19.620> not<01:29:19.739> be<01:29:19.920> helpful<01:29:20.219> like<01:29:20.880> right<01:29:21.179> here<01:29:21.420> it 01:29:21.649 --> 01:29:21.659 align:start position:0% might not be helpful like right here it 01:29:21.659 --> 01:29:23.750 align:start position:0% might not be helpful like right here it doesn't<01:29:21.840> flag<01:29:22.139> this<01:29:22.440> but<01:29:23.040> it<01:29:23.280> might<01:29:23.400> be<01:29:23.520> worth 01:29:23.750 --> 01:29:23.760 align:start position:0% doesn't flag this but it might be worth 01:29:23.760 --> 01:29:26.450 align:start position:0% doesn't flag this but it might be worth going<01:29:24.120> out<01:29:24.300> and<01:29:24.540> checking<01:29:24.960> this<01:29:25.199> version<01:29:25.500> 5.6 01:29:26.450 --> 01:29:26.460 align:start position:0% going out and checking this version 5.6 01:29:26.460 --> 01:29:28.729 align:start position:0% going out and checking this version 5.6 it's<01:29:26.820> insecure<01:29:27.360> on<01:29:27.480> this<01:29:27.780> specific<01:29:28.320> release 01:29:28.729 --> 01:29:28.739 align:start position:0% it's insecure on this specific release 01:29:28.739 --> 01:29:31.490 align:start position:0% it's insecure on this specific release and<01:29:29.400> you<01:29:29.580> can<01:29:29.639> go<01:29:29.880> and<01:29:30.239> check<01:29:30.480> this<01:29:30.960> these 01:29:31.490 --> 01:29:31.500 align:start position:0% and you can go and check this these 01:29:31.500 --> 01:29:33.890 align:start position:0% and you can go and check this these different<01:29:31.679> version<01:29:32.159> numbers<01:29:32.520> and<01:29:33.360> this<01:29:33.780> might 01:29:33.890 --> 01:29:33.900 align:start position:0% different version numbers and this might 01:29:33.900 --> 01:29:35.030 align:start position:0% different version numbers and this might take<01:29:34.080> a<01:29:34.199> little<01:29:34.320> while<01:29:34.500> because<01:29:34.739> we're 01:29:35.030 --> 01:29:35.040 align:start position:0% take a little while because we're 01:29:35.040 --> 01:29:38.030 align:start position:0% take a little while because we're running<01:29:35.280> the<01:29:35.580> aggressive<01:29:36.120> but<01:29:37.020> that<01:29:37.500> is<01:29:37.679> okay 01:29:38.030 --> 01:29:38.040 align:start position:0% running the aggressive but that is okay 01:29:38.040 --> 01:29:41.209 align:start position:0% running the aggressive but that is okay so<01:29:38.699> this<01:29:39.060> is<01:29:39.239> a<01:29:39.540> WP<01:29:39.960> scan<01:29:40.380> you're<01:29:40.980> going<01:29:41.159> to 01:29:41.209 --> 01:29:41.219 align:start position:0% so this is a WP scan you're going to 01:29:41.219 --> 01:29:42.830 align:start position:0% so this is a WP scan you're going to want<01:29:41.340> to<01:29:41.460> run<01:29:41.580> this<01:29:41.820> whenever<01:29:42.360> you<01:29:42.540> come 01:29:42.830 --> 01:29:42.840 align:start position:0% want to run this whenever you come 01:29:42.840 --> 01:29:46.070 align:start position:0% want to run this whenever you come across<01:29:43.620> WordPress<01:29:44.280> web<01:29:44.699> applications<01:29:45.239> it<01:29:45.900> is 01:29:46.070 --> 01:29:46.080 align:start position:0% across WordPress web applications it is 01:29:46.080 --> 01:29:47.689 align:start position:0% across WordPress web applications it is going<01:29:46.380> to<01:29:46.500> be<01:29:46.679> your<01:29:46.860> friend<01:29:47.040> you're<01:29:47.520> going<01:29:47.699> to 01:29:47.689 --> 01:29:47.699 align:start position:0% going to be your friend you're going to 01:29:47.699 --> 01:29:49.850 align:start position:0% going to be your friend you're going to use<01:29:47.880> it<01:29:48.060> regularly<01:29:48.540> throughout<01:29:49.440> your 01:29:49.850 --> 01:29:49.860 align:start position:0% use it regularly throughout your 01:29:49.860 --> 01:29:52.610 align:start position:0% use it regularly throughout your penetration<01:29:50.580> testing<01:29:51.420> career<01:29:51.900> especially<01:29:52.380> in 01:29:52.610 --> 01:29:52.620 align:start position:0% penetration testing career especially in 01:29:52.620 --> 01:29:55.310 align:start position:0% penetration testing career especially in the<01:29:52.739> world<01:29:52.860> of<01:29:53.040> CTS<01:29:53.520> and<01:29:54.060> always<01:29:54.239> remember 01:29:55.310 --> 01:29:55.320 align:start position:0% the world of CTS and always remember 01:29:55.320 --> 01:29:57.110 align:start position:0% the world of CTS and always remember read<01:29:55.739> the<01:29:55.980> output<01:29:56.219> in<01:29:56.699> this<01:29:56.820> video<01:29:56.940> we're 01:29:57.110 --> 01:29:57.120 align:start position:0% read the output in this video we're 01:29:57.120 --> 01:29:59.750 align:start position:0% read the output in this video we're going<01:29:57.360> to<01:29:57.540> cover<01:29:58.020> how<01:29:58.440> to<01:29:58.620> choose<01:29:59.280> a<01:29:59.580> bug 01:29:59.750 --> 01:29:59.760 align:start position:0% going to cover how to choose a bug 01:29:59.760 --> 01:30:02.149 align:start position:0% going to cover how to choose a bug Bounty<01:30:00.239> program<01:30:00.420> for<01:30:00.960> you<01:30:01.080> to<01:30:01.320> attack<01:30:01.620> one<01:30:02.040> of 01:30:02.149 --> 01:30:02.159 align:start position:0% Bounty program for you to attack one of 01:30:02.159 --> 01:30:03.290 align:start position:0% Bounty program for you to attack one of the<01:30:02.219> first<01:30:02.340> things<01:30:02.520> you<01:30:02.699> have<01:30:02.820> to<01:30:02.940> do<01:30:03.060> is 01:30:03.290 --> 01:30:03.300 align:start position:0% the first things you have to do is 01:30:03.300 --> 01:30:05.390 align:start position:0% the first things you have to do is figure<01:30:03.659> out<01:30:03.900> a<01:30:04.080> Target<01:30:04.440> that<01:30:04.800> you<01:30:04.980> want<01:30:05.159> to 01:30:05.390 --> 01:30:05.400 align:start position:0% figure out a Target that you want to 01:30:05.400 --> 01:30:07.669 align:start position:0% figure out a Target that you want to start<01:30:05.760> doing<01:30:06.060> your<01:30:06.360> recon<01:30:06.840> on<01:30:07.080> and<01:30:07.320> sometimes 01:30:07.669 --> 01:30:07.679 align:start position:0% start doing your recon on and sometimes 01:30:07.679 --> 01:30:10.370 align:start position:0% start doing your recon on and sometimes people<01:30:07.980> can<01:30:08.280> become<01:30:08.639> Paralyzed<01:30:09.480> by<01:30:09.840> analyzing 01:30:10.370 --> 01:30:10.380 align:start position:0% people can become Paralyzed by analyzing 01:30:10.380 --> 01:30:11.810 align:start position:0% people can become Paralyzed by analyzing all<01:30:10.679> the<01:30:10.739> different<01:30:10.920> targets<01:30:11.400> and<01:30:11.580> trying<01:30:11.760> to 01:30:11.810 --> 01:30:11.820 align:start position:0% all the different targets and trying to 01:30:11.820 --> 01:30:14.030 align:start position:0% all the different targets and trying to figure<01:30:11.940> out<01:30:12.120> which<01:30:12.420> one<01:30:12.600> they<01:30:13.139> want<01:30:13.440> to<01:30:13.679> attack 01:30:14.030 --> 01:30:14.040 align:start position:0% figure out which one they want to attack 01:30:14.040 --> 01:30:16.310 align:start position:0% figure out which one they want to attack first<01:30:14.639> and<01:30:15.179> so<01:30:15.360> I<01:30:15.480> want<01:30:15.659> to<01:30:15.780> try<01:30:15.960> and<01:30:16.080> help<01:30:16.199> you 01:30:16.310 --> 01:30:16.320 align:start position:0% first and so I want to try and help you 01:30:16.320 --> 01:30:17.810 align:start position:0% first and so I want to try and help you figure<01:30:16.500> out<01:30:16.620> how<01:30:16.800> to<01:30:16.920> narrow<01:30:17.280> down<01:30:17.520> your 01:30:17.810 --> 01:30:17.820 align:start position:0% figure out how to narrow down your 01:30:17.820 --> 01:30:19.790 align:start position:0% figure out how to narrow down your options<01:30:18.179> and<01:30:18.600> then<01:30:18.719> specifically<01:30:19.260> choose<01:30:19.620> one 01:30:19.790 --> 01:30:19.800 align:start position:0% options and then specifically choose one 01:30:19.800 --> 01:30:22.250 align:start position:0% options and then specifically choose one and<01:30:20.100> then<01:30:20.219> start<01:30:20.460> your<01:30:20.760> recon<01:30:21.239> process<01:30:21.840> with 01:30:22.250 --> 01:30:22.260 align:start position:0% and then start your recon process with 01:30:22.260 --> 01:30:24.350 align:start position:0% and then start your recon process with so<01:30:22.679> before<01:30:22.800> we<01:30:23.040> jump<01:30:23.159> into<01:30:23.400> this<01:30:23.580> a<01:30:23.820> too<01:30:23.940> far<01:30:24.179> I 01:30:24.350 --> 01:30:24.360 align:start position:0% so before we jump into this a too far I 01:30:24.360 --> 01:30:25.970 align:start position:0% so before we jump into this a too far I kind<01:30:24.480> of<01:30:24.600> wanted<01:30:24.719> to<01:30:24.900> give<01:30:25.020> you<01:30:25.199> a<01:30:25.500> little<01:30:25.739> bit 01:30:25.970 --> 01:30:25.980 align:start position:0% kind of wanted to give you a little bit 01:30:25.980 --> 01:30:28.310 align:start position:0% kind of wanted to give you a little bit of<01:30:26.400> encouragement<01:30:27.000> and<01:30:27.540> I'm<01:30:27.719> not<01:30:27.840> really<01:30:28.020> a 01:30:28.310 --> 01:30:28.320 align:start position:0% of encouragement and I'm not really a 01:30:28.320 --> 01:30:30.350 align:start position:0% of encouragement and I'm not really a Star<01:30:28.620> Wars<01:30:28.860> fan<01:30:29.159> but<01:30:29.580> I<01:30:29.820> came<01:30:29.940> across<01:30:30.239> this 01:30:30.350 --> 01:30:30.360 align:start position:0% Star Wars fan but I came across this 01:30:30.360 --> 01:30:32.390 align:start position:0% Star Wars fan but I came across this quote<01:30:30.719> a<01:30:31.080> really<01:30:31.260> long<01:30:31.440> time<01:30:31.679> ago<01:30:31.860> and<01:30:32.100> I<01:30:32.219> found 01:30:32.390 --> 01:30:32.400 align:start position:0% quote a really long time ago and I found 01:30:32.400 --> 01:30:35.450 align:start position:0% quote a really long time ago and I found it<01:30:32.580> to<01:30:32.820> be<01:30:33.060> really<01:30:33.420> helpful<01:30:33.840> and<01:30:34.560> it<01:30:34.800> says<01:30:35.100> you 01:30:35.450 --> 01:30:35.460 align:start position:0% it to be really helpful and it says you 01:30:35.460 --> 01:30:37.129 align:start position:0% it to be really helpful and it says you want<01:30:35.580> to<01:30:35.760> know<01:30:35.820> the<01:30:36.000> difference<01:30:36.179> between<01:30:36.600> the 01:30:37.129 --> 01:30:37.139 align:start position:0% want to know the difference between the 01:30:37.139 --> 01:30:39.649 align:start position:0% want to know the difference between the master<01:30:37.440> and<01:30:37.980> the<01:30:38.280> beginner<01:30:38.520> the<01:30:38.940> master<01:30:39.120> has 01:30:39.649 --> 01:30:39.659 align:start position:0% master and the beginner the master has 01:30:39.659 --> 01:30:42.050 align:start position:0% master and the beginner the master has failed<01:30:40.260> more<01:30:40.620> times<01:30:40.800> than<01:30:41.159> the<01:30:41.400> beginner<01:30:41.699> has 01:30:42.050 --> 01:30:42.060 align:start position:0% failed more times than the beginner has 01:30:42.060 --> 01:30:44.030 align:start position:0% failed more times than the beginner has even<01:30:42.360> tried<01:30:42.900> and<01:30:43.380> I<01:30:43.560> think<01:30:43.620> this<01:30:43.739> is<01:30:43.920> really 01:30:44.030 --> 01:30:44.040 align:start position:0% even tried and I think this is really 01:30:44.040 --> 01:30:45.950 align:start position:0% even tried and I think this is really helpful<01:30:44.340> when<01:30:44.639> trying<01:30:44.880> to<01:30:45.000> figure<01:30:45.120> out<01:30:45.360> how 01:30:45.950 --> 01:30:45.960 align:start position:0% helpful when trying to figure out how 01:30:45.960 --> 01:30:47.990 align:start position:0% helpful when trying to figure out how these<01:30:46.440> top<01:30:46.679> hackers<01:30:47.159> are<01:30:47.340> finding<01:30:47.699> so<01:30:47.880> many 01:30:47.990 --> 01:30:48.000 align:start position:0% these top hackers are finding so many 01:30:48.000 --> 01:30:49.790 align:start position:0% these top hackers are finding so many bugs<01:30:48.420> and<01:30:48.719> so<01:30:48.960> many<01:30:49.080> other<01:30:49.260> people<01:30:49.440> are 01:30:49.790 --> 01:30:49.800 align:start position:0% bugs and so many other people are 01:30:49.800 --> 01:30:51.410 align:start position:0% bugs and so many other people are struggling<01:30:50.219> it<01:30:50.699> is<01:30:50.820> because<01:30:50.940> they<01:30:51.239> have 01:30:51.410 --> 01:30:51.420 align:start position:0% struggling it is because they have 01:30:51.420 --> 01:30:54.050 align:start position:0% struggling it is because they have dedicated<01:30:51.840> a<01:30:52.139> lot<01:30:52.380> of<01:30:52.560> time<01:30:52.739> to<01:30:53.400> specific 01:30:54.050 --> 01:30:54.060 align:start position:0% dedicated a lot of time to specific 01:30:54.060 --> 01:30:56.149 align:start position:0% dedicated a lot of time to specific platforms<01:30:54.600> and<01:30:54.780> to<01:30:54.960> learning<01:30:55.199> in<01:30:55.739> this<01:30:55.980> craft 01:30:56.149 --> 01:30:56.159 align:start position:0% platforms and to learning in this craft 01:30:56.159 --> 01:30:58.250 align:start position:0% platforms and to learning in this craft and<01:30:56.520> so<01:30:56.699> we<01:30:56.880> just<01:30:57.060> have<01:30:57.239> to<01:30:57.360> keep<01:30:57.780> moving 01:30:58.250 --> 01:30:58.260 align:start position:0% and so we just have to keep moving 01:30:58.260 --> 01:31:00.290 align:start position:0% and so we just have to keep moving forward<01:30:58.560> every<01:30:59.040> day<01:30:59.280> and<01:30:59.580> you'll<01:30:59.760> be<01:30:59.880> getting 01:31:00.290 --> 01:31:00.300 align:start position:0% forward every day and you'll be getting 01:31:00.300 --> 01:31:02.030 align:start position:0% forward every day and you'll be getting better<01:31:00.719> we<01:31:01.139> might<01:31:01.320> get<01:31:01.500> you<01:31:01.620> down<01:31:01.800> you<01:31:01.920> know 01:31:02.030 --> 01:31:02.040 align:start position:0% better we might get you down you know 01:31:02.040 --> 01:31:02.930 align:start position:0% better we might get you down you know what<01:31:02.100> you<01:31:02.219> got<01:31:02.280> to<01:31:02.400> do<01:31:02.460> I<01:31:02.639> don't<01:31:02.699> want<01:31:02.820> to<01:31:02.880> know 01:31:02.930 --> 01:31:02.940 align:start position:0% what you got to do I don't want to know 01:31:02.940 --> 01:31:04.430 align:start position:0% what you got to do I don't want to know what<01:31:03.000> you<01:31:03.120> got<01:31:03.239> to<01:31:03.300> do<01:31:03.360> just<01:31:03.659> keep<01:31:03.960> swimming 01:31:04.430 --> 01:31:04.440 align:start position:0% what you got to do just keep swimming 01:31:04.440 --> 01:31:07.270 align:start position:0% what you got to do just keep swimming just<01:31:04.920> keep<01:31:05.100> swimming<01:31:05.639> just<01:31:06.179> keep<01:31:06.420> swimming 01:31:07.270 --> 01:31:07.280 align:start position:0% just keep swimming just keep swimming 01:31:07.280 --> 01:31:10.310 align:start position:0% just keep swimming just keep swimming swimming<01:31:08.280> what<01:31:08.760> do<01:31:09.000> we<01:31:09.120> do<01:31:09.300> we<01:31:09.540> swim<01:31:09.840> so<01:31:10.199> I 01:31:10.310 --> 01:31:10.320 align:start position:0% swimming what do we do we swim so I 01:31:10.320 --> 01:31:11.870 align:start position:0% swimming what do we do we swim so I decided<01:31:10.739> to<01:31:10.800> add<01:31:11.040> and<01:31:11.280> just<01:31:11.460> keep<01:31:11.639> moving 01:31:11.870 --> 01:31:11.880 align:start position:0% decided to add and just keep moving 01:31:11.880 --> 01:31:14.030 align:start position:0% decided to add and just keep moving forward<01:31:12.060> to<01:31:12.420> a<01:31:12.659> t-shirt<01:31:12.900> recently<01:31:13.440> because<01:31:13.679> it 01:31:14.030 --> 01:31:14.040 align:start position:0% forward to a t-shirt recently because it 01:31:14.040 --> 01:31:16.490 align:start position:0% forward to a t-shirt recently because it really<01:31:14.219> does<01:31:14.460> show<01:31:14.940> the<01:31:15.480> perseverance<01:31:16.139> that 01:31:16.490 --> 01:31:16.500 align:start position:0% really does show the perseverance that 01:31:16.500 --> 01:31:19.070 align:start position:0% really does show the perseverance that you<01:31:16.620> have<01:31:16.739> to<01:31:16.860> have<01:31:17.040> in<01:31:17.760> the<01:31:17.940> field<01:31:18.239> of<01:31:18.540> cyber 01:31:19.070 --> 01:31:19.080 align:start position:0% you have to have in the field of cyber 01:31:19.080 --> 01:31:20.450 align:start position:0% you have to have in the field of cyber security<01:31:19.320> so<01:31:19.800> let's<01:31:19.920> go<01:31:20.040> ahead<01:31:20.159> and<01:31:20.219> take<01:31:20.400> a 01:31:20.450 --> 01:31:20.460 align:start position:0% security so let's go ahead and take a 01:31:20.460 --> 01:31:22.729 align:start position:0% security so let's go ahead and take a look<01:31:20.580> at<01:31:20.699> hacker<01:31:21.000> one<01:31:21.120> and<01:31:21.540> narrow<01:31:22.020> down<01:31:22.199> some 01:31:22.729 --> 01:31:22.739 align:start position:0% look at hacker one and narrow down some 01:31:22.739 --> 01:31:24.470 align:start position:0% look at hacker one and narrow down some potential<01:31:23.219> targets<01:31:23.820> and<01:31:24.060> I'm<01:31:24.179> going<01:31:24.300> to<01:31:24.360> show 01:31:24.470 --> 01:31:24.480 align:start position:0% potential targets and I'm going to show 01:31:24.480 --> 01:31:26.270 align:start position:0% potential targets and I'm going to show you<01:31:24.540> my<01:31:24.840> process<01:31:25.199> for<01:31:25.500> doing<01:31:25.679> this<01:31:25.860> let's<01:31:26.100> go 01:31:26.270 --> 01:31:26.280 align:start position:0% you my process for doing this let's go 01:31:26.280 --> 01:31:27.830 align:start position:0% you my process for doing this let's go ahead<01:31:26.400> and<01:31:26.580> jump<01:31:26.880> into<01:31:27.060> it<01:31:27.239> so<01:31:27.360> here<01:31:27.480> we<01:31:27.600> are<01:31:27.719> on 01:31:27.830 --> 01:31:27.840 align:start position:0% ahead and jump into it so here we are on 01:31:27.840 --> 01:31:30.110 align:start position:0% ahead and jump into it so here we are on hacker<01:31:28.199> one<01:31:28.320> and<01:31:28.620> one<01:31:28.920> of<01:31:29.040> the<01:31:29.159> first<01:31:29.580> things<01:31:29.820> I 01:31:30.110 --> 01:31:30.120 align:start position:0% hacker one and one of the first things I 01:31:30.120 --> 01:31:33.290 align:start position:0% hacker one and one of the first things I like<01:31:30.300> to<01:31:30.480> do<01:31:30.600> is<01:31:30.960> come<01:31:31.440> in<01:31:31.739> to<01:31:32.100> the<01:31:32.400> hackers<01:31:32.820> and 01:31:33.290 --> 01:31:33.300 align:start position:0% like to do is come in to the hackers and 01:31:33.300 --> 01:31:34.790 align:start position:0% like to do is come in to the hackers and then<01:31:33.420> we<01:31:33.600> need<01:31:33.719> to<01:31:33.780> go<01:31:33.900> to<01:31:34.020> the<01:31:34.199> directory<01:31:34.620> so 01:31:34.790 --> 01:31:34.800 align:start position:0% then we need to go to the directory so 01:31:34.800 --> 01:31:36.830 align:start position:0% then we need to go to the directory so that<01:31:34.920> we<01:31:35.159> can<01:31:35.340> start<01:31:35.760> looking<01:31:36.120> for<01:31:36.480> different 01:31:36.830 --> 01:31:36.840 align:start position:0% that we can start looking for different 01:31:36.840 --> 01:31:39.649 align:start position:0% that we can start looking for different programs<01:31:37.500> and<01:31:37.800> now<01:31:37.980> I<01:31:38.340> like<01:31:38.520> to<01:31:38.760> click<01:31:39.239> launch 01:31:39.649 --> 01:31:39.659 align:start position:0% programs and now I like to click launch 01:31:39.659 --> 01:31:42.890 align:start position:0% programs and now I like to click launch date<01:31:39.900> and<01:31:40.320> I<01:31:40.560> like<01:31:40.679> to<01:31:41.040> sort<01:31:41.639> by<01:31:42.060> the<01:31:42.360> date<01:31:42.540> I 01:31:42.890 --> 01:31:42.900 align:start position:0% date and I like to sort by the date I 01:31:42.900 --> 01:31:44.870 align:start position:0% date and I like to sort by the date I want<01:31:42.960> to<01:31:43.080> go<01:31:43.260> from<01:31:43.679> the<01:31:44.100> newest<01:31:44.400> first 01:31:44.870 --> 01:31:44.880 align:start position:0% want to go from the newest first 01:31:44.880 --> 01:31:46.310 align:start position:0% want to go from the newest first accidentally<01:31:45.420> clicked<01:31:45.659> it<01:31:45.719> one<01:31:45.900> too<01:31:46.199> many 01:31:46.310 --> 01:31:46.320 align:start position:0% accidentally clicked it one too many 01:31:46.320 --> 01:31:47.990 align:start position:0% accidentally clicked it one too many times<01:31:46.500> and<01:31:47.040> I<01:31:47.219> actually<01:31:47.340> believe<01:31:47.580> you<01:31:47.699> had<01:31:47.880> to 01:31:47.990 --> 01:31:48.000 align:start position:0% times and I actually believe you had to 01:31:48.000 --> 01:31:50.270 align:start position:0% times and I actually believe you had to be<01:31:48.060> logged<01:31:48.540> out<01:31:48.659> of<01:31:49.080> hacker<01:31:49.500> one<01:31:49.679> to<01:31:49.920> have<01:31:50.040> this 01:31:50.270 --> 01:31:50.280 align:start position:0% be logged out of hacker one to have this 01:31:50.280 --> 01:31:51.830 align:start position:0% be logged out of hacker one to have this feature<01:31:50.639> work<01:31:50.820> so<01:31:51.060> if<01:31:51.179> you're<01:31:51.239> logged<01:31:51.600> in<01:31:51.659> go 01:31:51.830 --> 01:31:51.840 align:start position:0% feature work so if you're logged in go 01:31:51.840 --> 01:31:54.350 align:start position:0% feature work so if you're logged in go ahead<01:31:51.960> and<01:31:52.080> log<01:31:52.320> out<01:31:52.560> and<01:31:53.219> then<01:31:53.340> you<01:31:53.760> can<01:31:53.880> look 01:31:54.350 --> 01:31:54.360 align:start position:0% ahead and log out and then you can look 01:31:54.360 --> 01:31:55.790 align:start position:0% ahead and log out and then you can look through<01:31:54.659> here<01:31:54.900> and<01:31:55.139> then<01:31:55.199> once<01:31:55.440> you<01:31:55.560> have<01:31:55.620> them 01:31:55.790 --> 01:31:55.800 align:start position:0% through here and then once you have them 01:31:55.800 --> 01:31:57.350 align:start position:0% through here and then once you have them all<01:31:56.159> sorted<01:31:56.520> out<01:31:56.639> one<01:31:56.820> of<01:31:56.940> my<01:31:57.000> favorite<01:31:57.120> things 01:31:57.350 --> 01:31:57.360 align:start position:0% all sorted out one of my favorite things 01:31:57.360 --> 01:32:00.110 align:start position:0% all sorted out one of my favorite things to<01:31:57.540> do<01:31:57.659> is<01:31:57.840> open<01:31:58.139> them<01:31:58.380> up<01:31:58.620> and<01:31:59.280> look<01:31:59.580> at<01:31:59.880> the 01:32:00.110 --> 01:32:00.120 align:start position:0% to do is open them up and look at the 01:32:00.120 --> 01:32:02.750 align:start position:0% to do is open them up and look at the scope<01:32:00.360> I<01:32:00.659> like<01:32:00.780> to<01:32:00.960> see<01:32:01.199> how<01:32:01.739> big<01:32:01.980> the<01:32:02.280> scope<01:32:02.520> is 01:32:02.750 --> 01:32:02.760 align:start position:0% scope I like to see how big the scope is 01:32:02.760 --> 01:32:05.149 align:start position:0% scope I like to see how big the scope is and<01:32:03.300> make<01:32:03.480> sure<01:32:03.659> that<01:32:04.020> there<01:32:04.199> is<01:32:04.380> a<01:32:04.860> really 01:32:05.149 --> 01:32:05.159 align:start position:0% and make sure that there is a really 01:32:05.159 --> 01:32:07.490 align:start position:0% and make sure that there is a really large<01:32:05.639> scope<01:32:06.179> because<01:32:06.480> one<01:32:06.719> of<01:32:06.840> my<01:32:07.020> get 01:32:07.490 --> 01:32:07.500 align:start position:0% large scope because one of my get 01:32:07.500 --> 01:32:10.310 align:start position:0% large scope because one of my get personal<01:32:07.739> and<01:32:07.980> biggest<01:32:08.159> struggles<01:32:08.639> is<01:32:09.360> I<01:32:09.900> will 01:32:10.310 --> 01:32:10.320 align:start position:0% personal and biggest struggles is I will 01:32:10.320 --> 01:32:11.930 align:start position:0% personal and biggest struggles is I will open<01:32:10.620> up<01:32:10.800> a<01:32:10.980> program<01:32:11.100> and<01:32:11.400> I'll<01:32:11.520> get<01:32:11.639> started 01:32:11.930 --> 01:32:11.940 align:start position:0% open up a program and I'll get started 01:32:11.940 --> 01:32:14.330 align:start position:0% open up a program and I'll get started and<01:32:12.239> then<01:32:12.420> in<01:32:12.780> 20<01:32:13.199> minutes<01:32:13.380> I<01:32:13.679> find<01:32:13.800> myself<01:32:14.040> out 01:32:14.330 --> 01:32:14.340 align:start position:0% and then in 20 minutes I find myself out 01:32:14.340 --> 01:32:16.910 align:start position:0% and then in 20 minutes I find myself out of<01:32:14.520> scope<01:32:14.760> and<01:32:15.360> this<01:32:15.719> can<01:32:15.900> be<01:32:16.199> a<01:32:16.380> problem<01:32:16.500> so<01:32:16.800> I 01:32:16.910 --> 01:32:16.920 align:start position:0% of scope and this can be a problem so I 01:32:16.920 --> 01:32:18.649 align:start position:0% of scope and this can be a problem so I really<01:32:17.040> like<01:32:17.219> to<01:32:17.400> have<01:32:17.580> large<01:32:17.880> Scopes<01:32:18.300> it<01:32:18.480> also 01:32:18.649 --> 01:32:18.659 align:start position:0% really like to have large Scopes it also 01:32:18.659 --> 01:32:19.970 align:start position:0% really like to have large Scopes it also means<01:32:18.900> you<01:32:19.080> have<01:32:19.199> a<01:32:19.320> lot<01:32:19.440> larger<01:32:19.739> attack 01:32:19.970 --> 01:32:19.980 align:start position:0% means you have a lot larger attack 01:32:19.980 --> 01:32:22.189 align:start position:0% means you have a lot larger attack surface<01:32:20.520> and<01:32:21.120> there's<01:32:21.420> going<01:32:21.600> to<01:32:21.719> be<01:32:21.780> a<01:32:22.080> lot 01:32:22.189 --> 01:32:22.199 align:start position:0% surface and there's going to be a lot 01:32:22.199 --> 01:32:24.590 align:start position:0% surface and there's going to be a lot more<01:32:22.500> diversity<01:32:23.100> in<01:32:23.460> where<01:32:23.699> different<01:32:24.239> bug 01:32:24.590 --> 01:32:24.600 align:start position:0% more diversity in where different bug 01:32:24.600 --> 01:32:26.390 align:start position:0% more diversity in where different bug bounty<01:32:24.960> hunters<01:32:25.260> have<01:32:25.440> been<01:32:25.739> looking<01:32:26.100> and 01:32:26.390 --> 01:32:26.400 align:start position:0% bounty hunters have been looking and 01:32:26.400 --> 01:32:28.010 align:start position:0% bounty hunters have been looking and testing<01:32:26.820> and<01:32:27.179> so<01:32:27.300> you're<01:32:27.420> more<01:32:27.600> likely<01:32:27.900> to 01:32:28.010 --> 01:32:28.020 align:start position:0% testing and so you're more likely to 01:32:28.020 --> 01:32:31.310 align:start position:0% testing and so you're more likely to find<01:32:28.739> a<01:32:29.100> bug<01:32:29.400> so<01:32:29.699> let's<01:32:29.820> go<01:32:30.000> ahead<01:32:30.179> and<01:32:30.960> scroll 01:32:31.310 --> 01:32:31.320 align:start position:0% find a bug so let's go ahead and scroll 01:32:31.320 --> 01:32:33.290 align:start position:0% find a bug so let's go ahead and scroll through<01:32:31.560> some<01:32:31.980> of<01:32:32.100> these<01:32:32.340> and<01:32:32.639> let's<01:32:32.760> look<01:32:33.000> at 01:32:33.290 --> 01:32:33.300 align:start position:0% through some of these and let's look at 01:32:33.300 --> 01:32:36.229 align:start position:0% through some of these and let's look at some<01:32:33.540> of<01:32:33.659> the<01:32:33.960> Scopes<01:32:34.440> maybe<01:32:35.100> we<01:32:35.460> can<01:32:35.639> look<01:32:35.880> at 01:32:36.229 --> 01:32:36.239 align:start position:0% some of the Scopes maybe we can look at 01:32:36.239 --> 01:32:37.729 align:start position:0% some of the Scopes maybe we can look at this<01:32:36.420> link<01:32:36.659> tree<01:32:36.900> I<01:32:37.199> have<01:32:37.380> actually<01:32:37.500> never 01:32:37.729 --> 01:32:37.739 align:start position:0% this link tree I have actually never 01:32:37.739 --> 01:32:39.649 align:start position:0% this link tree I have actually never looked<01:32:38.040> at<01:32:38.100> this<01:32:38.280> but<01:32:38.820> you<01:32:39.000> can<01:32:39.120> scroll<01:32:39.480> down 01:32:39.649 --> 01:32:39.659 align:start position:0% looked at this but you can scroll down 01:32:39.659 --> 01:32:42.050 align:start position:0% looked at this but you can scroll down and<01:32:40.020> look<01:32:40.199> to<01:32:40.380> see<01:32:40.560> how<01:32:40.980> large<01:32:41.159> their<01:32:41.520> scope<01:32:41.820> is 01:32:42.050 --> 01:32:42.060 align:start position:0% and look to see how large their scope is 01:32:42.060 --> 01:32:44.209 align:start position:0% and look to see how large their scope is and<01:32:42.420> it<01:32:42.719> seems<01:32:42.960> like<01:32:43.080> they<01:32:43.440> have<01:32:43.679> a<01:32:43.920> pretty 01:32:44.209 --> 01:32:44.219 align:start position:0% and it seems like they have a pretty 01:32:44.219 --> 01:32:46.189 align:start position:0% and it seems like they have a pretty large<01:32:44.400> scope<01:32:44.699> and<01:32:45.300> then<01:32:45.480> you<01:32:45.659> need<01:32:45.780> to<01:32:45.900> make 01:32:46.189 --> 01:32:46.199 align:start position:0% large scope and then you need to make 01:32:46.199 --> 01:32:48.890 align:start position:0% large scope and then you need to make sure<01:32:46.380> you<01:32:46.860> stay<01:32:47.219> away<01:32:47.460> from<01:32:47.940> these<01:32:48.480> specific 01:32:48.890 --> 01:32:48.900 align:start position:0% sure you stay away from these specific 01:32:48.900 --> 01:32:50.810 align:start position:0% sure you stay away from these specific ones<01:32:49.260> and<01:32:49.500> so<01:32:49.679> make<01:32:49.920> sure<01:32:50.100> when<01:32:50.520> you<01:32:50.699> are 01:32:50.810 --> 01:32:50.820 align:start position:0% ones and so make sure when you are 01:32:50.820 --> 01:32:52.970 align:start position:0% ones and so make sure when you are searching<01:32:51.239> for<01:32:51.540> a<01:32:51.780> Target<01:32:51.900> that<01:32:52.260> it<01:32:52.500> has<01:32:52.739> a 01:32:52.970 --> 01:32:52.980 align:start position:0% searching for a Target that it has a 01:32:52.980 --> 01:32:54.470 align:start position:0% searching for a Target that it has a large<01:32:53.100> scope<01:32:53.400> and<01:32:53.639> one<01:32:53.880> of<01:32:54.000> the<01:32:54.060> second<01:32:54.179> things 01:32:54.470 --> 01:32:54.480 align:start position:0% large scope and one of the second things 01:32:54.480 --> 01:32:56.090 align:start position:0% large scope and one of the second things you<01:32:54.840> should<01:32:55.020> search<01:32:55.199> for<01:32:55.380> is<01:32:55.679> something<01:32:55.860> that 01:32:56.090 --> 01:32:56.100 align:start position:0% you should search for is something that 01:32:56.100 --> 01:32:58.790 align:start position:0% you should search for is something that you're<01:32:56.340> really<01:32:56.820> familiar<01:32:57.420> with<01:32:57.840> so<01:32:58.560> I've 01:32:58.790 --> 01:32:58.800 align:start position:0% you're really familiar with so I've 01:32:58.800 --> 01:33:01.129 align:start position:0% you're really familiar with so I've noticed<01:32:59.219> that<01:32:59.460> there<01:32:59.820> can<01:33:00.000> be<01:33:00.239> a<01:33:00.540> lot<01:33:00.659> of<01:33:00.840> like 01:33:01.129 --> 01:33:01.139 align:start position:0% noticed that there can be a lot of like 01:33:01.139 --> 01:33:04.310 align:start position:0% noticed that there can be a lot of like currency<01:33:01.920> trading<01:33:02.639> programs<01:33:03.540> on<01:33:03.780> here<01:33:03.960> and 01:33:04.310 --> 01:33:04.320 align:start position:0% currency trading programs on here and 01:33:04.320 --> 01:33:05.570 align:start position:0% currency trading programs on here and I'm<01:33:04.500> not<01:33:04.620> familiar<01:33:04.860> with<01:33:05.040> a<01:33:05.219> lot<01:33:05.280> of<01:33:05.400> the 01:33:05.570 --> 01:33:05.580 align:start position:0% I'm not familiar with a lot of the 01:33:05.580 --> 01:33:07.910 align:start position:0% I'm not familiar with a lot of the online<01:33:05.820> currency<01:33:06.360> Trading<01:33:06.960> programs<01:33:07.739> so 01:33:07.910 --> 01:33:07.920 align:start position:0% online currency Trading programs so 01:33:07.920 --> 01:33:09.290 align:start position:0% online currency Trading programs so that's<01:33:08.040> something<01:33:08.219> that<01:33:08.460> I'm<01:33:08.639> going<01:33:08.820> to<01:33:09.000> just 01:33:09.290 --> 01:33:09.300 align:start position:0% that's something that I'm going to just 01:33:09.300 --> 01:33:12.229 align:start position:0% that's something that I'm going to just avoid<01:33:09.659> but<01:33:10.199> maybe<01:33:10.380> you're<01:33:10.739> into<01:33:11.100> shopping<01:33:11.820> and 01:33:12.229 --> 01:33:12.239 align:start position:0% avoid but maybe you're into shopping and 01:33:12.239 --> 01:33:13.970 align:start position:0% avoid but maybe you're into shopping and you're<01:33:12.420> like<01:33:12.600> I<01:33:12.780> want<01:33:12.900> to<01:33:13.020> check<01:33:13.080> out<01:33:13.260> fossil<01:33:13.800> I 01:33:13.970 --> 01:33:13.980 align:start position:0% you're like I want to check out fossil I 01:33:13.980 --> 01:33:15.709 align:start position:0% you're like I want to check out fossil I want<01:33:14.100> to<01:33:14.219> see<01:33:14.400> what<01:33:14.820> kind<01:33:15.000> of<01:33:15.060> scope<01:33:15.239> they<01:33:15.540> have 01:33:15.709 --> 01:33:15.719 align:start position:0% want to see what kind of scope they have 01:33:15.719 --> 01:33:17.030 align:start position:0% want to see what kind of scope they have and<01:33:15.900> you<01:33:16.020> can<01:33:16.139> come<01:33:16.199> in<01:33:16.320> here<01:33:16.500> and<01:33:16.739> read<01:33:16.920> about 01:33:17.030 --> 01:33:17.040 align:start position:0% and you can come in here and read about 01:33:17.040 --> 01:33:19.669 align:start position:0% and you can come in here and read about it<01:33:17.280> maybe<01:33:17.760> you're<01:33:18.239> really<01:33:18.480> into<01:33:18.780> gaming<01:33:19.440> and 01:33:19.669 --> 01:33:19.679 align:start position:0% it maybe you're really into gaming and 01:33:19.679 --> 01:33:21.350 align:start position:0% it maybe you're really into gaming and I'm<01:33:19.800> pretty<01:33:19.980> sure<01:33:20.159> here's<01:33:20.639> GameStop<01:33:20.820> there 01:33:21.350 --> 01:33:21.360 align:start position:0% I'm pretty sure here's GameStop there 01:33:21.360 --> 01:33:24.709 align:start position:0% I'm pretty sure here's GameStop there are<01:33:21.480> quite<01:33:21.659> a<01:33:21.780> few<01:33:21.900> game<01:33:22.800> style<01:33:23.480> programs<01:33:24.480> on 01:33:24.709 --> 01:33:24.719 align:start position:0% are quite a few game style programs on 01:33:24.719 --> 01:33:26.209 align:start position:0% are quite a few game style programs on here<01:33:24.840> and<01:33:25.080> you<01:33:25.199> can<01:33:25.320> go<01:33:25.440> ahead<01:33:25.560> and<01:33:25.920> attack 01:33:26.209 --> 01:33:26.219 align:start position:0% here and you can go ahead and attack 01:33:26.219 --> 01:33:28.070 align:start position:0% here and you can go ahead and attack those<01:33:26.580> I'm<01:33:26.820> pretty<01:33:27.000> sure<01:33:27.120> PlayStation<01:33:27.659> is<01:33:27.960> on 01:33:28.070 --> 01:33:28.080 align:start position:0% those I'm pretty sure PlayStation is on 01:33:28.080 --> 01:33:30.050 align:start position:0% those I'm pretty sure PlayStation is on here<01:33:28.199> GameStop<01:33:28.560> is<01:33:28.980> on<01:33:29.159> here<01:33:29.340> and<01:33:29.760> if<01:33:29.940> you're 01:33:30.050 --> 01:33:30.060 align:start position:0% here GameStop is on here and if you're 01:33:30.060 --> 01:33:31.729 align:start position:0% here GameStop is on here and if you're familiar<01:33:30.420> with<01:33:30.719> those<01:33:30.960> websites<01:33:31.560> already 01:33:31.729 --> 01:33:31.739 align:start position:0% familiar with those websites already 01:33:31.739 --> 01:33:32.810 align:start position:0% familiar with those websites already those<01:33:32.040> are<01:33:32.159> going<01:33:32.280> to<01:33:32.340> be<01:33:32.400> something<01:33:32.580> you're 01:33:32.810 --> 01:33:32.820 align:start position:0% those are going to be something you're 01:33:32.820 --> 01:33:34.490 align:start position:0% those are going to be something you're going<01:33:32.940> to<01:33:33.120> want<01:33:33.179> to<01:33:33.420> attack<01:33:33.780> because<01:33:34.199> you're 01:33:34.490 --> 01:33:34.500 align:start position:0% going to want to attack because you're 01:33:34.500 --> 01:33:35.570 align:start position:0% going to want to attack because you're going<01:33:34.620> to<01:33:34.679> already<01:33:34.800> know<01:33:34.980> how<01:33:35.159> the<01:33:35.280> web<01:33:35.400> app 01:33:35.570 --> 01:33:35.580 align:start position:0% going to already know how the web app 01:33:35.580 --> 01:33:37.189 align:start position:0% going to already know how the web app functions<01:33:36.060> and<01:33:36.420> what<01:33:36.600> should<01:33:36.780> be<01:33:36.900> happening 01:33:37.189 --> 01:33:37.199 align:start position:0% functions and what should be happening 01:33:37.199 --> 01:33:39.050 align:start position:0% functions and what should be happening when<01:33:37.440> you<01:33:37.500> click<01:33:37.679> on<01:33:37.800> different<01:33:37.980> links<01:33:38.460> or<01:33:38.760> log 01:33:39.050 --> 01:33:39.060 align:start position:0% when you click on different links or log 01:33:39.060 --> 01:33:42.290 align:start position:0% when you click on different links or log in<01:33:39.360> and<01:33:39.960> so<01:33:40.199> pick<01:33:40.739> a<01:33:41.100> program<01:33:41.460> that<01:33:42.000> you 01:33:42.290 --> 01:33:42.300 align:start position:0% in and so pick a program that you 01:33:42.300 --> 01:33:44.030 align:start position:0% in and so pick a program that you personally<01:33:42.659> are<01:33:42.960> familiar<01:33:43.320> with<01:33:43.440> and<01:33:43.800> are 01:33:44.030 --> 01:33:44.040 align:start position:0% personally are familiar with and are 01:33:44.040 --> 01:33:46.189 align:start position:0% personally are familiar with and are already<01:33:44.219> interested<01:33:44.880> in<01:33:45.239> and<01:33:45.600> a<01:33:45.780> sub<01:33:45.900> point<01:33:46.020> to 01:33:46.189 --> 01:33:46.199 align:start position:0% already interested in and a sub point to 01:33:46.199 --> 01:33:47.570 align:start position:0% already interested in and a sub point to this<01:33:46.320> is<01:33:46.440> pick<01:33:46.620> a<01:33:46.800> program<01:33:47.040> that<01:33:47.460> you're 01:33:47.570 --> 01:33:47.580 align:start position:0% this is pick a program that you're 01:33:47.580 --> 01:33:49.310 align:start position:0% this is pick a program that you're really<01:33:47.880> interested<01:33:48.300> in<01:33:48.480> because<01:33:48.840> you<01:33:49.199> are 01:33:49.310 --> 01:33:49.320 align:start position:0% really interested in because you are 01:33:49.320 --> 01:33:50.689 align:start position:0% really interested in because you are going<01:33:49.440> to<01:33:49.560> be<01:33:49.620> interested<01:33:49.980> in<01:33:50.219> clicking 01:33:50.689 --> 01:33:50.699 align:start position:0% going to be interested in clicking 01:33:50.699 --> 01:33:51.830 align:start position:0% going to be interested in clicking through<01:33:50.820> the<01:33:51.000> website<01:33:51.300> seeing<01:33:51.719> what's 01:33:51.830 --> 01:33:51.840 align:start position:0% through the website seeing what's 01:33:51.840 --> 01:33:53.689 align:start position:0% through the website seeing what's happening<01:33:52.139> what<01:33:52.440> products<01:33:52.860> there<01:33:52.980> are<01:33:53.159> and 01:33:53.689 --> 01:33:53.699 align:start position:0% happening what products there are and 01:33:53.699 --> 01:33:55.129 align:start position:0% happening what products there are and maybe<01:33:53.880> you'll<01:33:54.120> be<01:33:54.300> interested<01:33:54.600> in<01:33:54.719> looking<01:33:54.960> at 01:33:55.129 --> 01:33:55.139 align:start position:0% maybe you'll be interested in looking at 01:33:55.139 --> 01:33:56.390 align:start position:0% maybe you'll be interested in looking at the<01:33:55.320> products<01:33:55.679> and<01:33:55.800> it's<01:33:55.920> going<01:33:56.100> to<01:33:56.159> help<01:33:56.280> you 01:33:56.390 --> 01:33:56.400 align:start position:0% the products and it's going to help you 01:33:56.400 --> 01:33:57.770 align:start position:0% the products and it's going to help you figure<01:33:56.580> out<01:33:56.699> how<01:33:56.940> the<01:33:57.060> website<01:33:57.360> functions 01:33:57.770 --> 01:33:57.780 align:start position:0% figure out how the website functions 01:33:57.780 --> 01:33:59.090 align:start position:0% figure out how the website functions just<01:33:58.080> because<01:33:58.199> you're<01:33:58.560> going<01:33:58.620> to<01:33:58.739> be<01:33:58.860> a<01:33:58.980> normal 01:33:59.090 --> 01:33:59.100 align:start position:0% just because you're going to be a normal 01:33:59.100 --> 01:34:00.830 align:start position:0% just because you're going to be a normal user<01:33:59.520> and<01:34:00.000> there's<01:34:00.120> going<01:34:00.300> to<01:34:00.360> be<01:34:00.480> things<01:34:00.600> on 01:34:00.830 --> 01:34:00.840 align:start position:0% user and there's going to be things on 01:34:00.840 --> 01:34:02.330 align:start position:0% user and there's going to be things on the<01:34:01.020> website<01:34:01.320> that<01:34:01.440> you<01:34:01.560> want<01:34:01.679> to<01:34:01.739> look<01:34:01.860> at<01:34:02.040> and 01:34:02.330 --> 01:34:02.340 align:start position:0% the website that you want to look at and 01:34:02.340 --> 01:34:03.470 align:start position:0% the website that you want to look at and click<01:34:02.639> through<01:34:02.760> and<01:34:03.000> check<01:34:03.179> out<01:34:03.300> the 01:34:03.470 --> 01:34:03.480 align:start position:0% click through and check out the 01:34:03.480 --> 01:34:04.970 align:start position:0% click through and check out the functionality<01:34:03.960> but<01:34:04.380> you're<01:34:04.560> also<01:34:04.860> really 01:34:04.970 --> 01:34:04.980 align:start position:0% functionality but you're also really 01:34:04.980 --> 01:34:06.470 align:start position:0% functionality but you're also really interested<01:34:05.400> in<01:34:05.580> what<01:34:05.820> they<01:34:06.000> have<01:34:06.179> to<01:34:06.300> sell 01:34:06.470 --> 01:34:06.480 align:start position:0% interested in what they have to sell 01:34:06.480 --> 01:34:07.850 align:start position:0% interested in what they have to sell this<01:34:06.659> is<01:34:06.780> going<01:34:06.840> to<01:34:06.900> to<01:34:07.320> really<01:34:07.440> help<01:34:07.620> in 01:34:07.850 --> 01:34:07.860 align:start position:0% this is going to to really help in 01:34:07.860 --> 01:34:09.770 align:start position:0% this is going to to really help in keeping<01:34:08.280> your<01:34:08.520> interest<01:34:08.699> and<01:34:09.179> so<01:34:09.360> pick<01:34:09.600> a 01:34:09.770 --> 01:34:09.780 align:start position:0% keeping your interest and so pick a 01:34:09.780 --> 01:34:11.330 align:start position:0% keeping your interest and so pick a program<01:34:09.960> that<01:34:10.320> you're<01:34:10.440> familiar<01:34:10.739> with<01:34:10.860> or<01:34:11.219> one 01:34:11.330 --> 01:34:11.340 align:start position:0% program that you're familiar with or one 01:34:11.340 --> 01:34:12.950 align:start position:0% program that you're familiar with or one that<01:34:11.520> offers<01:34:11.820> some<01:34:12.120> kind<01:34:12.239> of<01:34:12.360> service<01:34:12.540> that 01:34:12.950 --> 01:34:12.960 align:start position:0% that offers some kind of service that 01:34:12.960 --> 01:34:14.810 align:start position:0% that offers some kind of service that you're<01:34:13.139> really<01:34:13.500> interested<01:34:13.920> in<01:34:14.040> or<01:34:14.340> products 01:34:14.810 --> 01:34:14.820 align:start position:0% you're really interested in or products 01:34:14.820 --> 01:34:17.330 align:start position:0% you're really interested in or products that<01:34:15.239> they're<01:34:15.420> selling<01:34:15.840> that<01:34:16.139> you<01:34:16.380> would<01:34:16.920> be<01:34:17.100> a 01:34:17.330 --> 01:34:17.340 align:start position:0% that they're selling that you would be a 01:34:17.340 --> 01:34:19.070 align:start position:0% that they're selling that you would be a potential<01:34:17.639> buyer<01:34:18.000> of<01:34:18.179> now<01:34:18.480> the<01:34:18.659> reason<01:34:18.780> I<01:34:18.960> told 01:34:19.070 --> 01:34:19.080 align:start position:0% potential buyer of now the reason I told 01:34:19.080 --> 01:34:21.229 align:start position:0% potential buyer of now the reason I told you<01:34:19.199> to<01:34:19.380> sort<01:34:19.739> the<01:34:19.920> programs<01:34:20.280> by<01:34:20.639> date<01:34:20.940> is 01:34:21.229 --> 01:34:21.239 align:start position:0% you to sort the programs by date is 01:34:21.239 --> 01:34:22.910 align:start position:0% you to sort the programs by date is because<01:34:21.360> the<01:34:21.659> newer<01:34:21.900> the<01:34:22.020> program<01:34:22.260> the<01:34:22.800> less 01:34:22.910 --> 01:34:22.920 align:start position:0% because the newer the program the less 01:34:22.920 --> 01:34:24.649 align:start position:0% because the newer the program the less likely<01:34:23.219> they<01:34:23.460> are<01:34:23.639> going<01:34:23.880> to<01:34:24.060> have<01:34:24.480> already 01:34:24.649 --> 01:34:24.659 align:start position:0% likely they are going to have already 01:34:24.659 --> 01:34:26.149 align:start position:0% likely they are going to have already been<01:34:24.900> tested<01:34:25.320> by<01:34:25.560> a<01:34:25.679> bunch<01:34:25.860> of<01:34:25.980> different 01:34:26.149 --> 01:34:26.159 align:start position:0% been tested by a bunch of different 01:34:26.159 --> 01:34:28.070 align:start position:0% been tested by a bunch of different penetration<01:34:26.699> testers<01:34:27.179> or<01:34:27.420> bug<01:34:27.659> brownie 01:34:28.070 --> 01:34:28.080 align:start position:0% penetration testers or bug brownie 01:34:28.080 --> 01:34:29.330 align:start position:0% penetration testers or bug brownie hunters<01:34:28.380> and<01:34:28.620> this<01:34:28.739> is<01:34:28.860> really<01:34:28.980> going<01:34:29.100> to<01:34:29.159> help 01:34:29.330 --> 01:34:29.340 align:start position:0% hunters and this is really going to help 01:34:29.340 --> 01:34:32.030 align:start position:0% hunters and this is really going to help you<01:34:29.460> land<01:34:29.940> a<01:34:30.300> vulnerability<01:34:30.960> before<01:34:31.560> anyone 01:34:32.030 --> 01:34:32.040 align:start position:0% you land a vulnerability before anyone 01:34:32.040 --> 01:34:33.709 align:start position:0% you land a vulnerability before anyone else<01:34:32.219> because<01:34:32.460> the<01:34:32.820> web<01:34:33.000> application<01:34:33.420> just 01:34:33.709 --> 01:34:33.719 align:start position:0% else because the web application just 01:34:33.719 --> 01:34:36.290 align:start position:0% else because the web application just hasn't<01:34:34.020> been<01:34:34.199> picked<01:34:34.620> over<01:34:34.679> as<01:34:35.520> much<01:34:35.639> as<01:34:35.880> the 01:34:36.290 --> 01:34:36.300 align:start position:0% hasn't been picked over as much as the 01:34:36.300 --> 01:34:39.169 align:start position:0% hasn't been picked over as much as the older<01:34:36.600> programs<01:34:37.260> and<01:34:37.739> a<01:34:38.100> another<01:34:38.340> tip<01:34:38.820> to<01:34:38.940> this 01:34:39.169 --> 01:34:39.179 align:start position:0% older programs and a another tip to this 01:34:39.179 --> 01:34:40.910 align:start position:0% older programs and a another tip to this and<01:34:39.480> is<01:34:39.659> really<01:34:39.900> popular<01:34:40.139> and<01:34:40.620> probably 01:34:40.910 --> 01:34:40.920 align:start position:0% and is really popular and probably 01:34:40.920 --> 01:34:43.550 align:start position:0% and is really popular and probably really<01:34:41.219> common<01:34:41.460> knowledge<01:34:41.880> is<01:34:42.420> to<01:34:42.840> choose<01:34:43.260> a 01:34:43.550 --> 01:34:43.560 align:start position:0% really common knowledge is to choose a 01:34:43.560 --> 01:34:45.649 align:start position:0% really common knowledge is to choose a program<01:34:43.860> that<01:34:44.340> is<01:34:44.520> unpaid<01:34:45.120> so<01:34:45.360> you<01:34:45.480> can<01:34:45.540> come 01:34:45.649 --> 01:34:45.659 align:start position:0% program that is unpaid so you can come 01:34:45.659 --> 01:34:48.290 align:start position:0% program that is unpaid so you can come down<01:34:45.840> to<01:34:46.080> one<01:34:46.260> of<01:34:46.380> these<01:34:46.560> unpaid<01:34:46.980> programs<01:34:47.580> and 01:34:48.290 --> 01:34:48.300 align:start position:0% down to one of these unpaid programs and 01:34:48.300 --> 01:34:50.270 align:start position:0% down to one of these unpaid programs and hack<01:34:48.600> on<01:34:48.900> one<01:34:49.139> of<01:34:49.260> those<01:34:49.380> because<01:34:49.800> the<01:34:50.159> top 01:34:50.270 --> 01:34:50.280 align:start position:0% hack on one of those because the top 01:34:50.280 --> 01:34:51.770 align:start position:0% hack on one of those because the top hackers<01:34:50.820> are<01:34:51.000> going<01:34:51.120> to<01:34:51.120> be<01:34:51.239> going<01:34:51.360> after<01:34:51.540> the 01:34:51.770 --> 01:34:51.780 align:start position:0% hackers are going to be going after the 01:34:51.780 --> 01:34:53.510 align:start position:0% hackers are going to be going after the programs<01:34:52.199> that<01:34:52.380> offer<01:34:52.739> rewards<01:34:53.280> and 01:34:53.510 --> 01:34:53.520 align:start position:0% programs that offer rewards and 01:34:53.520 --> 01:34:54.890 align:start position:0% programs that offer rewards and financial<01:34:53.880> gain<01:34:54.239> because<01:34:54.480> they're<01:34:54.719> doing 01:34:54.890 --> 01:34:54.900 align:start position:0% financial gain because they're doing 01:34:54.900 --> 01:34:57.050 align:start position:0% financial gain because they're doing this<01:34:55.139> for<01:34:55.380> a<01:34:55.620> living<01:34:55.860> and<01:34:56.580> if<01:34:56.760> you're<01:34:56.880> just 01:34:57.050 --> 01:34:57.060 align:start position:0% this for a living and if you're just 01:34:57.060 --> 01:34:58.910 align:start position:0% this for a living and if you're just trying<01:34:57.179> to<01:34:57.300> get<01:34:57.480> that<01:34:57.719> first<01:34:57.960> bug<01:34:58.260> then<01:34:58.620> you 01:34:58.910 --> 01:34:58.920 align:start position:0% trying to get that first bug then you 01:34:58.920 --> 01:35:01.310 align:start position:0% trying to get that first bug then you can<01:34:59.040> go<01:34:59.219> for<01:34:59.520> the<01:34:59.820> unpaid<01:35:00.179> programs<01:35:00.719> and<01:35:01.199> then 01:35:01.310 --> 01:35:01.320 align:start position:0% can go for the unpaid programs and then 01:35:01.320 --> 01:35:04.370 align:start position:0% can go for the unpaid programs and then also<01:35:01.620> the<01:35:01.920> newest<01:35:02.400> unpaid<01:35:02.880> program<01:35:03.360> and<01:35:04.080> the 01:35:04.370 --> 01:35:04.380 align:start position:0% also the newest unpaid program and the 01:35:04.380 --> 01:35:06.590 align:start position:0% also the newest unpaid program and the last<01:35:04.620> tip<01:35:05.040> is<01:35:05.219> kind<01:35:05.400> of<01:35:05.460> an<01:35:05.639> ocent<01:35:05.940> tip<01:35:06.300> and<01:35:06.480> I 01:35:06.590 --> 01:35:06.600 align:start position:0% last tip is kind of an ocent tip and I 01:35:06.600 --> 01:35:07.729 align:start position:0% last tip is kind of an ocent tip and I think<01:35:06.719> this<01:35:06.780> is<01:35:06.840> is<01:35:07.199> really<01:35:07.380> going<01:35:07.560> to<01:35:07.679> help 01:35:07.729 --> 01:35:07.739 align:start position:0% think this is is really going to help 01:35:07.739 --> 01:35:11.149 align:start position:0% think this is is really going to help you<01:35:07.920> in<01:35:08.460> your<01:35:09.060> ability<01:35:09.420> to<01:35:09.840> find<01:35:10.199> bugs<01:35:10.739> based 01:35:11.149 --> 01:35:11.159 align:start position:0% you in your ability to find bugs based 01:35:11.159 --> 01:35:13.669 align:start position:0% you in your ability to find bugs based on<01:35:11.219> what<01:35:11.580> the<01:35:11.699> developers<01:35:12.179> are<01:35:12.420> posting<01:35:12.780> so<01:35:13.139> go 01:35:13.669 --> 01:35:13.679 align:start position:0% on what the developers are posting so go 01:35:13.679 --> 01:35:15.830 align:start position:0% on what the developers are posting so go on<01:35:13.920> to<01:35:14.100> all<01:35:14.340> the<01:35:14.520> social<01:35:14.699> medias<01:35:15.120> and<01:35:15.540> follow 01:35:15.830 --> 01:35:15.840 align:start position:0% on to all the social medias and follow 01:35:15.840 --> 01:35:17.870 align:start position:0% on to all the social medias and follow the<01:35:16.199> developers<01:35:16.679> that<01:35:16.860> work<01:35:17.100> for<01:35:17.340> a<01:35:17.639> specific 01:35:17.870 --> 01:35:17.880 align:start position:0% the developers that work for a specific 01:35:17.880 --> 01:35:20.149 align:start position:0% the developers that work for a specific company<01:35:18.179> so<01:35:18.840> if<01:35:19.080> I<01:35:19.260> was<01:35:19.380> going<01:35:19.560> to<01:35:19.679> come<01:35:19.980> over 01:35:20.149 --> 01:35:20.159 align:start position:0% company so if I was going to come over 01:35:20.159 --> 01:35:23.030 align:start position:0% company so if I was going to come over here<01:35:20.340> to<01:35:20.659> mongodb<01:35:21.659> I'd<01:35:22.260> want<01:35:22.440> to<01:35:22.560> find<01:35:22.739> the 01:35:23.030 --> 01:35:23.040 align:start position:0% here to mongodb I'd want to find the 01:35:23.040 --> 01:35:25.310 align:start position:0% here to mongodb I'd want to find the developers<01:35:23.520> that<01:35:23.760> work<01:35:23.940> for<01:35:24.120> mongodb<01:35:24.960> on 01:35:25.310 --> 01:35:25.320 align:start position:0% developers that work for mongodb on 01:35:25.320 --> 01:35:27.950 align:start position:0% developers that work for mongodb on Twitter<01:35:25.560> find<01:35:26.219> their<01:35:26.520> GitHub<01:35:26.940> Pages<01:35:27.239> follow 01:35:27.950 --> 01:35:27.960 align:start position:0% Twitter find their GitHub Pages follow 01:35:27.960 --> 01:35:29.810 align:start position:0% Twitter find their GitHub Pages follow them<01:35:28.260> on<01:35:28.739> any<01:35:28.920> social<01:35:29.159> media<01:35:29.460> that<01:35:29.639> I<01:35:29.760> can 01:35:29.810 --> 01:35:29.820 align:start position:0% them on any social media that I can 01:35:29.820 --> 01:35:31.850 align:start position:0% them on any social media that I can because<01:35:30.060> developers<01:35:30.659> will<01:35:30.840> often<01:35:31.199> brag<01:35:31.679> about 01:35:31.850 --> 01:35:31.860 align:start position:0% because developers will often brag about 01:35:31.860 --> 01:35:33.050 align:start position:0% because developers will often brag about the<01:35:32.040> different<01:35:32.219> software<01:35:32.699> that<01:35:32.880> they're 01:35:33.050 --> 01:35:33.060 align:start position:0% the different software that they're 01:35:33.060 --> 01:35:34.370 align:start position:0% the different software that they're using<01:35:33.360> and<01:35:33.600> they're<01:35:33.719> implementing<01:35:34.199> into 01:35:34.370 --> 01:35:34.380 align:start position:0% using and they're implementing into 01:35:34.380 --> 01:35:36.530 align:start position:0% using and they're implementing into different<01:35:34.860> projects<01:35:35.400> and<01:35:35.940> then<01:35:36.120> lastly 01:35:36.530 --> 01:35:36.540 align:start position:0% different projects and then lastly 01:35:36.540 --> 01:35:37.970 align:start position:0% different projects and then lastly they're<01:35:36.719> going<01:35:36.900> to<01:35:36.960> be<01:35:37.020> pushing<01:35:37.440> their<01:35:37.739> new 01:35:37.970 --> 01:35:37.980 align:start position:0% they're going to be pushing their new 01:35:37.980 --> 01:35:39.950 align:start position:0% they're going to be pushing their new code<01:35:38.159> to<01:35:38.580> GitHub<01:35:39.060> and<01:35:39.300> if<01:35:39.480> you<01:35:39.540> are<01:35:39.659> following 01:35:39.950 --> 01:35:39.960 align:start position:0% code to GitHub and if you are following 01:35:39.960 --> 01:35:42.050 align:start position:0% code to GitHub and if you are following them<01:35:40.080> on<01:35:40.320> GitHub<01:35:40.739> you<01:35:41.340> can<01:35:41.400> go<01:35:41.520> and<01:35:41.699> check<01:35:41.880> out 01:35:42.050 --> 01:35:42.060 align:start position:0% them on GitHub you can go and check out 01:35:42.060 --> 01:35:43.669 align:start position:0% them on GitHub you can go and check out the<01:35:42.239> code<01:35:42.360> that<01:35:42.600> they<01:35:42.840> have<01:35:43.020> published<01:35:43.500> before 01:35:43.669 --> 01:35:43.679 align:start position:0% the code that they have published before 01:35:43.679 --> 01:35:46.550 align:start position:0% the code that they have published before anyone<01:35:44.159> else<01:35:44.340> and<01:35:45.060> see<01:35:45.480> if<01:35:45.780> you<01:35:46.080> can<01:35:46.139> find<01:35:46.320> any 01:35:46.550 --> 01:35:46.560 align:start position:0% anyone else and see if you can find any 01:35:46.560 --> 01:35:48.110 align:start position:0% anyone else and see if you can find any vulnerabilities<01:35:47.100> within<01:35:47.580> there<01:35:47.760> or<01:35:47.940> maybe 01:35:48.110 --> 01:35:48.120 align:start position:0% vulnerabilities within there or maybe 01:35:48.120 --> 01:35:49.790 align:start position:0% vulnerabilities within there or maybe they<01:35:48.420> have<01:35:48.600> pushed<01:35:49.139> some<01:35:49.320> sensitive 01:35:49.790 --> 01:35:49.800 align:start position:0% they have pushed some sensitive 01:35:49.800 --> 01:35:51.350 align:start position:0% they have pushed some sensitive information<01:35:49.980> to<01:35:50.400> GitHub<01:35:50.760> that<01:35:51.239> they 01:35:51.350 --> 01:35:51.360 align:start position:0% information to GitHub that they 01:35:51.360 --> 01:35:52.850 align:start position:0% information to GitHub that they otherwise<01:35:51.719> shouldn't<01:35:52.139> have<01:35:52.260> and<01:35:52.679> so 01:35:52.850 --> 01:35:52.860 align:start position:0% otherwise shouldn't have and so 01:35:52.860 --> 01:35:54.290 align:start position:0% otherwise shouldn't have and so following<01:35:53.280> the<01:35:53.400> developers<01:35:53.760> is<01:35:54.000> going<01:35:54.120> to<01:35:54.239> be 01:35:54.290 --> 01:35:54.300 align:start position:0% following the developers is going to be 01:35:54.300 --> 01:35:56.870 align:start position:0% following the developers is going to be really<01:35:54.540> helpful<01:35:54.960> and<01:35:55.800> and<01:35:56.219> one<01:35:56.520> last<01:35:56.699> thing 01:35:56.870 --> 01:35:56.880 align:start position:0% really helpful and and one last thing 01:35:56.880 --> 01:35:58.490 align:start position:0% really helpful and and one last thing the<01:35:57.060> developers<01:35:57.480> will<01:35:57.659> often<01:35:57.900> do<01:35:58.020> is<01:35:58.199> when 01:35:58.490 --> 01:35:58.500 align:start position:0% the developers will often do is when 01:35:58.500 --> 01:36:01.010 align:start position:0% the developers will often do is when they<01:35:58.739> launch<01:35:59.100> a<01:35:59.460> new<01:35:59.580> subdomain<01:36:00.179> or<01:36:00.540> a<01:36:00.840> new 01:36:01.010 --> 01:36:01.020 align:start position:0% they launch a new subdomain or a new 01:36:01.020 --> 01:36:03.050 align:start position:0% they launch a new subdomain or a new area<01:36:01.560> of<01:36:01.860> the<01:36:01.980> web<01:36:02.159> application<01:36:02.580> that<01:36:02.880> wasn't 01:36:03.050 --> 01:36:03.060 align:start position:0% area of the web application that wasn't 01:36:03.060 --> 01:36:05.030 align:start position:0% area of the web application that wasn't previously<01:36:03.600> launched<01:36:03.960> they'll<01:36:04.560> often<01:36:04.800> post 01:36:05.030 --> 01:36:05.040 align:start position:0% previously launched they'll often post 01:36:05.040 --> 01:36:06.590 align:start position:0% previously launched they'll often post about<01:36:05.280> it<01:36:05.520> and<01:36:05.820> they'll<01:36:06.179> tell<01:36:06.300> you<01:36:06.360> what<01:36:06.540> is 01:36:06.590 --> 01:36:06.600 align:start position:0% about it and they'll tell you what is 01:36:06.600 --> 01:36:08.689 align:start position:0% about it and they'll tell you what is going<01:36:06.780> on<01:36:07.199> on<01:36:07.500> that<01:36:07.620> specific<01:36:07.860> page<01:36:08.219> and 01:36:08.689 --> 01:36:08.699 align:start position:0% going on on that specific page and 01:36:08.699 --> 01:36:10.310 align:start position:0% going on on that specific page and following<01:36:09.060> the<01:36:09.239> developers<01:36:09.600> is<01:36:09.840> one<01:36:10.080> of<01:36:10.199> my 01:36:10.310 --> 01:36:10.320 align:start position:0% following the developers is one of my 01:36:10.320 --> 01:36:12.530 align:start position:0% following the developers is one of my last<01:36:10.500> tips<01:36:10.860> in<01:36:11.159> trying<01:36:11.580> to<01:36:11.820> choose<01:36:12.179> a<01:36:12.420> program 01:36:12.530 --> 01:36:12.540 align:start position:0% last tips in trying to choose a program 01:36:12.540 --> 01:36:15.050 align:start position:0% last tips in trying to choose a program if<01:36:13.320> there<01:36:13.500> are<01:36:13.739> a<01:36:13.920> lot<01:36:14.100> of<01:36:14.280> developers<01:36:14.880> that 01:36:15.050 --> 01:36:15.060 align:start position:0% if there are a lot of developers that 01:36:15.060 --> 01:36:16.910 align:start position:0% if there are a lot of developers that you<01:36:15.179> have<01:36:15.300> the<01:36:15.420> opportunity<01:36:15.840> to<01:36:16.199> follow<01:36:16.500> on<01:36:16.800> a 01:36:16.910 --> 01:36:16.920 align:start position:0% you have the opportunity to follow on a 01:36:16.920 --> 01:36:19.010 align:start position:0% you have the opportunity to follow on a specific<01:36:17.159> program<01:36:17.460> this<01:36:18.179> is<01:36:18.360> going<01:36:18.480> to<01:36:18.659> help 01:36:19.010 --> 01:36:19.020 align:start position:0% specific program this is going to help 01:36:19.020 --> 01:36:21.110 align:start position:0% specific program this is going to help you<01:36:19.139> be<01:36:19.500> one<01:36:19.679> of<01:36:19.800> the<01:36:19.860> first<01:36:19.980> ones<01:36:20.280> to<01:36:20.639> find<01:36:20.820> new 01:36:21.110 --> 01:36:21.120 align:start position:0% you be one of the first ones to find new 01:36:21.120 --> 01:36:23.510 align:start position:0% you be one of the first ones to find new pages<01:36:21.480> as<01:36:22.020> well<01:36:22.199> as<01:36:22.500> code<01:36:22.920> that<01:36:23.159> is<01:36:23.340> being 01:36:23.510 --> 01:36:23.520 align:start position:0% pages as well as code that is being 01:36:23.520 --> 01:36:27.620 align:start position:0% pages as well as code that is being pushed<01:36:23.820> to<01:36:24.179> GitHub<01:36:24.719> thanks<01:36:25.199> for<01:36:25.320> watching