WEBVTT

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


00:00:04.810 --> 00:00:08.177 align:middle line:90%
[MUSIC PLAYING]

00:00:08.177 --> 00:00:10.110 align:middle line:90%


00:00:10.110 --> 00:00:12.462 align:middle line:84%
Website Footprinting
with Netcraft.

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

00:00:14.670 --> 00:00:18.480 align:middle line:84%
to utilize Netcraft to,
essentially, enumerate

00:00:18.480 --> 00:00:22.440 align:middle line:84%
as much information as possible,
passively, from a website.

00:00:22.440 --> 00:00:25.740 align:middle line:84%
So this will give us,
Netcraft, essentially,

00:00:25.740 --> 00:00:27.090 align:middle line:90%
correlates all information.

00:00:27.090 --> 00:00:29.280 align:middle line:90%
Like the "who is" information.

00:00:29.280 --> 00:00:32.130 align:middle line:84%
It'll give you information
regarding the SSL or TLS

00:00:32.130 --> 00:00:33.540 align:middle line:90%
certificate on the site.

00:00:33.540 --> 00:00:36.210 align:middle line:84%
What web technologies are
being used on the site.

00:00:36.210 --> 00:00:38.230 align:middle line:84%
The name servers,
all that good stuff.

00:00:38.230 --> 00:00:41.837 align:middle line:84%
So I'm going to be doing
this on my Kali Linux VM

00:00:41.837 --> 00:00:43.920 align:middle line:84%
because we are going to
be accessing the internet.

00:00:43.920 --> 00:00:45.810 align:middle line:84%
So you can follow
along with this.

00:00:45.810 --> 00:00:47.910 align:middle line:84%
We're going to be doing
this on my website.

00:00:47.910 --> 00:00:50.100 align:middle line:84%
Again, this is all
passive, so it really

00:00:50.100 --> 00:00:53.340 align:middle line:84%
doesn't make a difference to
me because this information is

00:00:53.340 --> 00:00:55.840 align:middle line:90%
already publicly available.

00:00:55.840 --> 00:01:00.680 align:middle line:84%
So I'll just switch over
to my Kali Linux VM.

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

00:01:03.410 --> 00:01:06.120 align:middle line:84%
And I'm currently on the
Netcraft website, here.

00:01:06.120 --> 00:01:09.830 align:middle line:84%
So Netcraft is a fairly
simple service to understand.

00:01:09.830 --> 00:01:13.040 align:middle line:84%
It is, essentially, used
to gather information

00:01:13.040 --> 00:01:15.020 align:middle line:90%
about a target domain.

00:01:15.020 --> 00:01:17.960 align:middle line:84%
And when you're talking
about the domain itself,

00:01:17.960 --> 00:01:20.540 align:middle line:84%
it gives you information
regarding the registrar,

00:01:20.540 --> 00:01:25.100 align:middle line:84%
the emails, the operating system
or the web technologies that

00:01:25.100 --> 00:01:26.840 align:middle line:84%
are running on the
website, et cetera.

00:01:26.840 --> 00:01:29.120 align:middle line:84%
So it's essentially
collating all

00:01:29.120 --> 00:01:32.510 align:middle line:84%
of the information we were
able to obtain manually

00:01:32.510 --> 00:01:34.950 align:middle line:84%
in the previous videos,
which is really, really cool,

00:01:34.950 --> 00:01:37.290 align:middle line:84%
which is, again, why I
wanted to showcase this.

00:01:37.290 --> 00:01:41.550 align:middle line:84%
So to, essentially, perform
a check on a website,

00:01:41.550 --> 00:01:45.140 align:middle line:84%
just click on Services
and Internet Data Mining

00:01:45.140 --> 00:01:47.090 align:middle line:90%
at the bottom.

00:01:47.090 --> 00:01:49.760 align:middle line:84%
You should be able
to see a box, here.

00:01:49.760 --> 00:01:53.640 align:middle line:84%
An input box that allows you to
check what a site is running.

00:01:53.640 --> 00:01:56.930 align:middle line:84%
So it's going to use results
from Netcrafts internet

00:01:56.930 --> 00:02:01.040 align:middle line:84%
data mining database to
find out the technologies

00:02:01.040 --> 00:02:02.950 align:middle line:84%
and the infrastructure
of any site.

00:02:02.950 --> 00:02:05.120 align:middle line:84%
So you can type in
the address, here.

00:02:05.120 --> 00:02:08.930 align:middle line:84%
In my case, I've already run
a check on hackersploit.org,

00:02:08.930 --> 00:02:10.877 align:middle line:84%
so I'm just going to
close that up here.

00:02:10.877 --> 00:02:12.210 align:middle line:90%
So let's go through the results.

00:02:12.210 --> 00:02:14.418 align:middle line:84%
So it's going to sort it
out into various categories.

00:02:14.418 --> 00:02:19.080 align:middle line:84%
We have background, network,
SSL TLS, and then, of course,

00:02:19.080 --> 00:02:20.630 align:middle line:84%
it'll perform a few
vulnerabilities,

00:02:20.630 --> 00:02:23.930 align:middle line:90%
with regards to SSL and TLS.

00:02:23.930 --> 00:02:27.140 align:middle line:84%
It'll provide you
with hosting history.

00:02:27.140 --> 00:02:30.230 align:middle line:84%
Let's see, we have web
trackers, the site technology,

00:02:30.230 --> 00:02:31.760 align:middle line:90%
which is very, very important.

00:02:31.760 --> 00:02:33.750 align:middle line:90%
And yeah, that's pretty much it.

00:02:33.750 --> 00:02:36.410 align:middle line:84%
So as I've said, the
information That's

00:02:36.410 --> 00:02:38.780 align:middle line:84%
important from the perspective
of a penetration test

00:02:38.780 --> 00:02:40.610 align:middle line:84%
is going to be the
network information,

00:02:40.610 --> 00:02:43.110 align:middle line:84%
but we can take a look
at the background first.

00:02:43.110 --> 00:02:45.650 align:middle line:84%
So this will give you the
site title, the website rank,

00:02:45.650 --> 00:02:48.650 align:middle line:84%
the description, when this
website was first seen

00:02:48.650 --> 00:02:52.370 align:middle line:84%
and the primary language,
which again, makes sense.

00:02:52.370 --> 00:02:54.590 align:middle line:84%
It'll then provide you
with information regarding

00:02:54.590 --> 00:02:56.310 align:middle line:90%
the actual domain IP address.

00:02:56.310 --> 00:02:59.660 align:middle line:84%
So you can see the name
server is Cloudflare.

00:02:59.660 --> 00:03:01.520 align:middle line:84%
The name server
organization again,

00:03:01.520 --> 00:03:03.350 align:middle line:84%
is Cloudflare, which,
again, makes sense.

00:03:03.350 --> 00:03:05.600 align:middle line:84%
Now, if you had not
performed the previous checks

00:03:05.600 --> 00:03:10.040 align:middle line:84%
with the WHOIS lookups
and the host commands,

00:03:10.040 --> 00:03:15.140 align:middle line:84%
then this could tell you
what domain registrar

00:03:15.140 --> 00:03:17.910 align:middle line:84%
was used to register
this particular domain.

00:03:17.910 --> 00:03:20.503 align:middle line:84%
And then, of course, you have
the IP address of the website.

00:03:20.503 --> 00:03:21.920 align:middle line:84%
Now, of course,
in this case, it's

00:03:21.920 --> 00:03:25.220 align:middle line:84%
going through Cloudflare, which
means that this is not really

00:03:25.220 --> 00:03:27.350 align:middle line:84%
the IP address of the
web server that is

00:03:27.350 --> 00:03:31.675 align:middle line:84%
being protected by Cloudflare,
which is really, really cool.

00:03:31.675 --> 00:03:33.050 align:middle line:84%
And then, of
course, it gives you

00:03:33.050 --> 00:03:35.450 align:middle line:84%
the actual top level
domain, which in this case,

00:03:35.450 --> 00:03:39.230 align:middle line:90%
is the org DLD.

00:03:39.230 --> 00:03:42.350 align:middle line:84%
And then it'll tell you
whether the site has any DNS

00:03:42.350 --> 00:03:46.100 align:middle line:90%
security extensions enabled.

00:03:46.100 --> 00:03:48.590 align:middle line:84%
fOR the IP address, it will
give you the IP delegation.

00:03:48.590 --> 00:03:50.810 align:middle line:84%
So this is the primary
IP, which as we

00:03:50.810 --> 00:03:54.140 align:middle line:84%
know from the previous
videos, belongs to Cloudflare,

00:03:54.140 --> 00:03:56.130 align:middle line:90%
as it, again, highlights here.

00:03:56.130 --> 00:03:59.420 align:middle line:84%
So I'll tell you the
name right over here

00:03:59.420 --> 00:04:01.760 align:middle line:90%
of each of the IP blocks.

00:04:01.760 --> 00:04:04.620 align:middle line:84%
And in specific,
this particular IP,

00:04:04.620 --> 00:04:06.680 align:middle line:84%
which is owned by
Cloudflare and it

00:04:06.680 --> 00:04:10.280 align:middle line:84%
does that for IPv6, you
then have the SSL and TLS

00:04:10.280 --> 00:04:11.480 align:middle line:90%
certificate information.

00:04:11.480 --> 00:04:13.940 align:middle line:84%
This is very important
because it can, essentially,

00:04:13.940 --> 00:04:15.980 align:middle line:84%
provide you with
information regarding when

00:04:15.980 --> 00:04:19.700 align:middle line:90%
an SSL certificate expires.

00:04:19.700 --> 00:04:21.740 align:middle line:84%
It'll also tell you
who it was issued by.

00:04:21.740 --> 00:04:23.750 align:middle line:90%
In this case, it is Cloudflare.

00:04:23.750 --> 00:04:27.650 align:middle line:84%
And in this case, it
tells us that it expires

00:04:27.650 --> 00:04:31.700 align:middle line:90%
on the tenth of June, 2022.

00:04:31.700 --> 00:04:36.140 align:middle line:84%
So 11 months, four
weeks, one day.

00:04:36.140 --> 00:04:38.840 align:middle line:84%
That's really weird,
because it actually-- yeah,

00:04:38.840 --> 00:04:43.790 align:middle line:84%
so this is valid from
the 11th of June,

00:04:43.790 --> 00:04:49.640 align:middle line:84%
2021 to this year
on June the 10th.

00:04:49.640 --> 00:04:51.120 align:middle line:90%
So there we are.

00:04:51.120 --> 00:04:54.827 align:middle line:84%
That's the SSL DLS
certificate information.

00:04:54.827 --> 00:04:56.660 align:middle line:84%
One thing that's really
important, as I said

00:04:56.660 --> 00:04:58.560 align:middle line:84%
is, of course, the
validity period.

00:04:58.560 --> 00:05:00.470 align:middle line:84%
And, of course,
who is issued it.

00:05:00.470 --> 00:05:02.570 align:middle line:84%
And, of course, the
issuer country, there.

00:05:02.570 --> 00:05:05.390 align:middle line:84%
In this case, it's still
valid, which makes sense.

00:05:05.390 --> 00:05:08.510 align:middle line:84%
And then, of course, the
Certificate of Transparency.

00:05:08.510 --> 00:05:11.300 align:middle line:84%
In this case, you can
see that it provides you

00:05:11.300 --> 00:05:14.530 align:middle line:84%
with information
regarding that there.

00:05:14.530 --> 00:05:22.630 align:middle line:84%
And then if this site is
vulnerable to any SSL TLS

00:05:22.630 --> 00:05:25.880 align:middle line:84%
related vulnerabilities, it'll
tell you that right over here.

00:05:25.880 --> 00:05:29.290 align:middle line:84%
So it's not vulnerable
to SSL version 3 poodle,

00:05:29.290 --> 00:05:30.580 align:middle line:90%
or the poodle exploit.

00:05:30.580 --> 00:05:35.260 align:middle line:84%
And it's not vulnerable to
the actual Heartbleed exploit.

00:05:35.260 --> 00:05:38.560 align:middle line:84%
So the site did not offer the
Heartbleed TLS extension prior

00:05:38.560 --> 00:05:40.420 align:middle line:90%
to the Heartbleed disclosure.

00:05:40.420 --> 00:05:43.303 align:middle line:90%
And so was not exploitable.

00:05:43.303 --> 00:05:45.220 align:middle line:84%
You can learn more about
these vulnerabilities

00:05:45.220 --> 00:05:48.850 align:middle line:84%
by clicking on these
hyperlinked links here.

00:05:48.850 --> 00:05:52.630 align:middle line:84%
You can also click on the SSL
certificate chain, which will,

00:05:52.630 --> 00:05:54.520 align:middle line:84%
essentially, give you
information regarding

00:05:54.520 --> 00:05:56.020 align:middle line:90%
the-- as it says here--

00:05:56.020 --> 00:05:58.210 align:middle line:90%
the actual certificate chain.

00:05:58.210 --> 00:06:01.840 align:middle line:84%
Hosting history, this is
very useful in getting

00:06:01.840 --> 00:06:04.540 align:middle line:84%
an idea as to what
hosting providers

00:06:04.540 --> 00:06:06.490 align:middle line:90%
we use to Host this website.

00:06:06.490 --> 00:06:10.420 align:middle line:84%
Now as I said, in my
case, this is a site

00:06:10.420 --> 00:06:13.900 align:middle line:84%
that goes through Cloudflare,
which means that information

00:06:13.900 --> 00:06:14.950 align:middle line:90%
will be redacted.

00:06:14.950 --> 00:06:17.560 align:middle line:84%
And then, of course, you have
the sender policy framework

00:06:17.560 --> 00:06:18.480 align:middle line:90%
here.

00:06:18.480 --> 00:06:20.230 align:middle line:84%
And then, of course,
we have web trackers.

00:06:20.230 --> 00:06:22.300 align:middle line:84%
This is very important
because it tells you

00:06:22.300 --> 00:06:26.560 align:middle line:84%
what analytics systems or
what trackers are currently

00:06:26.560 --> 00:06:27.490 align:middle line:90%
active on the site.

00:06:27.490 --> 00:06:29.230 align:middle line:84%
In this case, you
can see that we

00:06:29.230 --> 00:06:31.450 align:middle line:84%
have Google Analytics
and WordPress

00:06:31.450 --> 00:06:34.430 align:middle line:90%
analytics enabled here.

00:06:34.430 --> 00:06:38.200 align:middle line:84%
And we then have the
site technology profiler,

00:06:38.200 --> 00:06:40.450 align:middle line:90%
which tells you what--

00:06:40.450 --> 00:06:43.640 align:middle line:84%
in this case-- the proxy
server that's being used,

00:06:43.640 --> 00:06:45.070 align:middle line:90%
which is Cloudflare.

00:06:45.070 --> 00:06:47.830 align:middle line:84%
On the service side, what
web technologies are running?

00:06:47.830 --> 00:06:50.890 align:middle line:84%
We can see we have
PHP, XML, SSL,

00:06:50.890 --> 00:06:53.930 align:middle line:84%
and we know that PHP is
enabled on the client-side.

00:06:53.930 --> 00:06:57.070 align:middle line:84%
Of course, we have
JavaScript and yeah,

00:06:57.070 --> 00:06:58.497 align:middle line:90%
that's pretty much it.

00:06:58.497 --> 00:07:00.580 align:middle line:84%
We then have the client-side
scripting frameworks,

00:07:00.580 --> 00:07:04.270 align:middle line:84%
which is jQuery and Google
hosted libraries for fonts.

00:07:04.270 --> 00:07:06.340 align:middle line:84%
In this case, it's
the Google API

00:07:06.340 --> 00:07:08.840 align:middle line:84%
used to retrieve
JavaScript libraries.

00:07:08.840 --> 00:07:11.180 align:middle line:84%
And then the advertising
networks, in this case,

00:07:11.180 --> 00:07:12.130 align:middle line:90%
it's AdSense.

00:07:12.130 --> 00:07:15.070 align:middle line:84%
And the blog, which tells us
that it's running WordPress,

00:07:15.070 --> 00:07:17.000 align:middle line:90%
which is really, really cool.

00:07:17.000 --> 00:07:18.940 align:middle line:84%
And then, of course,
under PHP application,

00:07:18.940 --> 00:07:21.590 align:middle line:84%
it will tell you what
application is running.

00:07:21.590 --> 00:07:24.460 align:middle line:84%
So you can see that is running
WordPress and WordPress is

00:07:24.460 --> 00:07:28.840 align:middle line:84%
a PHP application that runs on a
LAMP stack, which, again, tells

00:07:28.840 --> 00:07:34.090 align:middle line:84%
us as a fact that this website
also utilizes a database.

00:07:34.090 --> 00:07:37.180 align:middle line:84%
Now whether this database
is being run or being hosted

00:07:37.180 --> 00:07:39.460 align:middle line:84%
on another server is
a different question,

00:07:39.460 --> 00:07:43.360 align:middle line:84%
but we know it's either
going to be MySQL or MariaDB.

00:07:43.360 --> 00:07:45.740 align:middle line:84%
We can see that RSS
is also enabled,

00:07:45.740 --> 00:07:47.480 align:middle line:90%
which is also very interesting.

00:07:47.480 --> 00:07:51.970 align:middle line:84%
And then, of course, let's see
the other important information

00:07:51.970 --> 00:07:53.950 align:middle line:90%
here, that we are HTML5.

00:07:53.950 --> 00:07:55.700 align:middle line:84%
So you can see
that, in this case,

00:07:55.700 --> 00:07:59.270 align:middle line:84%
HTML5 is indeed being used
for mobile optimization.

00:07:59.270 --> 00:08:02.050 align:middle line:84%
So the reason I wanted
to cover Netcraft

00:08:02.050 --> 00:08:04.420 align:middle line:84%
is because it sort of collates
all of the information

00:08:04.420 --> 00:08:06.550 align:middle line:84%
that we've been able
to identify previously

00:08:06.550 --> 00:08:08.020 align:middle line:90%
or in previous videos.

00:08:08.020 --> 00:08:11.920 align:middle line:84%
And it gives you in a very
simple, easy to consume,

00:08:11.920 --> 00:08:13.700 align:middle line:90%
easy to understand format.

00:08:13.700 --> 00:08:16.660 align:middle line:90%
So do take a look at Netcraft.

00:08:16.660 --> 00:08:19.150 align:middle line:84%
As I said, you can perform
a lookup on another site.

00:08:19.150 --> 00:08:23.980 align:middle line:84%
So I can perform another lookup
on maybe a site that I own,

00:08:23.980 --> 00:08:28.550 align:middle line:84%
like hackertube.net, and let's
see how this is different.

00:08:28.550 --> 00:08:32.010 align:middle line:84%
So I'm just going to
run the lookup here.

00:08:32.010 --> 00:08:35.500 align:middle line:84%
And you'll actually see the
differences between the two.

00:08:35.500 --> 00:08:39.390 align:middle line:84%
They both go through a
web application firewall.

00:08:39.390 --> 00:08:41.130 align:middle line:84%
In the case of
hackertube.net, it

00:08:41.130 --> 00:08:44.640 align:middle line:84%
goes through an actual
web application firewall.

00:08:44.640 --> 00:08:46.598 align:middle line:84%
So we'll give this
a couple of seconds

00:08:46.598 --> 00:08:47.890 align:middle line:90%
and you'll see the differences.

00:08:47.890 --> 00:08:51.780 align:middle line:84%
So in this case, you can
see that the actual hosting

00:08:51.780 --> 00:08:56.010 align:middle line:84%
company is GoDaddy, or the
actual registrar is GoDaddy.

00:08:56.010 --> 00:09:00.120 align:middle line:84%
It goes through the
actual security firewall.

00:09:00.120 --> 00:09:04.650 align:middle line:84%
So that's identifiable via
the actual name server.

00:09:04.650 --> 00:09:06.690 align:middle line:84%
The domain registrar
is namecheap,

00:09:06.690 --> 00:09:10.380 align:middle line:84%
so we now know that this domain
was registered with namecheap.

00:09:10.380 --> 00:09:15.660 align:middle line:84%
And then, of course, the
reverse DNS lookup points

00:09:15.660 --> 00:09:23.700 align:middle line:84%
towards the following cloud
proxy security domain there.

00:09:23.700 --> 00:09:26.580 align:middle line:84%
As for the IP
delegation, you can

00:09:26.580 --> 00:09:32.760 align:middle line:84%
see all of the IP addresses
owned by SUCURI, which makes

00:09:32.760 --> 00:09:34.500 align:middle line:90%
sense, apologies for that.

00:09:34.500 --> 00:09:38.940 align:middle line:84%
And of course, you also have
the SSL certificate information,

00:09:38.940 --> 00:09:40.830 align:middle line:84%
which tells you when
it's going to expire.

00:09:40.830 --> 00:09:43.050 align:middle line:84%
And of course, who
it was issued by.

00:09:43.050 --> 00:09:46.590 align:middle line:84%
In this case, it's issued
by Starfield Technologies.

00:09:46.590 --> 00:09:49.500 align:middle line:90%
And I'm looking for the actual--

00:09:49.500 --> 00:09:52.980 align:middle line:84%
let's see-- let's take a look at
the actual technologies running

00:09:52.980 --> 00:09:54.640 align:middle line:90%
on the actual site.

00:09:54.640 --> 00:10:01.360 align:middle line:84%
So HTTP accelerator, we can see
we have the SUCURI cloud proxy.

00:10:01.360 --> 00:10:04.860 align:middle line:84%
SUCURI is essentially a combined
web application firewall

00:10:04.860 --> 00:10:08.020 align:middle line:84%
and a content delivery
network provider.

00:10:08.020 --> 00:10:10.560 align:middle line:84%
We can see on the
client-side is JavaScript.

00:10:10.560 --> 00:10:13.270 align:middle line:84%
Nothing regarding the
actual server-side.

00:10:13.270 --> 00:10:16.200 align:middle line:84%
So we haven't been able to
identify that, but yeah.

00:10:16.200 --> 00:10:18.960 align:middle line:84%
That is going to conclude
the practical demonstration

00:10:18.960 --> 00:10:21.380 align:middle line:90%
side of this video.

00:10:21.380 --> 00:10:24.760 align:middle line:84%
All right, so that is how to
perform website reconnaissance,

00:10:24.760 --> 00:10:27.740 align:middle line:84%
or website footprinting
with Netcraft.

00:10:27.740 --> 00:10:30.115 align:middle line:84%
In the next video, we're going
to be taking a look at how

00:10:30.115 --> 00:10:34.600 align:middle line:84%
to perform DNS reconnaissance,
more specifically, passive

00:10:34.600 --> 00:10:35.890 align:middle line:90%
DNS reconnaissance.

00:10:35.890 --> 00:10:41.350 align:middle line:84%
So we're really just trying
to identify the various DNS

00:10:41.350 --> 00:10:44.210 align:middle line:84%
records pertinent to
a particular domain.

00:10:44.210 --> 00:10:47.500 align:middle line:84%
So I'll be seeing you
in the next video.

00:10:47.500 --> 00:10:48.000 align:middle line:90%