WEBVTT

00:00:00.000 --> 00:00:10.170 align:middle line:90%


00:00:10.170 --> 00:00:11.400 align:middle line:90%
Google Dorks.

00:00:11.400 --> 00:00:13.260 align:middle line:84%
In this video, we're
going to be taking

00:00:13.260 --> 00:00:16.410 align:middle line:84%
a look at the process of
utilizing Google Dorks

00:00:16.410 --> 00:00:21.390 align:middle line:84%
or Google Hacking as it's known
as by hackers and penetration

00:00:21.390 --> 00:00:24.930 align:middle line:84%
testers to essentially
identify information

00:00:24.930 --> 00:00:26.370 align:middle line:90%
pertinent to a target.

00:00:26.370 --> 00:00:28.680 align:middle line:84%
And in this case, we're going
to be primarily focusing

00:00:28.680 --> 00:00:32.549 align:middle line:90%
on domains as our targets.

00:00:32.549 --> 00:00:34.830 align:middle line:84%
So we're essentially going
to be taking a look at how

00:00:34.830 --> 00:00:38.490 align:middle line:84%
to utilize search filters,
Google search filters to find

00:00:38.490 --> 00:00:40.500 align:middle line:90%
exactly what we're looking for.

00:00:40.500 --> 00:00:45.240 align:middle line:84%
This will include specific
subdomains, specific files

00:00:45.240 --> 00:00:48.060 align:middle line:84%
associated with a
target like maybe we

00:00:48.060 --> 00:00:52.470 align:middle line:84%
wanted to find PDF
files that are publicly

00:00:52.470 --> 00:00:55.452 align:middle line:84%
available for a particular
domain, et cetera, et cetera.

00:00:55.452 --> 00:00:56.160 align:middle line:90%
You get the idea.

00:00:56.160 --> 00:00:58.810 align:middle line:84%
You'll actually see what this
looks like when we get started.

00:00:58.810 --> 00:01:02.040 align:middle line:84%
So again, I'm going to be
utilizing my Kali Linux VM.

00:01:02.040 --> 00:01:05.430 align:middle line:84%
And, of course, you can follow
along if you want to as well.

00:01:05.430 --> 00:01:10.290 align:middle line:84%
Just remember, be very
careful with what you actually

00:01:10.290 --> 00:01:11.130 align:middle line:90%
engage with.

00:01:11.130 --> 00:01:15.180 align:middle line:84%
Because as you'll see, there
is quite a lot of content

00:01:15.180 --> 00:01:17.970 align:middle line:84%
you can find online that
is unsecured and could

00:01:17.970 --> 00:01:22.600 align:middle line:84%
be potentially useful
as a penetration tester.

00:01:22.600 --> 00:01:26.150 align:middle line:90%
So let me just switch over.

00:01:26.150 --> 00:01:26.870 align:middle line:90%
All right.

00:01:26.870 --> 00:01:31.795 align:middle line:84%
So I am back on my Kali Linux
system, and we can get started.

00:01:31.795 --> 00:01:33.920 align:middle line:84%
So I'm just going to open
up Google, because that's

00:01:33.920 --> 00:01:35.100 align:middle line:90%
what we are dealing with.

00:01:35.100 --> 00:01:37.550 align:middle line:84%
And then we will
actually walk through it.

00:01:37.550 --> 00:01:39.420 align:middle line:90%
So there we are, google.com.

00:01:39.420 --> 00:01:43.280 align:middle line:84%
So let's say our
target is ine.com.

00:01:43.280 --> 00:01:46.370 align:middle line:84%
So a standard person
who is unenlightened

00:01:46.370 --> 00:01:48.770 align:middle line:84%
might just type
in ine.com, right?

00:01:48.770 --> 00:01:49.830 align:middle line:90%
Fairly simple.

00:01:49.830 --> 00:01:51.590 align:middle line:90%
So we type in ine.com.

00:01:51.590 --> 00:01:55.170 align:middle line:84%
You can see we have ine.com
here, their LinkedIn page,

00:01:55.170 --> 00:01:56.480 align:middle line:90%
Twitter.

00:01:56.480 --> 00:01:59.180 align:middle line:84%
That's looking OK,
but this is really not

00:01:59.180 --> 00:02:03.260 align:middle line:84%
giving me information
that might be useful to me

00:02:03.260 --> 00:02:05.370 align:middle line:84%
with regards to this
particular domain.

00:02:05.370 --> 00:02:08.750 align:middle line:84%
So let's say I wanted
to limit all results

00:02:08.750 --> 00:02:10.610 align:middle line:90%
to this particular domain.

00:02:10.610 --> 00:02:13.640 align:middle line:84%
To do that, I can utilize
the site operator.

00:02:13.640 --> 00:02:15.900 align:middle line:84%
And I'm just going
to zoom in here.

00:02:15.900 --> 00:02:19.760 align:middle line:90%
So this site:ine.com.

00:02:19.760 --> 00:02:21.150 align:middle line:84%
Now, you'll see
what will happen.

00:02:21.150 --> 00:02:29.180 align:middle line:84%
So as you can see, it will now
limit all results to specific--

00:02:29.180 --> 00:02:32.060 align:middle line:84%
it'll limit all the results
to the domain ine.com,

00:02:32.060 --> 00:02:33.230 align:middle line:90%
but not just that.

00:02:33.230 --> 00:02:37.000 align:middle line:84%
It'll also show you subdomains
for this particular domain

00:02:37.000 --> 00:02:37.500 align:middle line:90%
here.

00:02:37.500 --> 00:02:39.530 align:middle line:84%
So you can see we
have my.ine.com.

00:02:39.530 --> 00:02:41.780 align:middle line:90%
We have ine.com here.

00:02:41.780 --> 00:02:43.880 align:middle line:84%
These are all the
pages or categories

00:02:43.880 --> 00:02:45.380 align:middle line:90%
for the ine.com website.

00:02:45.380 --> 00:02:47.220 align:middle line:84%
So you can see we
have blog, careers.

00:02:47.220 --> 00:02:51.620 align:middle line:84%
So we are already starting
to actually identify

00:02:51.620 --> 00:02:53.690 align:middle line:84%
potentially interesting
pages and not

00:02:53.690 --> 00:02:56.120 align:middle line:84%
just that, but potentially
interesting subdomains

00:02:56.120 --> 00:02:59.390 align:middle line:84%
like, for example, they
have courses.ine.com,

00:02:59.390 --> 00:03:03.450 align:middle line:84%
they have community.ine.com,
so on, and so forth.

00:03:03.450 --> 00:03:07.220 align:middle line:84%
But this is still very wide
with regards to the scope.

00:03:07.220 --> 00:03:09.530 align:middle line:84%
We can pretty much go
through all of these pages

00:03:09.530 --> 00:03:12.800 align:middle line:84%
and identify subdomains
that might be

00:03:12.800 --> 00:03:14.550 align:middle line:90%
interesting like this one here.

00:03:14.550 --> 00:03:17.360 align:middle line:84%
Although, I'm not telling
you to do that, but let's

00:03:17.360 --> 00:03:22.610 align:middle line:84%
say we wanted to look
for specific results

00:03:22.610 --> 00:03:24.590 align:middle line:84%
and we want to
limit it to ine.com.

00:03:24.590 --> 00:03:28.520 align:middle line:84%
But let's say within
the website title

00:03:28.520 --> 00:03:30.560 align:middle line:84%
or within the website
URL, let's say

00:03:30.560 --> 00:03:32.150 align:middle line:84%
we were looking
for an admin panel.

00:03:32.150 --> 00:03:33.860 align:middle line:90%
Well, we could say inurl.

00:03:33.860 --> 00:03:36.500 align:middle line:84%
So that's the next
search filter.

00:03:36.500 --> 00:03:38.930 align:middle line:90%
We can say admin.

00:03:38.930 --> 00:03:40.700 align:middle line:84%
Will this show us
an admin panel?

00:03:40.700 --> 00:03:44.700 align:middle line:84%
Well, it shows us a Microsoft
365 Teams Admin page,

00:03:44.700 --> 00:03:46.610 align:middle line:90%
which looks like a course.

00:03:46.610 --> 00:03:48.050 align:middle line:90%
Nothing to do with admin.

00:03:48.050 --> 00:03:50.390 align:middle line:84%
Let's see if we can
find anything there.

00:03:50.390 --> 00:03:53.270 align:middle line:90%
We have another page here.

00:03:53.270 --> 00:03:55.890 align:middle line:84%
But yeah, we pretty much
don't have anything there.

00:03:55.890 --> 00:03:58.440 align:middle line:90%
So that's a bummer.

00:03:58.440 --> 00:04:00.380 align:middle line:90%
So we can see we have the forum.

00:04:00.380 --> 00:04:02.480 align:middle line:84%
By the way, we can also
change this to forum.

00:04:02.480 --> 00:04:04.580 align:middle line:84%
If we are looking
for an INE forum,

00:04:04.580 --> 00:04:07.500 align:middle line:84%
we can just type
inurl forum and then

00:04:07.500 --> 00:04:13.580 align:middle line:84%
we go, we get links pertinent
to the actual search,

00:04:13.580 --> 00:04:15.210 align:middle line:84%
the search queries
we have provided.

00:04:15.210 --> 00:04:18.500 align:middle line:84%
So you can see that the
forum is community.ine.com.

00:04:18.500 --> 00:04:22.220 align:middle line:84%
So we've been able to
identify that conclusively.

00:04:22.220 --> 00:04:24.522 align:middle line:84%
Now, let's say we were
looking for things that

00:04:24.522 --> 00:04:25.730 align:middle line:90%
are a little bit interesting.

00:04:25.730 --> 00:04:29.540 align:middle line:84%
What if we wanted to enumerate
subdomains via Google?

00:04:29.540 --> 00:04:30.840 align:middle line:90%
Well, we could do that.

00:04:30.840 --> 00:04:34.520 align:middle line:84%
And the way we can do
that is by saying site

00:04:34.520 --> 00:04:38.690 align:middle line:84%
and we then use the wild
card symbol or the asterisk.

00:04:38.690 --> 00:04:42.680 align:middle line:90%
And we say site:*.ine.com.

00:04:42.680 --> 00:04:47.240 align:middle line:84%
This will not show
ine.com, but it'll

00:04:47.240 --> 00:04:49.610 align:middle line:90%
show subdomains for ine.com.

00:04:49.610 --> 00:04:50.660 align:middle line:90%
So I'll hit Enter.

00:04:50.660 --> 00:04:53.940 align:middle line:84%
And as you can see now,
we're getting somewhere.

00:04:53.940 --> 00:04:57.230 align:middle line:84%
So we have my.ine.com,
courses.ine.com.

00:04:57.230 --> 00:05:00.320 align:middle line:84%
So this is essentially
what sublister was doing.

00:05:00.320 --> 00:05:04.580 align:middle line:84%
It was essentially utilizing
docs for all the search engines

00:05:04.580 --> 00:05:06.800 align:middle line:84%
to limit the results
to subdomains.

00:05:06.800 --> 00:05:09.110 align:middle line:84%
And these are, of
course, subdomains that

00:05:09.110 --> 00:05:10.760 align:middle line:90%
have been indexed by Google.

00:05:10.760 --> 00:05:12.420 align:middle line:84%
Now, you may be
thinking to yourself,

00:05:12.420 --> 00:05:15.470 align:middle line:84%
well aren't these the
subdomains that INE has

00:05:15.470 --> 00:05:17.840 align:middle line:90%
exposed by their own choice?

00:05:17.840 --> 00:05:19.280 align:middle line:90%
Well, that's true.

00:05:19.280 --> 00:05:20.850 align:middle line:90%
That is the case.

00:05:20.850 --> 00:05:24.290 align:middle line:84%
But in some cases, companies
can become very sloppy,

00:05:24.290 --> 00:05:27.020 align:middle line:84%
and they may expose a
subdomain to the internet

00:05:27.020 --> 00:05:29.600 align:middle line:84%
that they probably
don't want to expose.

00:05:29.600 --> 00:05:31.460 align:middle line:84%
And in many cases,
some companies

00:05:31.460 --> 00:05:33.440 align:middle line:84%
don't even know that
these subdomains

00:05:33.440 --> 00:05:35.750 align:middle line:90%
are accessible via Google.

00:05:35.750 --> 00:05:37.250 align:middle line:84%
So let's take a
look, and let's see.

00:05:37.250 --> 00:05:41.480 align:middle line:84%
Oh, looks like we have the
same remote desktop one there.

00:05:41.480 --> 00:05:45.000 align:middle line:84%
Let's take a look at
some of the other ones.

00:05:45.000 --> 00:05:45.500 align:middle line:90%
OK.

00:05:45.500 --> 00:05:47.720 align:middle line:90%
We have shop.inecourses.

00:05:47.720 --> 00:05:50.390 align:middle line:84%
We've already seen
that, but we still

00:05:50.390 --> 00:05:52.640 align:middle line:84%
aren't getting
anything interesting.

00:05:52.640 --> 00:05:55.130 align:middle line:90%
Nothing interesting so far.

00:05:55.130 --> 00:05:58.280 align:middle line:84%
So let's try and make
this a little bit--

00:05:58.280 --> 00:06:01.440 align:middle line:84%
let's try and make our search
a little bit more refined.

00:06:01.440 --> 00:06:05.630 align:middle line:84%
So I can say inurl, we
can say maybe admin.

00:06:05.630 --> 00:06:08.660 align:middle line:84%
Let's say we're looking
for a subdomain that

00:06:08.660 --> 00:06:11.120 align:middle line:90%
has admin in its URL.

00:06:11.120 --> 00:06:13.860 align:middle line:84%
In this case, that might
not be very useful.

00:06:13.860 --> 00:06:18.320 align:middle line:84%
So we can use the entitle
operator or filter

00:06:18.320 --> 00:06:21.470 align:middle line:84%
that will essentially limit
all the results to subdomains

00:06:21.470 --> 00:06:24.810 align:middle line:84%
with admin within the
actual site title.

00:06:24.810 --> 00:06:26.690 align:middle line:90%
So I'll hit Enter.

00:06:26.690 --> 00:06:31.250 align:middle line:84%
And we have a sales admin, which
looks like the subdomain is

00:06:31.250 --> 00:06:33.260 align:middle line:90%
stgacp.ine.

00:06:33.260 --> 00:06:35.030 align:middle line:90%
This looks like a CRM.

00:06:35.030 --> 00:06:40.880 align:middle line:84%
So you can already see that just
by utilizing the Google search

00:06:40.880 --> 00:06:43.280 align:middle line:84%
engine and utilizing
Google Dorks,

00:06:43.280 --> 00:06:46.280 align:middle line:84%
we can start finding
subdomains manually

00:06:46.280 --> 00:06:49.190 align:middle line:84%
and of course, this is something
that sublister would do.

00:06:49.190 --> 00:06:51.950 align:middle line:84%
But it's very important that you
learn how to do this yourself.

00:06:51.950 --> 00:06:53.100 align:middle line:90%
Now, why am I saying that?

00:06:53.100 --> 00:06:56.840 align:middle line:84%
Well, let's say we
wanted to find--

00:06:56.840 --> 00:07:01.790 align:middle line:84%
we can say, let's limit it
to subdomains of ine.com.

00:07:01.790 --> 00:07:04.440 align:middle line:90%
But we wanted to find files.

00:07:04.440 --> 00:07:07.450 align:middle line:84%
So we can say file type and then
we specify the type of file.

00:07:07.450 --> 00:07:09.290 align:middle line:90%
So let's say PDFs.

00:07:09.290 --> 00:07:11.150 align:middle line:84%
So you can start to
see that now, it's

00:07:11.150 --> 00:07:14.210 align:middle line:84%
going to limit the
results to subdomains

00:07:14.210 --> 00:07:17.180 align:middle line:84%
that have PDFs or
pages or subdomains

00:07:17.180 --> 00:07:18.780 align:middle line:90%
with pages that have PDFs.

00:07:18.780 --> 00:07:22.070 align:middle line:84%
So in this case, it looks
like we have a diagram here,

00:07:22.070 --> 00:07:24.200 align:middle line:90%
a network diagram.

00:07:24.200 --> 00:07:26.000 align:middle line:90%
Interesting.

00:07:26.000 --> 00:07:29.440 align:middle line:84%
And let's try and limit
this maybe to sales.

00:07:29.440 --> 00:07:34.570 align:middle line:84%
Let's see, oh, nothing there,
so nothing useful there.

00:07:34.570 --> 00:07:36.140 align:middle line:90%
Can we say CRM may be?

00:07:36.140 --> 00:07:36.640 align:middle line:90%
OK.

00:07:36.640 --> 00:07:38.380 align:middle line:90%
Nothing there.

00:07:38.380 --> 00:07:41.270 align:middle line:90%
Maybe marketing, nothing there.

00:07:41.270 --> 00:07:41.770 align:middle line:90%
OK.

00:07:41.770 --> 00:07:43.540 align:middle line:84%
So you can see that
we probably need

00:07:43.540 --> 00:07:49.270 align:middle line:84%
to make our search query
a bit more specific

00:07:49.270 --> 00:07:53.635 align:middle line:84%
or we pretty much do
not have anything--

00:07:53.635 --> 00:07:55.820 align:middle line:84%
we didn't get anything
returned by Google.

00:07:55.820 --> 00:08:00.010 align:middle line:84%
So let's try and limit
this to xlsx files

00:08:00.010 --> 00:08:02.800 align:middle line:84%
or Excel spreadsheet
files, nothing there.

00:08:02.800 --> 00:08:03.520 align:middle line:90%
OK.

00:08:03.520 --> 00:08:05.270 align:middle line:90%
That's good.

00:08:05.270 --> 00:08:07.810 align:middle line:84%
Maybe PDF, we've
already done PDF.

00:08:07.810 --> 00:08:09.430 align:middle line:90%
So can we say documents?

00:08:09.430 --> 00:08:13.880 align:middle line:90%
So doc or docx, nothing there.

00:08:13.880 --> 00:08:19.180 align:middle line:84%
Maybe zip, I believe zip still
works or .zip but you get

00:08:19.180 --> 00:08:19.760 align:middle line:90%
the idea.

00:08:19.760 --> 00:08:23.570 align:middle line:84%
So we can limit it
to specific files.

00:08:23.570 --> 00:08:30.280 align:middle line:84%
So if we say PDF or maybe
we can say filetype:xlsx.

00:08:30.280 --> 00:08:32.440 align:middle line:84%
And instead of searching
for subdomains,

00:08:32.440 --> 00:08:36.839 align:middle line:84%
we just search for-- we
limit the results to ine.com.

00:08:36.839 --> 00:08:38.530 align:middle line:90%
In this case, nothing there.

00:08:38.530 --> 00:08:39.685 align:middle line:90%
So maybe docx.

00:08:39.685 --> 00:08:42.250 align:middle line:90%


00:08:42.250 --> 00:08:42.750 align:middle line:90%
OK.

00:08:42.750 --> 00:08:45.120 align:middle line:84%
So Google has, of
course, detected

00:08:45.120 --> 00:08:47.940 align:middle line:84%
that we are making too many
requests, good on them.

00:08:47.940 --> 00:08:50.700 align:middle line:90%
We are making too many requests.

00:08:50.700 --> 00:08:54.310 align:middle line:84%
Taxis, taxis, I believe that's
all the taxis I can see there.

00:08:54.310 --> 00:08:54.810 align:middle line:90%
So OK.

00:08:54.810 --> 00:08:56.018 align:middle line:90%
That looks like it's working.

00:08:56.018 --> 00:08:58.350 align:middle line:90%
So nothing there.

00:08:58.350 --> 00:09:02.820 align:middle line:84%
So that is how to
essentially limit

00:09:02.820 --> 00:09:06.510 align:middle line:84%
or how to perform subdomain
enumeration manually.

00:09:06.510 --> 00:09:10.260 align:middle line:84%
Now, one other thing that we
can do for example, if we're

00:09:10.260 --> 00:09:13.080 align:middle line:84%
looking for information
regarding employees,

00:09:13.080 --> 00:09:16.140 align:middle line:84%
for example, we can
say a site ine.com,

00:09:16.140 --> 00:09:17.430 align:middle line:90%
and then we can say employee.

00:09:17.430 --> 00:09:19.990 align:middle line:84%
So we can enter a standard
search query here.

00:09:19.990 --> 00:09:22.380 align:middle line:84%
So we can say site
ine.com employees.

00:09:22.380 --> 00:09:26.550 align:middle line:84%
And you can see we get results
based on the actual keyword

00:09:26.550 --> 00:09:29.610 align:middle line:90%
that we specified there.

00:09:29.610 --> 00:09:32.890 align:middle line:84%
So if we were trying to look for
employees or individuals that

00:09:32.890 --> 00:09:35.740 align:middle line:84%
work at INE, this would be
one of the ways we can do it.

00:09:35.740 --> 00:09:38.760 align:middle line:84%
So you can see that
you can limit it

00:09:38.760 --> 00:09:41.920 align:middle line:84%
to what information you're
looking for specifically.

00:09:41.920 --> 00:09:43.870 align:middle line:90%
So there we are.

00:09:43.870 --> 00:09:47.220 align:middle line:90%
We can also say maybe--

00:09:47.220 --> 00:09:51.160 align:middle line:84%
let's see, ine.com
maybe instructors.

00:09:51.160 --> 00:09:52.452 align:middle line:90%
And this will probably display.

00:09:52.452 --> 00:09:52.993 align:middle line:90%
There we are.

00:09:52.993 --> 00:09:54.400 align:middle line:84%
So we have the
instructor's page.

00:09:54.400 --> 00:09:55.600 align:middle line:90%
So you get the idea.

00:09:55.600 --> 00:09:57.850 align:middle line:84%
You can pretty much search
for whatever you're looking

00:09:57.850 --> 00:10:00.220 align:middle line:90%
for by utilizing Google Dorks.

00:10:00.220 --> 00:10:03.640 align:middle line:84%
Now, let me take you through a
couple of examples that might

00:10:03.640 --> 00:10:05.510 align:middle line:90%
not be too good to show you.

00:10:05.510 --> 00:10:09.550 align:middle line:84%
But if we were looking
maybe for sites

00:10:09.550 --> 00:10:12.730 align:middle line:84%
with directory
listing enabled, we

00:10:12.730 --> 00:10:16.480 align:middle line:84%
can use the intitle
search filter

00:10:16.480 --> 00:10:20.440 align:middle line:84%
and specify that
within the title,

00:10:20.440 --> 00:10:23.170 align:middle line:90%
we're looking for index of.

00:10:23.170 --> 00:10:24.820 align:middle line:84%
So this is a common
vulnerability

00:10:24.820 --> 00:10:26.480 align:middle line:90%
within web servers.

00:10:26.480 --> 00:10:28.660 align:middle line:84%
So if you're familiar
with how web servers work

00:10:28.660 --> 00:10:31.300 align:middle line:84%
or if you've ever
set one up, there

00:10:31.300 --> 00:10:35.620 align:middle line:84%
is a misconfiguration
called directory listing.

00:10:35.620 --> 00:10:38.020 align:middle line:84%
Now, it's not really
a misconfiguration.

00:10:38.020 --> 00:10:42.070 align:middle line:84%
But you really rarely want
to have this open or running

00:10:42.070 --> 00:10:43.335 align:middle line:90%
on a production site.

00:10:43.335 --> 00:10:44.710 align:middle line:84%
The reason for
that is because it

00:10:44.710 --> 00:10:48.230 align:middle line:84%
allows users to view the
contents of that directory.

00:10:48.230 --> 00:10:50.000 align:middle line:84%
So in this case,
it looks like we

00:10:50.000 --> 00:10:52.000 align:middle line:84%
have a couple of sites
that are hosting probably

00:10:52.000 --> 00:10:53.320 align:middle line:90%
pirated movies.

00:10:53.320 --> 00:10:55.810 align:middle line:84%
So I wouldn't recommend
clicking on that.

00:10:55.810 --> 00:10:59.890 align:middle line:84%
And you can see that
nothing else there.

00:10:59.890 --> 00:11:01.600 align:middle line:84%
It's not displaying
anything else there.

00:11:01.600 --> 00:11:07.870 align:middle line:84%
So next, we have a
couple of other sites.

00:11:07.870 --> 00:11:09.790 align:middle line:90%
There we go.

00:11:09.790 --> 00:11:10.660 align:middle line:90%
You get the idea.

00:11:10.660 --> 00:11:14.590 align:middle line:84%
First, to show you how this
works, if I click on maybe--

00:11:14.590 --> 00:11:16.460 align:middle line:84%
this looks like a
government website.

00:11:16.460 --> 00:11:18.730 align:middle line:84%
So index of data,
that's probably secured.

00:11:18.730 --> 00:11:19.780 align:middle line:90%
But let's click on that.

00:11:19.780 --> 00:11:20.410 align:middle line:90%
No, it isn't.

00:11:20.410 --> 00:11:23.320 align:middle line:84%
So it looks like they have
data that's publicly exposed.

00:11:23.320 --> 00:11:25.990 align:middle line:84%
I'm not really sure
what this data is.

00:11:25.990 --> 00:11:28.910 align:middle line:84%
It looks like-- yeah, I'm
not going to click on that.

00:11:28.910 --> 00:11:31.870 align:middle line:84%
Anyway, this is publicly
accessible information.

00:11:31.870 --> 00:11:36.640 align:middle line:84%
But again, I'm just doing
this for educational purposes.

00:11:36.640 --> 00:11:39.970 align:middle line:84%
There are a couple
of other searches

00:11:39.970 --> 00:11:43.820 align:middle line:84%
we can perform that I
haven't covered here.

00:11:43.820 --> 00:11:47.500 align:middle line:84%
But let's say we
wanted to try and find

00:11:47.500 --> 00:11:49.030 align:middle line:90%
an older version of a website.

00:11:49.030 --> 00:11:52.960 align:middle line:84%
This is very important, because
companies can modify websites

00:11:52.960 --> 00:11:55.130 align:middle line:84%
and are constantly making
changes to website.

00:11:55.130 --> 00:11:59.170 align:middle line:84%
So if you wanted to see what
the website looked maybe five

00:11:59.170 --> 00:12:00.700 align:middle line:84%
months ago or
maybe one year ago,

00:12:00.700 --> 00:12:04.740 align:middle line:84%
you can use the cache operator
and then specify the site

00:12:04.740 --> 00:12:05.240 align:middle line:90%
itself.

00:12:05.240 --> 00:12:09.640 align:middle line:84%
So cache ine.com, and we'll
give this a couple of seconds.

00:12:09.640 --> 00:12:14.960 align:middle line:84%
And again, it looks like I
have the same issues, so boats,

00:12:14.960 --> 00:12:16.210 align:middle line:90%
do I see any more boats there?

00:12:16.210 --> 00:12:17.020 align:middle line:90%
Verify.

00:12:17.020 --> 00:12:18.070 align:middle line:90%
OK.

00:12:18.070 --> 00:12:19.880 align:middle line:84%
Google probably
allow us to do that.

00:12:19.880 --> 00:12:21.490 align:middle line:90%
So there we are.

00:12:21.490 --> 00:12:25.610 align:middle line:84%
So that'll display the
Google web cache for ine.com.

00:12:25.610 --> 00:12:30.120 align:middle line:84%
And in this case, it looks
like we don't have any--

00:12:30.120 --> 00:12:32.040 align:middle line:84%
this is pretty much
the latest version.

00:12:32.040 --> 00:12:36.560 align:middle line:84%
We can also utilize
the Wayback Machine.

00:12:36.560 --> 00:12:38.120 align:middle line:84%
The Wayback Machine
is a site that

00:12:38.120 --> 00:12:40.700 align:middle line:84%
stores older versions of
websites it essentially

00:12:40.700 --> 00:12:44.570 align:middle line:84%
takes a snapshot of a website
after a fixed period of time,

00:12:44.570 --> 00:12:46.340 align:middle line:90%
and it stores those snapshots.

00:12:46.340 --> 00:12:52.440 align:middle line:84%
So I can say
https://ine.com, and it's

00:12:52.440 --> 00:12:54.588 align:middle line:90%
going to take a second.

00:12:54.588 --> 00:12:55.130 align:middle line:90%
There we are.

00:12:55.130 --> 00:12:58.080 align:middle line:84%
It's taken snapshots
all the way from 1999.

00:12:58.080 --> 00:13:00.270 align:middle line:84%
So we can see the earliest
version of this website.

00:13:00.270 --> 00:13:03.380 align:middle line:84%
So I'll click on the snapshot
maybe on the 9th of February.

00:13:03.380 --> 00:13:08.912 align:middle line:84%
This is very close to when I was
born, which is scary, actually.

00:13:08.912 --> 00:13:09.620 align:middle line:90%
But there we are.

00:13:09.620 --> 00:13:12.590 align:middle line:90%
Let's see how the website looks.

00:13:12.590 --> 00:13:14.000 align:middle line:84%
It looks like he's
saying Welcome

00:13:14.000 --> 00:13:15.990 align:middle line:90%
to the Great Web of China.

00:13:15.990 --> 00:13:18.590 align:middle line:84%
I'm guessing that's before
INE actually set it up

00:13:18.590 --> 00:13:20.400 align:middle line:90%
for its current use case.

00:13:20.400 --> 00:13:22.010 align:middle line:90%
Let's see how we looked in 2006.

00:13:22.010 --> 00:13:25.400 align:middle line:84%
So let's see how it
looked on August the 3rd.

00:13:25.400 --> 00:13:26.340 align:middle line:90%
This is really cool.

00:13:26.340 --> 00:13:29.300 align:middle line:84%
So the snapshot was
taken 2200 hours.

00:13:29.300 --> 00:13:30.560 align:middle line:90%
Let's click on that one there.

00:13:30.560 --> 00:13:33.180 align:middle line:90%


00:13:33.180 --> 00:13:34.440 align:middle line:90%
This is 2006.

00:13:34.440 --> 00:13:38.540 align:middle line:90%
So I'm expecting it to be--

00:13:38.540 --> 00:13:40.760 align:middle line:84%
well that snapshot doesn't
really make any sense.

00:13:40.760 --> 00:13:44.930 align:middle line:84%
Let's take a look at a more
recent one, maybe 2016.

00:13:44.930 --> 00:13:46.430 align:middle line:84%
That's probably
where things started

00:13:46.430 --> 00:13:47.580 align:middle line:90%
getting really interesting.

00:13:47.580 --> 00:13:52.640 align:middle line:90%
So maybe March the 12th, 2016.

00:13:52.640 --> 00:13:56.150 align:middle line:84%
So we can start to see how
the website looked then.

00:13:56.150 --> 00:13:58.970 align:middle line:84%
So you can see, we
already have in the title,

00:13:58.970 --> 00:14:00.530 align:middle line:90%
we have CCI training.

00:14:00.530 --> 00:14:04.280 align:middle line:84%
So I'm just going to give this
a couple of seconds to load up.

00:14:04.280 --> 00:14:08.460 align:middle line:90%


00:14:08.460 --> 00:14:10.860 align:middle line:84%
So if you ever want to
know how a site looked

00:14:10.860 --> 00:14:13.905 align:middle line:84%
in 2016 like for
example ine.com,

00:14:13.905 --> 00:14:15.220 align:middle line:90%
this is how it looked like.

00:14:15.220 --> 00:14:17.730 align:middle line:84%
So the Wayback Machine
is really cool,

00:14:17.730 --> 00:14:20.670 align:middle line:84%
because it gives you
a historical view

00:14:20.670 --> 00:14:22.050 align:middle line:90%
of what a website look like.

00:14:22.050 --> 00:14:24.360 align:middle line:84%
Let me show you something
even cooler than that.

00:14:24.360 --> 00:14:26.340 align:middle line:84%
I'll show you what
hackersploit.org look

00:14:26.340 --> 00:14:28.080 align:middle line:90%
like during its inception.

00:14:28.080 --> 00:14:30.420 align:middle line:90%
So hackersploit.org.

00:14:30.420 --> 00:14:33.750 align:middle line:84%
I know that we really had
very, very bad theme right

00:14:33.750 --> 00:14:36.970 align:middle line:84%
around 2018 when I
first set the site up.

00:14:36.970 --> 00:14:40.140 align:middle line:84%
So let's take a look at
April the 20th, 2018.

00:14:40.140 --> 00:14:42.120 align:middle line:84%
I'm not really sure
what to expect,

00:14:42.120 --> 00:14:46.372 align:middle line:84%
but this had a different title,
hackersploit cybersecurity.

00:14:46.372 --> 00:14:48.330 align:middle line:84%
Let's see what that looks
like, because I think

00:14:48.330 --> 00:14:50.920 align:middle line:90%
I've even forgone that myself.

00:14:50.920 --> 00:14:51.420 align:middle line:90%
Yeah.

00:14:51.420 --> 00:14:53.128 align:middle line:84%
We'll just give this
a couple of seconds,

00:14:53.128 --> 00:14:55.950 align:middle line:84%
because it needs to fetch that
content and then, of course,

00:14:55.950 --> 00:15:00.890 align:middle line:84%
render it so that we
can view the web page.

00:15:00.890 --> 00:15:04.474 align:middle line:84%
So this is our
hackersploit.org looked.

00:15:04.474 --> 00:15:07.880 align:middle line:84%
Nothing too different but the
theme definitely has changed.

00:15:07.880 --> 00:15:12.000 align:middle line:84%
But you can get an idea as
to how this would be useful.

00:15:12.000 --> 00:15:15.110 align:middle line:84%
So a good example
of this is I'll

00:15:15.110 --> 00:15:19.100 align:middle line:84%
give you a personal example
or personal analogies.

00:15:19.100 --> 00:15:21.110 align:middle line:84%
When I was performing a
pen test for a company

00:15:21.110 --> 00:15:25.610 align:middle line:84%
that I can't name,
they had information

00:15:25.610 --> 00:15:28.970 align:middle line:84%
that was potentially
useful for attackers

00:15:28.970 --> 00:15:32.810 align:middle line:84%
on one of an older
version of their site,

00:15:32.810 --> 00:15:35.420 align:middle line:84%
probably four or five
years in the past.

00:15:35.420 --> 00:15:38.450 align:middle line:84%
And they thought that
information was not

00:15:38.450 --> 00:15:39.440 align:middle line:90%
accessible by anyone.

00:15:39.440 --> 00:15:42.290 align:middle line:84%
And with the Wayback Machine,
we could go ahead and view it.

00:15:42.290 --> 00:15:46.260 align:middle line:84%
And there was a lot of sensitive
information that was leaked.

00:15:46.260 --> 00:15:49.970 align:middle line:84%
So you can definitely take a
look at the Wayback Machine

00:15:49.970 --> 00:15:53.630 align:middle line:84%
to get a historical view of
what the website looked like.

00:15:53.630 --> 00:15:56.570 align:middle line:84%
And of course, that's not
just why you should be doing.

00:15:56.570 --> 00:15:59.030 align:middle line:84%
It is because older
version of website

00:15:59.030 --> 00:16:01.970 align:middle line:84%
might have potentially
important information

00:16:01.970 --> 00:16:06.050 align:middle line:84%
like email addresses, contact
information, et cetera.

00:16:06.050 --> 00:16:09.080 align:middle line:84%
So let's head back
over to google.com.

00:16:09.080 --> 00:16:12.560 align:middle line:84%
And I'll probably explore
a few more Google Dorks

00:16:12.560 --> 00:16:14.630 align:middle line:84%
that we can use or
that you can use

00:16:14.630 --> 00:16:18.330 align:middle line:84%
rather if you're ever trying
to find interesting stuff.

00:16:18.330 --> 00:16:21.170 align:middle line:84%
So another example of
this is, let's say,

00:16:21.170 --> 00:16:28.175 align:middle line:84%
we wanted to see if some
website has inadvertently

00:16:28.175 --> 00:16:34.010 align:middle line:84%
listed, or saved, or exposed the
directory that has passwords.

00:16:34.010 --> 00:16:35.430 align:middle line:90%
A lot of people do that.

00:16:35.430 --> 00:16:42.150 align:middle line:84%
So we can, for example, say
inurl, and in this case,

00:16:42.150 --> 00:16:45.760 align:middle line:90%
we can say auth user file.txt.

00:16:45.760 --> 00:16:49.050 align:middle line:90%


00:16:49.050 --> 00:16:52.000 align:middle line:84%
And you can already see
that a few sites have them.

00:16:52.000 --> 00:16:56.310 align:middle line:84%
So for example, this one here,
which is just an IP address.

00:16:56.310 --> 00:17:00.120 align:middle line:84%
And they probably have this
exposed on the internet.

00:17:00.120 --> 00:17:03.690 align:middle line:84%
And that means that
there's a login form here.

00:17:03.690 --> 00:17:05.585 align:middle line:90%
There's probably the password--

00:17:05.585 --> 00:17:06.960 align:middle line:84%
the passwords are
probably leaked

00:17:06.960 --> 00:17:07.599 align:middle line:90%
on this page.

00:17:07.599 --> 00:17:09.780 align:middle line:84%
I'm not going to get
into that, because again,

00:17:09.780 --> 00:17:14.200 align:middle line:84%
that'll be going over
what I'm allowed to do.

00:17:14.200 --> 00:17:19.300 align:middle line:84%
But looks like we
have another one here.

00:17:19.300 --> 00:17:20.720 align:middle line:90%
And it looks like the same site.

00:17:20.720 --> 00:17:21.220 align:middle line:90%
Interesting.

00:17:21.220 --> 00:17:22.000 align:middle line:90%
Very, very interesting.

00:17:22.000 --> 00:17:23.180 align:middle line:90%
Let's change this around.

00:17:23.180 --> 00:17:25.069 align:middle line:84%
I think there's
another one we can use.

00:17:25.069 --> 00:17:30.940 align:middle line:84%
So we can say inurl password.txt
or maybe intitle password.txt.

00:17:30.940 --> 00:17:32.680 align:middle line:84%
So it looks like
we have a couple

00:17:32.680 --> 00:17:35.830 align:middle line:84%
of sites that have
leaked their password.txt

00:17:35.830 --> 00:17:39.110 align:middle line:90%
file on the internet.

00:17:39.110 --> 00:17:40.360 align:middle line:90%
Let's take a look at this one.

00:17:40.360 --> 00:17:43.030 align:middle line:84%
Yeah, that's the
etc password file.

00:17:43.030 --> 00:17:46.480 align:middle line:84%
And hopefully, these individuals
or the owners of this website

00:17:46.480 --> 00:17:50.740 align:middle line:84%
here haven't inadvertently
leaked this information

00:17:50.740 --> 00:17:51.430 align:middle line:90%
to the public.

00:17:51.430 --> 00:17:52.450 align:middle line:90%
But there you go.

00:17:52.450 --> 00:17:54.610 align:middle line:84%
You can see that
there is a password

00:17:54.610 --> 00:17:59.110 align:middle line:84%
information or at least
usernames for a specific domain

00:17:59.110 --> 00:17:59.920 align:middle line:90%
here.

00:17:59.920 --> 00:18:01.690 align:middle line:90%
But you get the idea.

00:18:01.690 --> 00:18:03.670 align:middle line:84%
You can do a lot
with Google Dorks.

00:18:03.670 --> 00:18:06.760 align:middle line:84%
Now, I've not covered all
of the most important ones,

00:18:06.760 --> 00:18:10.510 align:middle line:84%
because I'm really focused
on passive enumeration

00:18:10.510 --> 00:18:12.400 align:middle line:84%
or passive
information gathering.

00:18:12.400 --> 00:18:16.420 align:middle line:84%
One of the greatest
resources for whenever you're

00:18:16.420 --> 00:18:20.470 align:middle line:84%
trying to utilize Google Dorks
or perform Google Hacking

00:18:20.470 --> 00:18:23.500 align:middle line:84%
is the Google Hacking
Database, which

00:18:23.500 --> 00:18:25.990 align:middle line:84%
is owned by Offensive Security,
the parent company that

00:18:25.990 --> 00:18:27.620 align:middle line:90%
owns and develops Kali Linux.

00:18:27.620 --> 00:18:30.430 align:middle line:84%
So this is a database
of Google Dorks

00:18:30.430 --> 00:18:32.930 align:middle line:84%
that can allow you to
find specific information.

00:18:32.930 --> 00:18:34.570 align:middle line:84%
So for example,
in this case, this

00:18:34.570 --> 00:18:37.210 align:middle line:84%
will essentially--
this Google Dork

00:18:37.210 --> 00:18:40.310 align:middle line:84%
can be used to find files that
contain juicy information.

00:18:40.310 --> 00:18:42.610 align:middle line:90%
So these are government sites.

00:18:42.610 --> 00:18:47.050 align:middle line:84%
So you can see we have
site gov dot whatever.

00:18:47.050 --> 00:18:50.890 align:middle line:84%
Intitle index of because
directory listing is enabled

00:18:50.890 --> 00:18:52.990 align:middle line:90%
and the file type is CSV.

00:18:52.990 --> 00:18:54.400 align:middle line:90%
So we can actually test this.

00:18:54.400 --> 00:18:56.860 align:middle line:84%
Let's see if we actually
find some juicy files, which

00:18:56.860 --> 00:19:00.130 align:middle line:84%
of course, we will because
people don't take the time

00:19:00.130 --> 00:19:01.210 align:middle line:90%
to secure their stuff.

00:19:01.210 --> 00:19:03.850 align:middle line:90%
So there we are.

00:19:03.850 --> 00:19:06.340 align:middle line:90%
A lot of sites here.

00:19:06.340 --> 00:19:08.110 align:middle line:84%
These all look like
government sites

00:19:08.110 --> 00:19:09.340 align:middle line:90%
for different governments.

00:19:09.340 --> 00:19:11.690 align:middle line:84%
And as I said, I'm not going
to be going through this.

00:19:11.690 --> 00:19:15.610 align:middle line:84%
But you can see that they're all
being leaked, because directory

00:19:15.610 --> 00:19:16.750 align:middle line:90%
listing is enabled.

00:19:16.750 --> 00:19:18.310 align:middle line:84%
Most of these are
WordPress sites,

00:19:18.310 --> 00:19:21.280 align:middle line:84%
which makes a lot of
sense, because WordPress

00:19:21.280 --> 00:19:24.820 align:middle line:90%
can be quite hard to lock down.

00:19:24.820 --> 00:19:26.860 align:middle line:84%
But yeah, you can
also limit this to--

00:19:26.860 --> 00:19:29.050 align:middle line:84%
you can specify
additional keywords

00:19:29.050 --> 00:19:30.590 align:middle line:90%
to find what you're looking for.

00:19:30.590 --> 00:19:33.730 align:middle line:90%
So maybe you can say passwords.

00:19:33.730 --> 00:19:34.360 align:middle line:90%
There we are.

00:19:34.360 --> 00:19:37.420 align:middle line:84%
And in this case,
that will limit it

00:19:37.420 --> 00:19:45.592 align:middle line:84%
to any URL with
the gov dot prefix.

00:19:45.592 --> 00:19:49.080 align:middle line:90%


00:19:49.080 --> 00:19:52.920 align:middle line:84%
So you can utilize the
Google Hacking Database

00:19:52.920 --> 00:19:54.670 align:middle line:90%
to find specific information.

00:19:54.670 --> 00:20:00.940 align:middle line:84%
So let's take a look at a
couple of others that might

00:20:00.940 --> 00:20:02.090 align:middle line:90%
be potentially interesting.

00:20:02.090 --> 00:20:04.070 align:middle line:90%
These are the latest ones here.

00:20:04.070 --> 00:20:05.420 align:middle line:90%
Let's run a few filters.

00:20:05.420 --> 00:20:11.130 align:middle line:84%
So let's say we're looking
for files containing passwords

00:20:11.130 --> 00:20:12.540 align:middle line:90%
probably.

00:20:12.540 --> 00:20:14.430 align:middle line:84%
There we are, files
containing passwords.

00:20:14.430 --> 00:20:21.120 align:middle line:84%
We can then utilize these
particular docs or search

00:20:21.120 --> 00:20:25.290 align:middle line:84%
filters to look for files
that contained passwords.

00:20:25.290 --> 00:20:31.470 align:middle line:84%
So we can use this one for
example here or maybe this one

00:20:31.470 --> 00:20:32.703 align:middle line:90%
here.

00:20:32.703 --> 00:20:35.120 align:middle line:84%
Let's see whether we are able
to find any credentials that

00:20:35.120 --> 00:20:36.078 align:middle line:90%
might have been leaked.

00:20:36.078 --> 00:20:39.590 align:middle line:90%


00:20:39.590 --> 00:20:40.475 align:middle line:90%
There we are.

00:20:40.475 --> 00:20:43.740 align:middle line:84%
You can see that we
might have a few here.

00:20:43.740 --> 00:20:48.350 align:middle line:84%
So this looks like potentially
interesting website.

00:20:48.350 --> 00:20:51.730 align:middle line:90%


00:20:51.730 --> 00:20:53.920 align:middle line:90%
And that is--

00:20:53.920 --> 00:20:56.183 align:middle line:84%
I probably won't
check them, because I

00:20:56.183 --> 00:20:57.100 align:middle line:90%
don't want to do that.

00:20:57.100 --> 00:21:01.210 align:middle line:84%
But you can do a lot of stuff
with the Google search engine

00:21:01.210 --> 00:21:02.800 align:middle line:90%
through the use of Google Dorks.

00:21:02.800 --> 00:21:06.040 align:middle line:84%
I've just gone through some
of the most interesting ones

00:21:06.040 --> 00:21:08.380 align:middle line:84%
that you can do from the
perspective of a penetration

00:21:08.380 --> 00:21:09.850 align:middle line:90%
tester legally speaking.

00:21:09.850 --> 00:21:13.690 align:middle line:84%
So I'm limiting the
results to a particular URL

00:21:13.690 --> 00:21:16.960 align:middle line:84%
or a particular title or
particular domain or subdomain.

00:21:16.960 --> 00:21:21.460 align:middle line:84%
So definitely take a look at
the Google Hacking Database.

00:21:21.460 --> 00:21:27.110 align:middle line:84%
As I said, this is pretty
much a one stop shop,

00:21:27.110 --> 00:21:30.340 align:middle line:84%
if you ever trying to find
potentially interesting files

00:21:30.340 --> 00:21:33.910 align:middle line:84%
or potentially
incriminating files

00:21:33.910 --> 00:21:37.900 align:middle line:84%
that a company might
not have secured

00:21:37.900 --> 00:21:39.470 align:middle line:90%
with regards to their website.

00:21:39.470 --> 00:21:41.380 align:middle line:84%
So definitely take
a look at this.

00:21:41.380 --> 00:21:43.840 align:middle line:84%
Especially if they
have a WordPress site,

00:21:43.840 --> 00:21:47.020 align:middle line:84%
then you can limit this, again,
by using the filter option

00:21:47.020 --> 00:21:50.350 align:middle line:84%
to a particular content
management system,

00:21:50.350 --> 00:21:53.830 align:middle line:84%
or you can just perform a
search maybe like WordPress.

00:21:53.830 --> 00:21:54.520 align:middle line:90%
There we are.

00:21:54.520 --> 00:21:58.330 align:middle line:84%
And in this case, we can also
limit this to maybe WordPress.

00:21:58.330 --> 00:21:59.320 align:middle line:90%
There we are.

00:21:59.320 --> 00:22:01.960 align:middle line:84%
And these are all the
Google Dorks for WordPress.

00:22:01.960 --> 00:22:08.160 align:middle line:84%
So you can try and find
WordPress config backup files.

00:22:08.160 --> 00:22:10.040 align:middle line:84%
This is something
that I've used before.

00:22:10.040 --> 00:22:13.930 align:middle line:84%
So let me just take
a step back here.

00:22:13.930 --> 00:22:17.820 align:middle line:84%
So sites that have taken a
backup of the WordPress config

00:22:17.820 --> 00:22:20.100 align:middle line:84%
file and have not
deleted that backup.

00:22:20.100 --> 00:22:22.620 align:middle line:84%
If you're not familiar with
it, the WordPress config file

00:22:22.620 --> 00:22:26.570 align:middle line:84%
pretty much contains credentials
to the MySQL database.

00:22:26.570 --> 00:22:29.670 align:middle line:84%
So this could be
potentially damning

00:22:29.670 --> 00:22:31.510 align:middle line:90%
for a particular company.

00:22:31.510 --> 00:22:34.200 align:middle line:84%
But that concludes the
practical demonstration side

00:22:34.200 --> 00:22:36.860 align:middle line:90%
of this video.

00:22:36.860 --> 00:22:38.960 align:middle line:84%
In the next video, we're
going to be exploring

00:22:38.960 --> 00:22:42.170 align:middle line:84%
the process of harvesting email
addresses through publicly

00:22:42.170 --> 00:22:45.710 align:middle line:84%
available sources or
databases with a tool called

00:22:45.710 --> 00:22:46.700 align:middle line:90%
The Harvester.

00:22:46.700 --> 00:22:50.616 align:middle line:84%
So I'll be seeing you
in the next video.

00:22:50.616 --> 00:22:51.116 align:middle line:90%