WEBVTT

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


00:00:10.140 --> 00:00:12.800 align:middle line:84%
Email harvesting
with theHarvester.

00:00:12.800 --> 00:00:14.550 align:middle line:84%
In this video, we're
going to be exploring

00:00:14.550 --> 00:00:18.120 align:middle line:84%
the process of enumerating
emails belonging

00:00:18.120 --> 00:00:21.390 align:middle line:84%
to a specific domain, which
is, of course, your target

00:00:21.390 --> 00:00:24.390 align:middle line:84%
through the use of an opensource
tool called theHarvester.

00:00:24.390 --> 00:00:27.840 align:middle line:84%
And, of course, theHarvester
works quite similarly

00:00:27.840 --> 00:00:32.369 align:middle line:84%
to sublister, where it utilizes
search engines and publicly

00:00:32.369 --> 00:00:36.570 align:middle line:84%
available databases
to identify emails

00:00:36.570 --> 00:00:39.850 align:middle line:84%
that might have been leaked
or that are available online.

00:00:39.850 --> 00:00:43.470 align:middle line:84%
So, again, we're not performing
active information gathering.

00:00:43.470 --> 00:00:44.430 align:middle line:90%
This is all passive.

00:00:44.430 --> 00:00:47.770 align:middle line:84%
And all of this information
is publicly accessible.

00:00:47.770 --> 00:00:51.370 align:middle line:84%
So, again, we're going to be
doing this from Kali Linux.

00:00:51.370 --> 00:00:54.150 align:middle line:84%
And, in my case, I'll be doing
it from my Kali Linux VM.

00:00:54.150 --> 00:00:56.800 align:middle line:84%
And, of course, you can
follow along if you want to.

00:00:56.800 --> 00:01:00.000 align:middle line:84%
So I'm just going to switch
over to my Kali Linux VM really

00:01:00.000 --> 00:01:02.480 align:middle line:90%
quickly.

00:01:02.480 --> 00:01:04.840 align:middle line:84%
All right, so I'm back
on my Kali Linus VM.

00:01:04.840 --> 00:01:08.050 align:middle line:84%
And I'm currently on
theHarvester GitHub repository.

00:01:08.050 --> 00:01:09.370 align:middle line:90%
As I said, it's opensource.

00:01:09.370 --> 00:01:10.900 align:middle line:90%
And it's freely available.

00:01:10.900 --> 00:01:14.860 align:middle line:84%
It really, really is a very
cool, very powerful tool.

00:01:14.860 --> 00:01:17.680 align:middle line:84%
As it says right over
here in the About section,

00:01:17.680 --> 00:01:19.810 align:middle line:84%
theHarvester is a very
simple to use, yet,

00:01:19.810 --> 00:01:22.000 align:middle line:84%
powerful, and
effective tool designed

00:01:22.000 --> 00:01:24.730 align:middle line:84%
to be used in the early
stages of a penetration test

00:01:24.730 --> 00:01:27.550 align:middle line:84%
or red team engagement,
i.e., information

00:01:27.550 --> 00:01:29.710 align:middle line:90%
gathering or reconnaissance.

00:01:29.710 --> 00:01:32.320 align:middle line:84%
You can use it for opensource
intelligence, also known

00:01:32.320 --> 00:01:36.220 align:middle line:84%
as OSINT, gathering to
help determine a company's

00:01:36.220 --> 00:01:38.680 align:middle line:84%
external threat landscape
on the internet.

00:01:38.680 --> 00:01:42.940 align:middle line:84%
The tool gathers emails, names,
subdomains, IPs, and URLs

00:01:42.940 --> 00:01:44.980 align:middle line:84%
using multiple
public data sources

00:01:44.980 --> 00:01:46.850 align:middle line:90%
that include the following.

00:01:46.850 --> 00:01:50.530 align:middle line:84%
So it uses the Anubis
database, Baidu--

00:01:50.530 --> 00:01:52.810 align:middle line:84%
Baidu is a Chinese
search engine--

00:01:52.810 --> 00:01:55.180 align:middle line:90%
Bing, Bing API, Censys.

00:01:55.180 --> 00:01:57.730 align:middle line:84%
You do require an API
key to use Censys.

00:01:57.730 --> 00:02:00.500 align:middle line:84%
Although, that's
really not required.

00:02:00.500 --> 00:02:05.110 align:middle line:84%
It also utilizes crtsh, which is
the Komodo certificate search,

00:02:05.110 --> 00:02:07.060 align:middle line:90%
DNS dumpster.

00:02:07.060 --> 00:02:08.860 align:middle line:84%
And, in the case
of email addresses,

00:02:08.860 --> 00:02:10.900 align:middle line:84%
it'll search on--
it'll essentially

00:02:10.900 --> 00:02:13.960 align:middle line:84%
search for exposed
email addresses on sites

00:02:13.960 --> 00:02:18.100 align:middle line:84%
like LinkedIn, so your
typical social media

00:02:18.100 --> 00:02:19.400 align:middle line:90%
or social networking sites.

00:02:19.400 --> 00:02:21.890 align:middle line:84%
So LinkedIn is one
that is very important.

00:02:21.890 --> 00:02:22.910 align:middle line:90%
Why is that important?

00:02:22.910 --> 00:02:28.570 align:middle line:84%
Well, if we are searching for
employee email addresses that

00:02:28.570 --> 00:02:32.080 align:middle line:84%
belong to a particular
domain, that information

00:02:32.080 --> 00:02:36.220 align:middle line:84%
is really only linked
in one area, typically.

00:02:36.220 --> 00:02:39.340 align:middle line:84%
And that is LinkedIn
because individuals usually

00:02:39.340 --> 00:02:42.070 align:middle line:84%
post or specify
what company they

00:02:42.070 --> 00:02:44.830 align:middle line:90%
are working for on LinkedIn.

00:02:44.830 --> 00:02:48.040 align:middle line:84%
And, of course, there's a
couple of other search engines

00:02:48.040 --> 00:02:49.780 align:middle line:90%
and databases that it uses.

00:02:49.780 --> 00:02:53.410 align:middle line:84%
It also utilizes sublister for
subdomain enumeration, which

00:02:53.410 --> 00:02:56.530 align:middle line:84%
we've already explored,
Twitter, VirusTotal, Yahoo,

00:02:56.530 --> 00:03:01.420 align:middle line:84%
and, of course, Google, and
a plethora of other search

00:03:01.420 --> 00:03:04.600 align:middle line:84%
engines and public
databases that

00:03:04.600 --> 00:03:08.200 align:middle line:84%
contain data that
could be potentially

00:03:08.200 --> 00:03:09.440 align:middle line:90%
useful in this case.

00:03:09.440 --> 00:03:13.630 align:middle line:84%
So theHarvester comes
prepackaged with Kali Linux.

00:03:13.630 --> 00:03:16.000 align:middle line:84%
Although, you can install
it, if you want to,

00:03:16.000 --> 00:03:18.760 align:middle line:90%
or install the latest version.

00:03:18.760 --> 00:03:21.190 align:middle line:84%
As I said, one thing that
I wanted to point out

00:03:21.190 --> 00:03:27.580 align:middle line:84%
is the functionality
that theHarvester offers

00:03:27.580 --> 00:03:30.760 align:middle line:84%
is broken down into passive
info gathering and, of course,

00:03:30.760 --> 00:03:31.480 align:middle line:90%
active.

00:03:31.480 --> 00:03:33.940 align:middle line:84%
We are primarily
focused on passive.

00:03:33.940 --> 00:03:36.268 align:middle line:84%
So to use the tool,
it's fairly simple.

00:03:36.268 --> 00:03:37.810 align:middle line:84%
I'm just going to
open up a terminal.

00:03:37.810 --> 00:03:40.940 align:middle line:90%
And we can type in theHarvester.

00:03:40.940 --> 00:03:41.780 align:middle line:90%
There we are.

00:03:41.780 --> 00:03:44.070 align:middle line:90%
And using it is fairly simple.

00:03:44.070 --> 00:03:47.960 align:middle line:84%
We can specify the domain
name and then the source.

00:03:47.960 --> 00:03:50.720 align:middle line:84%
The source allows us to
specify the search engine.

00:03:50.720 --> 00:03:53.420 align:middle line:90%
So let's perform a few checks.

00:03:53.420 --> 00:03:58.090 align:middle line:84%
So I'm going to say
theHarvester and the domain

00:03:58.090 --> 00:03:59.843 align:middle line:90%
hackersploit.org.

00:03:59.843 --> 00:04:01.760 align:middle line:84%
And let's see I'm looking
for email addresses.

00:04:01.760 --> 00:04:03.340 align:middle line:84%
So I can say limit
this to Google.

00:04:03.340 --> 00:04:07.360 align:middle line:90%
And we can say LinkedIn.

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

00:04:09.190 --> 00:04:11.900 align:middle line:84%
It's going to search on
Google and on LinkedIn.

00:04:11.900 --> 00:04:15.740 align:middle line:84%
And it's going to bring
back names, email addresses,

00:04:15.740 --> 00:04:19.390 align:middle line:84%
and subdomains, if
it does find them.

00:04:19.390 --> 00:04:22.120 align:middle line:84%
As you can see, it's utilizing
the sublist of functionality

00:04:22.120 --> 00:04:25.610 align:middle line:84%
here because it's incorporated
into this particular script.

00:04:25.610 --> 00:04:28.360 align:middle line:84%
So we'll give this
a couple of seconds.

00:04:28.360 --> 00:04:32.560 align:middle line:84%
I have switched, or I am
using a VPN server or a VPN,

00:04:32.560 --> 00:04:34.990 align:middle line:84%
if you will, primarily
because I've been running

00:04:34.990 --> 00:04:36.970 align:middle line:90%
a lot of Google searches today.

00:04:36.970 --> 00:04:40.960 align:middle line:84%
And Google is going to get
really suspicious if I continue

00:04:40.960 --> 00:04:44.050 align:middle line:84%
performing quite a few
Google searches as we

00:04:44.050 --> 00:04:45.730 align:middle line:90%
did in the previous video.

00:04:45.730 --> 00:04:47.267 align:middle line:84%
It's now going to
search LinkedIn.

00:04:47.267 --> 00:04:49.600 align:middle line:84%
And let's see whether it
brings anything interesting up.

00:04:49.600 --> 00:04:50.950 align:middle line:90%
Now, remember I'm searching.

00:04:50.950 --> 00:04:52.420 align:middle line:90%
My target is a domain name.

00:04:52.420 --> 00:04:54.640 align:middle line:84%
I can also specify a
company name, which

00:04:54.640 --> 00:04:56.300 align:middle line:90%
I'll show you in a second.

00:04:56.300 --> 00:04:59.643 align:middle line:84%
So I'm just going to wait
for this to complete.

00:04:59.643 --> 00:05:01.560 align:middle line:84%
All right, so you can
see the harvest is done.

00:05:01.560 --> 00:05:06.090 align:middle line:84%
And it tells us that no
users were found on LinkedIn,

00:05:06.090 --> 00:05:08.620 align:middle line:84%
no IPs found, no emails
found, no hosts found.

00:05:08.620 --> 00:05:10.290 align:middle line:84%
Now, that could be
down to the fact

00:05:10.290 --> 00:05:12.840 align:middle line:84%
that we're specifying
our target as a domain

00:05:12.840 --> 00:05:15.930 align:middle line:84%
and also because we limited
it to two search engines

00:05:15.930 --> 00:05:18.820 align:middle line:84%
or, really, a search engine
and a social network.

00:05:18.820 --> 00:05:23.640 align:middle line:84%
So what I can do is I can just
get rid of the domain option.

00:05:23.640 --> 00:05:27.790 align:middle line:84%
And we can specify the
company name as the target.

00:05:27.790 --> 00:05:32.780 align:middle line:84%
And, in this case, I believe
we actually can specify it.

00:05:32.780 --> 00:05:34.740 align:middle line:90%
Can we specify that?

00:05:34.740 --> 00:05:37.670 align:middle line:84%
I believe we still need to
specify this as the domain.

00:05:37.670 --> 00:05:38.838 align:middle line:90%
Let's see if that works out.

00:05:38.838 --> 00:05:39.380 align:middle line:90%
There we are.

00:05:39.380 --> 00:05:41.360 align:middle line:90%
So the target is hackersploit.

00:05:41.360 --> 00:05:42.980 align:middle line:84%
It's now going to
search on Google

00:05:42.980 --> 00:05:45.030 align:middle line:84%
and then, of
course, on LinkedIn.

00:05:45.030 --> 00:05:47.240 align:middle line:84%
And I'll also get rid
of the search engine

00:05:47.240 --> 00:05:51.380 align:middle line:84%
option or the specification,
so that we can run it on all.

00:05:51.380 --> 00:05:53.443 align:middle line:84%
And, of course, in the
case of hackersploit,

00:05:53.443 --> 00:05:54.860 align:middle line:84%
it looks like I've
done a good job

00:05:54.860 --> 00:05:59.570 align:middle line:84%
with sort of obfuscating
subdomains, names,

00:05:59.570 --> 00:06:00.710 align:middle line:90%
and, of course, emails.

00:06:00.710 --> 00:06:03.920 align:middle line:84%
But that's something
that we will actually

00:06:03.920 --> 00:06:07.070 align:middle line:90%
see at the end of this.

00:06:07.070 --> 00:06:09.250 align:middle line:90%
So LinkedIn should be done.

00:06:09.250 --> 00:06:11.018 align:middle line:90%
And we should be able to see.

00:06:11.018 --> 00:06:11.560 align:middle line:90%
there we are.

00:06:11.560 --> 00:06:17.900 align:middle line:84%
So nothing with regards to
hackersploit as a company name.

00:06:17.900 --> 00:06:21.200 align:middle line:90%
So I can say hackersploit.org.

00:06:21.200 --> 00:06:23.570 align:middle line:84%
And, when I don't
specify a search engine,

00:06:23.570 --> 00:06:26.490 align:middle line:84%
you can see that
that's what it--

00:06:26.490 --> 00:06:29.170 align:middle line:84%
if I don't specify a source,
that's what it tells me.

00:06:29.170 --> 00:06:35.880 align:middle line:84%
So we can say Google,
LinkedIn, Yahoo.

00:06:35.880 --> 00:06:39.390 align:middle line:84%
We can also specify
DNS dumpster.

00:06:39.390 --> 00:06:42.450 align:middle line:84%
Another good site that we can--
another good source, rather,

00:06:42.450 --> 00:06:45.900 align:middle line:84%
that we can use is
probably one that I

00:06:45.900 --> 00:06:50.385 align:middle line:84%
know works really well is, of
course, DuckDuckGo and CRTSH.

00:06:50.385 --> 00:06:55.370 align:middle line:90%


00:06:55.370 --> 00:06:55.870 align:middle line:90%
CRTSH.

00:06:55.870 --> 00:06:59.000 align:middle line:90%


00:06:59.000 --> 00:07:01.220 align:middle line:90%
Let's try hacker target.

00:07:01.220 --> 00:07:05.310 align:middle line:84%
That's not really required
at this point in time.

00:07:05.310 --> 00:07:08.090 align:middle line:84%
We can also try
project discovery.

00:07:08.090 --> 00:07:12.530 align:middle line:84%
I think that also
requires an API key.

00:07:12.530 --> 00:07:13.880 align:middle line:90%
We can try rapid DNS.

00:07:13.880 --> 00:07:16.740 align:middle line:90%


00:07:16.740 --> 00:07:20.490 align:middle line:84%
Remember, the objective
of this particular video

00:07:20.490 --> 00:07:22.200 align:middle line:90%
is to enumerate emails.

00:07:22.200 --> 00:07:23.280 align:middle line:90%
But let's just run this.

00:07:23.280 --> 00:07:27.040 align:middle line:84%
And let's see what
this brings up.

00:07:27.040 --> 00:07:29.708 align:middle line:90%
So I brought up rapid DNS.

00:07:29.708 --> 00:07:30.250 align:middle line:90%
There we are.

00:07:30.250 --> 00:07:34.750 align:middle line:84%
OK, so let's see whether
we get any results here.

00:07:34.750 --> 00:07:36.310 align:middle line:90%
OK, now we're talking.

00:07:36.310 --> 00:07:38.830 align:middle line:84%
So it looks like,
in this case, we

00:07:38.830 --> 00:07:41.050 align:middle line:90%
were not able to find any IPs.

00:07:41.050 --> 00:07:41.950 align:middle line:90%
But we did.

00:07:41.950 --> 00:07:43.180 align:middle line:90%
But no emails found.

00:07:43.180 --> 00:07:44.420 align:middle line:90%
But we found hosts.

00:07:44.420 --> 00:07:46.180 align:middle line:90%
So we found subdomains.

00:07:46.180 --> 00:07:47.830 align:middle line:84%
So this time around,
it looked like it

00:07:47.830 --> 00:07:49.210 align:middle line:90%
worked for hackersploit.org.

00:07:49.210 --> 00:07:52.690 align:middle line:84%
So we have apps.community,
cloud.hackersploit.org,

00:07:52.690 --> 00:07:56.080 align:middle line:84%
community.hackersploit.org,
demo, forum, et cetera.

00:07:56.080 --> 00:07:59.210 align:middle line:84%
So, again, that's really not
what we're interested in.

00:07:59.210 --> 00:08:03.130 align:middle line:84%
So we're going to now switch
this over to another domain.

00:08:03.130 --> 00:08:07.960 align:middle line:84%
And, in this case, let's
try zonetransfer.me.

00:08:07.960 --> 00:08:08.710 align:middle line:90%
All right?

00:08:08.710 --> 00:08:13.850 align:middle line:84%
And let's actually see
what this looks like.

00:08:13.850 --> 00:08:20.110 align:middle line:84%
So let's see whether we're able
to find any emails associated

00:08:20.110 --> 00:08:24.420 align:middle line:84%
with the domain
zonetransfer.met.

00:08:24.420 --> 00:08:26.600 align:middle line:84%
All right, so it looks like
we have much better luck

00:08:26.600 --> 00:08:27.890 align:middle line:90%
with zonetransfer.me.

00:08:27.890 --> 00:08:28.820 align:middle line:90%
No IPs found.

00:08:28.820 --> 00:08:32.419 align:middle line:84%
But we did find an email,
so pippa@zonetransfer.me.

00:08:32.419 --> 00:08:34.580 align:middle line:84%
Now, as I said, the
zonetransfer.me website

00:08:34.580 --> 00:08:38.990 align:middle line:84%
was essentially set
up to teach students

00:08:38.990 --> 00:08:41.600 align:middle line:84%
how to essentially interact
with the DNS server

00:08:41.600 --> 00:08:45.650 align:middle line:84%
and perform zone transfers,
which we will be exploring.

00:08:45.650 --> 00:08:47.000 align:middle line:90%
But we do get an email.

00:08:47.000 --> 00:08:49.740 align:middle line:84%
Now, why is this
information important?

00:08:49.740 --> 00:08:53.240 align:middle line:84%
Well, if you remember and go
back to the introductory video

00:08:53.240 --> 00:08:56.690 align:middle line:84%
to this course, I mentioned
in a simple scenario

00:08:56.690 --> 00:08:59.300 align:middle line:84%
that, when we find
emails pertinent

00:08:59.300 --> 00:09:02.480 align:middle line:84%
to a particular target, the
target could be a company.

00:09:02.480 --> 00:09:04.220 align:middle line:90%
It could be a domain.

00:09:04.220 --> 00:09:07.820 align:middle line:84%
Then an attacker could use
that to send a phishing email.

00:09:07.820 --> 00:09:10.460 align:middle line:84%
Or they could use
it to send an email

00:09:10.460 --> 00:09:14.840 align:middle line:84%
with a malicious attachment
that, when opened and executed

00:09:14.840 --> 00:09:20.510 align:middle line:84%
on a target system, could
provide us with initial access.

00:09:20.510 --> 00:09:22.400 align:middle line:84%
So this is very, very
important information.

00:09:22.400 --> 00:09:27.530 align:middle line:84%
Under the host, you can see we
found a couple of subdomains.

00:09:27.530 --> 00:09:30.770 align:middle line:84%
So you can see we have
contact, DC office,

00:09:30.770 --> 00:09:32.900 align:middle line:90%
and, of course, INT NS1.

00:09:32.900 --> 00:09:35.540 align:middle line:90%
So very good success there.

00:09:35.540 --> 00:09:38.735 align:middle line:84%
The final site I'm going to try
it on is, of course, INE.com.

00:09:38.735 --> 00:09:41.360 align:middle line:84%
I expect a lot of
success with this one.

00:09:41.360 --> 00:09:44.420 align:middle line:84%
But we can actually
see what comes up.

00:09:44.420 --> 00:09:47.000 align:middle line:84%
And, by the way, all
of this information

00:09:47.000 --> 00:09:50.490 align:middle line:84%
that we're gathering will
tie into the next video.

00:09:50.490 --> 00:09:53.270 align:middle line:84%
The next video will be taking
a look at leaked password

00:09:53.270 --> 00:09:57.680 align:middle line:84%
databases and how we can
potentially find passwords

00:09:57.680 --> 00:10:01.730 align:middle line:84%
for specific emails or passwords
linked to specific emails

00:10:01.730 --> 00:10:05.390 align:middle line:84%
that can then be used to
perform a password spray attack.

00:10:05.390 --> 00:10:07.160 align:middle line:90%
A password spray attack--

00:10:07.160 --> 00:10:10.490 align:middle line:84%
while this is actually
performing the actual search--

00:10:10.490 --> 00:10:12.800 align:middle line:84%
a password spray
attack is when you

00:10:12.800 --> 00:10:17.900 align:middle line:84%
identify a password for a
particular email for one site.

00:10:17.900 --> 00:10:21.170 align:middle line:84%
So let's say I have
found a password

00:10:21.170 --> 00:10:24.020 align:middle line:84%
for a particular email,
let's say, for Facebook.com.

00:10:24.020 --> 00:10:28.160 align:middle line:84%
Well, many users tend to reuse
passwords for different sites.

00:10:28.160 --> 00:10:29.900 align:middle line:84%
So I can put-- that's
essentially what

00:10:29.900 --> 00:10:31.100 align:middle line:90%
a password spray attack is.

00:10:31.100 --> 00:10:33.860 align:middle line:84%
It's where I use the
password I got from one site,

00:10:33.860 --> 00:10:36.950 align:middle line:84%
and I try and authenticate
with other services

00:10:36.950 --> 00:10:39.770 align:middle line:84%
like maybe Gmail or
maybe QuickBooks,

00:10:39.770 --> 00:10:41.990 align:middle line:84%
for example, as I
have done before

00:10:41.990 --> 00:10:43.250 align:middle line:90%
with previous engagements.

00:10:43.250 --> 00:10:45.510 align:middle line:84%
And it has actually
worked quite well.

00:10:45.510 --> 00:10:49.430 align:middle line:84%
So this, all of the
emails we find here

00:10:49.430 --> 00:10:53.630 align:middle line:84%
or that you typically find when
performing email harvesting

00:10:53.630 --> 00:10:56.398 align:middle line:84%
will tie in to the next
video, which is, again,

00:10:56.398 --> 00:10:57.690 align:middle line:90%
going to be really interesting.

00:10:57.690 --> 00:10:59.600 align:middle line:84%
We'll actually see what
we're able to find.

00:10:59.600 --> 00:11:03.150 align:middle line:84%
Now, you might be thinking
to yourself, well, Alexis,

00:11:03.150 --> 00:11:04.700 align:middle line:84%
you're showing us
all of this stuff.

00:11:04.700 --> 00:11:06.110 align:middle line:90%
Isn't any of this illegal?

00:11:06.110 --> 00:11:09.830 align:middle line:84%
Well, as I said, all of this
is available on the internet.

00:11:09.830 --> 00:11:13.610 align:middle line:84%
Now, it's what we do with this
information that might become

00:11:13.610 --> 00:11:16.670 align:middle line:84%
or might get into the
territory of being illegal,

00:11:16.670 --> 00:11:20.990 align:middle line:84%
which is why I have separated
the activity that you typically

00:11:20.990 --> 00:11:24.170 align:middle line:84%
perform in passive
information gathering

00:11:24.170 --> 00:11:26.870 align:middle line:84%
from the actual active
information gathering, which

00:11:26.870 --> 00:11:29.030 align:middle line:90%
does require authorization.

00:11:29.030 --> 00:11:30.920 align:middle line:84%
So, again, as a
penetration tester,

00:11:30.920 --> 00:11:33.860 align:middle line:84%
ensure that you abide
by a code of ethics

00:11:33.860 --> 00:11:37.430 align:middle line:90%
when it comes down to public--

00:11:37.430 --> 00:11:40.370 align:middle line:84%
to sites that are
available on the internet.

00:11:40.370 --> 00:11:43.010 align:middle line:84%
So you can see these are
all the subdomains for INE.

00:11:43.010 --> 00:11:46.010 align:middle line:84%
No emails were found, which
is very, very interesting.

00:11:46.010 --> 00:11:48.770 align:middle line:84%
But I guess we can add a
couple of more sources.

00:11:48.770 --> 00:11:50.930 align:middle line:84%
But you get the
idea. theHarvester

00:11:50.930 --> 00:11:52.670 align:middle line:84%
is extremely
comprehensive because it

00:11:52.670 --> 00:11:55.400 align:middle line:84%
not only performs
email harvesting

00:11:55.400 --> 00:11:57.110 align:middle line:90%
but also subdomain enumeration.

00:11:57.110 --> 00:12:00.290 align:middle line:84%
And you can probably
fine tune your searches

00:12:00.290 --> 00:12:02.570 align:middle line:84%
and limit them to
particular sources.

00:12:02.570 --> 00:12:06.020 align:middle line:84%
One really cool one that I
would recommend checking out

00:12:06.020 --> 00:12:08.330 align:middle line:90%
is the Spyse integration.

00:12:08.330 --> 00:12:09.710 align:middle line:90%
This requires an API key.

00:12:09.710 --> 00:12:12.980 align:middle line:84%
The Spyse search engine
is a search engine

00:12:12.980 --> 00:12:17.510 align:middle line:84%
built for penetration testers
for essentially performing

00:12:17.510 --> 00:12:21.440 align:middle line:84%
passive reconnaissance of a
target like a website or an IP

00:12:21.440 --> 00:12:22.370 align:middle line:90%
address.

00:12:22.370 --> 00:12:24.275 align:middle line:84%
But it does require
a subscription, which

00:12:24.275 --> 00:12:25.400 align:middle line:90%
is why I'm not covering it.

00:12:25.400 --> 00:12:27.980 align:middle line:84%
But if you are getting
into penetration testing,

00:12:27.980 --> 00:12:34.640 align:middle line:84%
do check out Spyse, as it
really is very, very useful.

00:12:34.640 --> 00:12:36.620 align:middle line:84%
Yeah, OK, so I
think that's going

00:12:36.620 --> 00:12:38.670 align:middle line:84%
to conclude the
practical demonstration

00:12:38.670 --> 00:12:41.590 align:middle line:90%
side of this video.

00:12:41.590 --> 00:12:43.090 align:middle line:84%
In the next video,
we're going to be

00:12:43.090 --> 00:12:46.180 align:middle line:84%
taking a look at leaked
password databases that

00:12:46.180 --> 00:12:47.980 align:middle line:84%
are freely available
online that can

00:12:47.980 --> 00:12:51.280 align:middle line:84%
be used to identify
whether a specific email

00:12:51.280 --> 00:12:55.060 align:middle line:84%
or a specific user's password
has been leaked previously

00:12:55.060 --> 00:12:56.320 align:middle line:90%
during a data breach.

00:12:56.320 --> 00:13:00.120 align:middle line:84%
So I'll be seeing you
in the next video.

00:13:00.120 --> 00:13:01.000 align:middle line:90%