WEBVTT

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


00:00:03.472 --> 00:00:06.944 align:middle line:90%
[MUSIC PLAYING]

00:00:06.944 --> 00:00:09.930 align:middle line:90%


00:00:09.930 --> 00:00:13.152 align:middle line:84%
Subdomain enumeration
with Sublist3r.

00:00:13.152 --> 00:00:15.360 align:middle line:84%
In this video, we're going
to be taking a look at how

00:00:15.360 --> 00:00:18.660 align:middle line:84%
to passively
enumerate subdomains

00:00:18.660 --> 00:00:21.600 align:middle line:84%
for a specific domain
through the use of a really

00:00:21.600 --> 00:00:24.630 align:middle line:84%
cool open source tool
called Sublist3r.

00:00:24.630 --> 00:00:27.600 align:middle line:84%
So again, I'm going to be
performing this on my Kali

00:00:27.600 --> 00:00:29.400 align:middle line:84%
Linux VM, and we're
going to be, again,

00:00:29.400 --> 00:00:32.100 align:middle line:84%
exploring or taking a
look at the same sites

00:00:32.100 --> 00:00:34.720 align:middle line:90%
that we've been using thus far.

00:00:34.720 --> 00:00:36.750 align:middle line:84%
So again, the important
thing to note here

00:00:36.750 --> 00:00:40.570 align:middle line:84%
is we're not performing
subdomain brute forcing.

00:00:40.570 --> 00:00:42.790 align:middle line:84%
So we're not actively
engaging with the target.

00:00:42.790 --> 00:00:45.090 align:middle line:84%
This is not active
information gathering.

00:00:45.090 --> 00:00:48.310 align:middle line:84%
We're essentially
using-- we're using

00:00:48.310 --> 00:00:51.940 align:middle line:84%
publicly available sources
of information, like search

00:00:51.940 --> 00:00:55.300 align:middle line:84%
engines, like Google,
Bing, Yahoo, et cetera,

00:00:55.300 --> 00:00:58.240 align:middle line:84%
to find subdomains that
might have been indexed

00:00:58.240 --> 00:00:59.740 align:middle line:90%
by these search engines.

00:00:59.740 --> 00:01:03.490 align:middle line:84%
And Sublist3r is a
really, really useful tool

00:01:03.490 --> 00:01:07.270 align:middle line:84%
that will essentially allow us
to do this as efficiently as

00:01:07.270 --> 00:01:07.820 align:middle line:90%
possible.

00:01:07.820 --> 00:01:10.885 align:middle line:84%
So I'm going to switch
over to my Kali Linux VM.

00:01:10.885 --> 00:01:14.080 align:middle line:90%


00:01:14.080 --> 00:01:16.420 align:middle line:84%
All right, so I'm back
on my Kali Linux VM,

00:01:16.420 --> 00:01:18.940 align:middle line:84%
and I'm currently on the
Sublist3r GitHub repository.

00:01:18.940 --> 00:01:20.860 align:middle line:84%
By the way, all credits
go to the author

00:01:20.860 --> 00:01:25.270 align:middle line:84%
of this really cool tool, Ahmed
Aboul-Ela, a really fantastic

00:01:25.270 --> 00:01:28.365 align:middle line:84%
tool that I've used
for many, many years.

00:01:28.365 --> 00:01:29.990 align:middle line:84%
And if you want to
learn more about it,

00:01:29.990 --> 00:01:32.660 align:middle line:84%
I recommend taking a look
at the GitHub repository.

00:01:32.660 --> 00:01:34.120 align:middle line:84%
So as you can see
right over here,

00:01:34.120 --> 00:01:36.610 align:middle line:84%
Sublist3r is a
Python tool that's

00:01:36.610 --> 00:01:39.910 align:middle line:84%
designed to enumerate subdomains
of websites using OSINT, which

00:01:39.910 --> 00:01:42.400 align:middle line:90%
is Open Source INTelligence.

00:01:42.400 --> 00:01:44.080 align:middle line:84%
That essentially
means information

00:01:44.080 --> 00:01:45.880 align:middle line:84%
that is publicly
available, which

00:01:45.880 --> 00:01:50.590 align:middle line:84%
falls in line with passive
information gathering.

00:01:50.590 --> 00:01:53.770 align:middle line:84%
It helps penetration testers and
bug hunters collect and gather

00:01:53.770 --> 00:01:56.560 align:middle line:84%
subdomains for the domain
they are targeting.

00:01:56.560 --> 00:01:58.720 align:middle line:84%
Sublist3r enumerates
subdomains using

00:01:58.720 --> 00:02:02.140 align:middle line:84%
many search engines, such as
Google, Yahoo, Bing, Baidu,

00:02:02.140 --> 00:02:03.130 align:middle line:90%
and Ask.

00:02:03.130 --> 00:02:05.050 align:middle line:84%
Sublist3r also
enumerates subdomains

00:02:05.050 --> 00:02:08.650 align:middle line:84%
using Netcraft, VirusTotal,
ThreatCrowd, DNSdumpster, which

00:02:08.650 --> 00:02:11.110 align:middle line:90%
we've used, and ReverseDNS.

00:02:11.110 --> 00:02:14.770 align:middle line:84%
And subbrute, which
was another script,

00:02:14.770 --> 00:02:17.350 align:middle line:84%
was integrated with
Sublist3r to increase

00:02:17.350 --> 00:02:20.330 align:middle line:84%
the possibility of finding more
subdomains using brute force.

00:02:20.330 --> 00:02:23.210 align:middle line:84%
So this tool also
supports brute force,

00:02:23.210 --> 00:02:28.870 align:middle line:84%
and we will not be utilizing
that functionality because that

00:02:28.870 --> 00:02:31.390 align:middle line:84%
essentially falls into the
domain of active information

00:02:31.390 --> 00:02:33.040 align:middle line:84%
gathering because,
at that point,

00:02:33.040 --> 00:02:35.800 align:middle line:84%
we'll be actively
engaging with the target

00:02:35.800 --> 00:02:38.600 align:middle line:84%
system or, in this
case, the target domain.

00:02:38.600 --> 00:02:43.630 align:middle line:84%
So Sublist3r is already part
of the Kali Linux repositories,

00:02:43.630 --> 00:02:45.918 align:middle line:84%
which means you can
install it by typing

00:02:45.918 --> 00:02:46.960 align:middle line:90%
in the following command.

00:02:46.960 --> 00:02:48.670 align:middle line:84%
It doesn't come
preinstalled, but it's

00:02:48.670 --> 00:02:50.410 align:middle line:90%
available within the repos.

00:02:50.410 --> 00:02:55.690 align:middle line:84%
So if I type in sudo app-get
install and sublist3r,

00:02:55.690 --> 00:02:57.970 align:middle line:84%
you can see I already
have it installed.

00:02:57.970 --> 00:03:04.990 align:middle line:84%
And the actual syntax or
the usage instructions

00:03:04.990 --> 00:03:06.740 align:middle line:90%
are fairly easy to understand.

00:03:06.740 --> 00:03:08.350 align:middle line:84%
You can see that
you need to specify

00:03:08.350 --> 00:03:12.310 align:middle line:84%
the domain with the -d
argument or the -d option.

00:03:12.310 --> 00:03:14.643 align:middle line:84%
You also have the long form
if you want to specify that.

00:03:14.643 --> 00:03:16.018 align:middle line:84%
And then, of
course, in our case,

00:03:16.018 --> 00:03:18.040 align:middle line:84%
we're going to be specifying
the search engines.

00:03:18.040 --> 00:03:20.810 align:middle line:84%
So you might be asking yourself,
well, how does this work?

00:03:20.810 --> 00:03:22.780 align:middle line:84%
How does Sublist3r
find subdomains

00:03:22.780 --> 00:03:25.360 align:middle line:84%
for a particular domain
that you're targeting?

00:03:25.360 --> 00:03:28.570 align:middle line:84%
And I want to firstly
point out that you're not

00:03:28.570 --> 00:03:31.300 align:middle line:84%
going to get 100%
success because it's

00:03:31.300 --> 00:03:34.390 align:middle line:84%
going to essentially
search or perform searches

00:03:34.390 --> 00:03:37.810 align:middle line:84%
on all of these search engines
to try and see if there is

00:03:37.810 --> 00:03:40.960 align:middle line:84%
a subdomain that might have
been indexed previously

00:03:40.960 --> 00:03:45.880 align:middle line:84%
that could possibly be hidden
now, or might not be active

00:03:45.880 --> 00:03:48.670 align:middle line:84%
but it's still accessible
through the internet.

00:03:48.670 --> 00:03:50.410 align:middle line:84%
And this is something
that you will

00:03:50.410 --> 00:03:52.120 align:middle line:84%
be able to do in
the next video when

00:03:52.120 --> 00:03:53.920 align:middle line:90%
we'll be exploring Google Docs.

00:03:53.920 --> 00:03:56.570 align:middle line:84%
So this is essentially
automating that process,

00:03:56.570 --> 00:03:59.840 align:middle line:84%
but I wanted to cover it before
we actually get to that point.

00:03:59.840 --> 00:04:02.000 align:middle line:84%
So now that we
have it installed,

00:04:02.000 --> 00:04:04.570 align:middle line:84%
you can see that the search
engines we can specify

00:04:04.570 --> 00:04:07.150 align:middle line:90%
are Google, Baidu, et cetera.

00:04:07.150 --> 00:04:10.090 align:middle line:84%
So in this case, let's try
it out with Google and Yahoo

00:04:10.090 --> 00:04:11.410 align:middle line:90%
because they are the ones--

00:04:11.410 --> 00:04:15.850 align:middle line:84%
these are the sites or search
engines that index the best.

00:04:15.850 --> 00:04:18.310 align:middle line:90%
So we can say, Sublist3r.

00:04:18.310 --> 00:04:21.279 align:middle line:90%
Domain is hackersploit.org.

00:04:21.279 --> 00:04:23.350 align:middle line:84%
And in this case,
the search engine

00:04:23.350 --> 00:04:25.300 align:middle line:90%
is going to be Google and Yahoo.

00:04:25.300 --> 00:04:29.140 align:middle line:84%
Now, one thing to note, this
tool makes a lot of requests

00:04:29.140 --> 00:04:32.170 align:middle line:84%
to Google via your IP
address, and Google

00:04:32.170 --> 00:04:34.720 align:middle line:84%
has a rate-limiting
functionality

00:04:34.720 --> 00:04:37.960 align:middle line:84%
that will essentially limit
the amount of requests

00:04:37.960 --> 00:04:38.800 align:middle line:90%
that you can make.

00:04:38.800 --> 00:04:41.470 align:middle line:84%
So that's why in the
previous videos you saw that,

00:04:41.470 --> 00:04:45.310 align:middle line:84%
whenever I open up google.com,
it prompted me to essentially

00:04:45.310 --> 00:04:49.660 align:middle line:84%
enter in a CAPTCHA or to
verify myself because I passed

00:04:49.660 --> 00:04:53.500 align:middle line:84%
the threshold of what Google
considers legitimate traffic

00:04:53.500 --> 00:04:55.810 align:middle line:90%
that's being essentially--

00:04:55.810 --> 00:04:58.750 align:middle line:84%
being performed or facilitated
by a standard user.

00:04:58.750 --> 00:05:02.410 align:middle line:84%
With a tool like this, we're
sending a ton of requests,

00:05:02.410 --> 00:05:04.730 align:middle line:90%
so do be cognizant of that.

00:05:04.730 --> 00:05:07.840 align:middle line:84%
So I'll hit Enter, and
we're going to give this

00:05:07.840 --> 00:05:08.750 align:middle line:90%
a couple of seconds.

00:05:08.750 --> 00:05:11.840 align:middle line:84%
So you can see that Google
is now blocking our requests.

00:05:11.840 --> 00:05:16.850 align:middle line:84%
So in order to bypass this, I
am going to switch to a VPN.

00:05:16.850 --> 00:05:19.510 align:middle line:84%
So I have a third-party
VPN service that

00:05:19.510 --> 00:05:21.130 align:middle line:90%
will allow me to bypass this.

00:05:21.130 --> 00:05:22.870 align:middle line:84%
In your case, you
will not need to go

00:05:22.870 --> 00:05:26.050 align:middle line:84%
through this particular
process, but we can easily

00:05:26.050 --> 00:05:29.840 align:middle line:84%
bypass it by saying, we want
to use Yahoo, for example.

00:05:29.840 --> 00:05:35.140 align:middle line:84%
So we'll just run it with Yahoo
before switching to my VPN.

00:05:35.140 --> 00:05:36.760 align:middle line:84%
As I said, you don't
need to do this

00:05:36.760 --> 00:05:39.610 align:middle line:84%
because this is going to be
your first time running it.

00:05:39.610 --> 00:05:41.890 align:middle line:84%
Again, if you take a look
at the usage instructions,

00:05:41.890 --> 00:05:45.550 align:middle line:84%
it should actually
highlight that.

00:05:45.550 --> 00:05:47.050 align:middle line:84%
And, of course, you
have the ability

00:05:47.050 --> 00:05:51.547 align:middle line:84%
to output your results into a
text file, which is something

00:05:51.547 --> 00:05:53.380 align:middle line:84%
that I recommend that
you do whenever you're

00:05:53.380 --> 00:05:55.310 align:middle line:90%
performing a penetration test.

00:05:55.310 --> 00:05:57.730 align:middle line:84%
So let me just activate
my VPN, and then we

00:05:57.730 --> 00:05:59.860 align:middle line:90%
can try this out again.

00:05:59.860 --> 00:06:02.530 align:middle line:84%
All right, so I've
enabled my VPN, which

00:06:02.530 --> 00:06:04.900 align:middle line:84%
means I'm now in
another location,

00:06:04.900 --> 00:06:07.010 align:middle line:84%
but you didn't
hear that from me.

00:06:07.010 --> 00:06:08.780 align:middle line:90%
So we can perform--

00:06:08.780 --> 00:06:11.950 align:middle line:84%
we can run Sublist3r again
now, and hopefully, Google

00:06:11.950 --> 00:06:13.473 align:middle line:90%
will not block our requests.

00:06:13.473 --> 00:06:14.140 align:middle line:90%
So there we are.

00:06:14.140 --> 00:06:15.800 align:middle line:90%
It looks like it's working now.

00:06:15.800 --> 00:06:17.890 align:middle line:84%
So that's one way
to bypass that.

00:06:17.890 --> 00:06:22.060 align:middle line:84%
You can easily get a free access
to a free VPN for the purposes

00:06:22.060 --> 00:06:23.780 align:middle line:90%
of performing enumeration.

00:06:23.780 --> 00:06:27.140 align:middle line:84%
So this will take a couple
of seconds, and in this case,

00:06:27.140 --> 00:06:30.130 align:middle line:84%
you can see we weren't able
to find any subdomains.

00:06:30.130 --> 00:06:33.070 align:middle line:84%
So we can try and add
other search engines

00:06:33.070 --> 00:06:36.350 align:middle line:90%
into our particular search here.

00:06:36.350 --> 00:06:39.940 align:middle line:84%
So let's see if we can find the
actual search engines that we

00:06:39.940 --> 00:06:42.640 align:middle line:84%
can use here because I don't
think they are highlighted

00:06:42.640 --> 00:06:44.650 align:middle line:90%
explicitly.

00:06:44.650 --> 00:06:45.260 align:middle line:90%
There we are.

00:06:45.260 --> 00:06:52.840 align:middle line:84%
So in this case, it looks
like we don't need to specify.

00:06:52.840 --> 00:06:56.800 align:middle line:84%
We can simply get rid of
the engine option here,

00:06:56.800 --> 00:06:59.780 align:middle line:84%
and this will run the
search on all engines.

00:06:59.780 --> 00:07:00.860 align:middle line:90%
So there we are.

00:07:00.860 --> 00:07:04.000 align:middle line:84%
Looks like VirusTotal is
probably blocking our requests.

00:07:04.000 --> 00:07:05.630 align:middle line:90%
So that's fine.

00:07:05.630 --> 00:07:08.590 align:middle line:84%
We should be able to find
subdomains for hackersploit.org

00:07:08.590 --> 00:07:11.140 align:middle line:90%
because I have set up others.

00:07:11.140 --> 00:07:13.390 align:middle line:84%
And, of course, we should
be able to find the forum

00:07:13.390 --> 00:07:15.440 align:middle line:90%
subdomain.

00:07:15.440 --> 00:07:19.745 align:middle line:84%
So again, we'll just
let this complete.

00:07:19.745 --> 00:07:21.120 align:middle line:84%
There might be an
issue where you

00:07:21.120 --> 00:07:25.930 align:middle line:84%
would need to specify
the actual domain as is,

00:07:25.930 --> 00:07:28.480 align:middle line:90%
but this should work.

00:07:28.480 --> 00:07:30.980 align:middle line:84%
So I'm just going to let this
complete because it's actually

00:07:30.980 --> 00:07:33.900 align:middle line:90%
searching in all--

00:07:33.900 --> 00:07:37.340 align:middle line:84%
it's going to be searching
with all search engines.

00:07:37.340 --> 00:07:39.050 align:middle line:84%
As you can see in
this case, that

00:07:39.050 --> 00:07:40.740 align:middle line:90%
did not look like it worked.

00:07:40.740 --> 00:07:46.190 align:middle line:84%
So if we say
www.hackersploit.org,

00:07:46.190 --> 00:07:47.490 align:middle line:90%
will that change anything?

00:07:47.490 --> 00:07:48.035 align:middle line:90%
Probably not.

00:07:48.035 --> 00:07:55.450 align:middle line:90%


00:07:55.450 --> 00:07:57.490 align:middle line:84%
So for some reason,
it looks like we

00:07:57.490 --> 00:07:59.360 align:middle line:90%
aren't getting any results.

00:07:59.360 --> 00:08:01.690 align:middle line:84%
So what we can do
is we can limit this

00:08:01.690 --> 00:08:04.930 align:middle line:84%
to maybe a site
like DNSdumpster,

00:08:04.930 --> 00:08:08.450 align:middle line:84%
and let's see whether
that produces any results.

00:08:08.450 --> 00:08:10.360 align:middle line:90%
As you can see, that doesn't.

00:08:10.360 --> 00:08:14.320 align:middle line:84%
We were able to identify
the subdomain on Netcraft,

00:08:14.320 --> 00:08:17.450 align:middle line:90%
so let's try and do that now.

00:08:17.450 --> 00:08:19.780 align:middle line:84%
So I'm going to specify the
search engine as Netcraft.

00:08:19.780 --> 00:08:22.330 align:middle line:84%
Is it still not
giving us any results?

00:08:22.330 --> 00:08:23.750 align:middle line:90%
That's perfectly fine.

00:08:23.750 --> 00:08:26.960 align:middle line:84%
We can try this maybe
on zonetransfer.me.

00:08:26.960 --> 00:08:29.502 align:middle line:90%


00:08:29.502 --> 00:08:31.210 align:middle line:84%
And let's see whether
we get any results.

00:08:31.210 --> 00:08:33.830 align:middle line:84%
If not, it's probably
my VPN again.

00:08:33.830 --> 00:08:36.700 align:middle line:84%
I'll probably need
to switch my VPN,

00:08:36.700 --> 00:08:40.240 align:middle line:84%
and we'll see whether that
works again because this can

00:08:40.240 --> 00:08:42.772 align:middle line:90%
be quite tedious of a process.

00:08:42.772 --> 00:08:44.980 align:middle line:84%
But that's why we'll have
the next video, where we'll

00:08:44.980 --> 00:08:49.360 align:middle line:84%
be taking a look at how to
essentially utilize Google Docs

00:08:49.360 --> 00:08:53.350 align:middle line:84%
or Google hacking to identify
information like this,

00:08:53.350 --> 00:08:56.330 align:middle line:84%
through publicly
available information.

00:08:56.330 --> 00:09:00.610 align:middle line:84%
So let's see whether we get any
results for zonetransfer.me.

00:09:00.610 --> 00:09:02.290 align:middle line:84%
I really doubt it
because we weren't

00:09:02.290 --> 00:09:07.600 align:middle line:84%
able to enumerate or identify
any subdomains on DNSdumpster.

00:09:07.600 --> 00:09:10.200 align:middle line:90%


00:09:10.200 --> 00:09:12.000 align:middle line:84%
So in this case,
you can see we only

00:09:12.000 --> 00:09:18.730 align:middle line:84%
found the actual main domain,
which is www.zonetransfer.me,

00:09:18.730 --> 00:09:20.430 align:middle line:84%
which is really
weird because I do

00:09:20.430 --> 00:09:22.740 align:middle line:84%
know that I had
various subdomains

00:09:22.740 --> 00:09:24.570 align:middle line:90%
for hackersploit.org.

00:09:24.570 --> 00:09:27.300 align:middle line:84%
What we can do is try and
do this for maybe a site

00:09:27.300 --> 00:09:30.270 align:middle line:84%
like ine.com, and
let's see whether we

00:09:30.270 --> 00:09:34.260 align:middle line:84%
are able to identify
subdomains like this.

00:09:34.260 --> 00:09:36.090 align:middle line:84%
If not, as I said,
it might be an issue

00:09:36.090 --> 00:09:39.300 align:middle line:84%
with my DNS server and the
fact that most of these sites

00:09:39.300 --> 00:09:41.010 align:middle line:90%
are now blocking my requests.

00:09:41.010 --> 00:09:44.370 align:middle line:84%
So we can also limit
the amount of threads

00:09:44.370 --> 00:09:47.820 align:middle line:84%
we are using to essentially
limit the amount of requests

00:09:47.820 --> 00:09:50.280 align:middle line:84%
we are sending, using the
-t option, which you saw

00:09:50.280 --> 00:09:52.380 align:middle line:84%
me use previously,
but that's really

00:09:52.380 --> 00:09:53.700 align:middle line:90%
for the brute force attack.

00:09:53.700 --> 00:09:56.490 align:middle line:90%


00:09:56.490 --> 00:09:59.330 align:middle line:84%
And let's see whether we get
any subdomains for ine.com,

00:09:59.330 --> 00:10:02.000 align:middle line:84%
because I know that this
tool does indeed work,

00:10:02.000 --> 00:10:05.450 align:middle line:84%
just that in certain cases,
some of these search engines

00:10:05.450 --> 00:10:08.000 align:middle line:84%
or sites might be
blocking your requests.

00:10:08.000 --> 00:10:09.570 align:middle line:90%
So do keep that in mind.

00:10:09.570 --> 00:10:10.350 align:middle line:90%
There we are.

00:10:10.350 --> 00:10:15.260 align:middle line:84%
So for INE, you can see we get
all of these subdomains, which

00:10:15.260 --> 00:10:17.190 align:middle line:90%
you might not have known about.

00:10:17.190 --> 00:10:18.425 align:middle line:90%
So some of these--

00:10:18.425 --> 00:10:20.300 align:middle line:84%
I don't know whether I
should be showing you,

00:10:20.300 --> 00:10:23.060 align:middle line:84%
but again, there really
isn't any harm in this

00:10:23.060 --> 00:10:25.970 align:middle line:84%
because these are all
publicly available subdomains.

00:10:25.970 --> 00:10:28.380 align:middle line:84%
You just need to know
how to search for them.

00:10:28.380 --> 00:10:30.740 align:middle line:84%
So as you can see
here, we have all

00:10:30.740 --> 00:10:33.560 align:middle line:84%
of these subdomains, which
it's enumerated successfully

00:10:33.560 --> 00:10:35.330 align:middle line:90%
for ine.com.

00:10:35.330 --> 00:10:39.200 align:middle line:84%
And that's essentially it with
regards to utilizing Sublist3r.

00:10:39.200 --> 00:10:41.600 align:middle line:84%
As I said, in certain
cases, it might not

00:10:41.600 --> 00:10:44.030 align:middle line:84%
work because you
might have exceeded

00:10:44.030 --> 00:10:48.090 align:middle line:84%
the amount of requests you're
sending, but there you go.

00:10:48.090 --> 00:10:50.450 align:middle line:84%
So that is how to
utilize Sublist3r

00:10:50.450 --> 00:10:53.780 align:middle line:84%
for subdomain enumeration,
more specifically

00:10:53.780 --> 00:10:55.580 align:middle line:90%
passive subdomain enumeration.

00:10:55.580 --> 00:10:58.340 align:middle line:84%
And this is going to conclude
the practical demonstration

00:10:58.340 --> 00:11:00.692 align:middle line:90%
side of this video.

00:11:00.692 --> 00:11:02.150 align:middle line:84%
All right, in the
next video, we're

00:11:02.150 --> 00:11:04.910 align:middle line:84%
going to be taking a look at
how to utilize Google Docs

00:11:04.910 --> 00:11:09.230 align:middle line:84%
or Google dorking to
essentially identify information

00:11:09.230 --> 00:11:11.360 align:middle line:90%
that is pertinent to a target.

00:11:11.360 --> 00:11:13.070 align:middle line:84%
In this case, we're
going to be, again,

00:11:13.070 --> 00:11:15.170 align:middle line:90%
sticking to domain names.

00:11:15.170 --> 00:11:20.390 align:middle line:84%
But we're going to be taking
a look at how to really use

00:11:20.390 --> 00:11:22.350 align:middle line:84%
Google to find what
you're looking for,

00:11:22.350 --> 00:11:26.180 align:middle line:84%
whether it be specific
subdomains, specific sites,

00:11:26.180 --> 00:11:29.060 align:middle line:84%
or specific links,
specific files associated

00:11:29.060 --> 00:11:31.770 align:middle line:84%
with a domain, et
cetera, et cetera.

00:11:31.770 --> 00:11:35.542 align:middle line:84%
So I'll be seeing you
in the next video.

00:11:35.542 --> 00:11:36.042 align:middle line:90%