WEBVTT

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


00:00:10.200 --> 00:00:13.092 align:middle line:84%
DNS recon, or DNS
reconnaissance.

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

00:00:15.300 --> 00:00:17.760 align:middle line:90%
to perform DNS reconnaissance.

00:00:17.760 --> 00:00:20.280 align:middle line:84%
So again, remember, this falls
under passive information

00:00:20.280 --> 00:00:22.380 align:middle line:84%
gathering, which
means we're not really

00:00:22.380 --> 00:00:26.250 align:middle line:84%
going to be actively
engaging with the DNS server.

00:00:26.250 --> 00:00:28.260 align:middle line:84%
So we're not going to
be performing anything

00:00:28.260 --> 00:00:31.590 align:middle line:90%
like DNS zone transfer.

00:00:31.590 --> 00:00:35.640 align:middle line:84%
We're simply trying to
identify the records associated

00:00:35.640 --> 00:00:37.830 align:middle line:90%
with a particular domain.

00:00:37.830 --> 00:00:40.440 align:middle line:84%
So we're trying to
identify A records,

00:00:40.440 --> 00:00:45.390 align:middle line:84%
maybe the mail server, IP
address, TXT records, anything

00:00:45.390 --> 00:00:49.200 align:middle line:84%
that could provide us with a
better understanding as to how

00:00:49.200 --> 00:00:54.335 align:middle line:84%
the target website or a target
system is configured to run.

00:00:54.335 --> 00:00:55.710 align:middle line:84%
And in this case,
we're primarily

00:00:55.710 --> 00:00:59.250 align:middle line:84%
going to be focusing on
websites, because that's really

00:00:59.250 --> 00:01:00.820 align:middle line:90%
where DNS comes into play.

00:01:00.820 --> 00:01:03.360 align:middle line:84%
So again, I'm going to be
running this or performing

00:01:03.360 --> 00:01:06.510 align:middle line:84%
this practical demonstration
on my Kali Linux VM.

00:01:06.510 --> 00:01:09.330 align:middle line:84%
And the reason for that,
as I said previously,

00:01:09.330 --> 00:01:12.480 align:middle line:84%
is because we're essentially
utilizing the internet.

00:01:12.480 --> 00:01:15.510 align:middle line:84%
So I'm just going to switch
over to my Kali Linux VM,

00:01:15.510 --> 00:01:16.860 align:middle line:90%
and we can get started.

00:01:16.860 --> 00:01:20.610 align:middle line:90%


00:01:20.610 --> 00:01:23.340 align:middle line:90%
So I'm back on my Kali Linux VM.

00:01:23.340 --> 00:01:26.670 align:middle line:84%
And the first tool that we're
going to be taking a look at

00:01:26.670 --> 00:01:29.460 align:middle line:90%
is a tool called DNSRecon.

00:01:29.460 --> 00:01:33.180 align:middle line:84%
So if I just perform a quick
Google search for DNSRecon,

00:01:33.180 --> 00:01:34.740 align:middle line:84%
this will bring
up the tool here.

00:01:34.740 --> 00:01:37.380 align:middle line:84%
I'm just going to accept
here, because Google

00:01:37.380 --> 00:01:40.920 align:middle line:84%
thinks that I'm a robot for some
weird reason, but there we are.

00:01:40.920 --> 00:01:42.700 align:middle line:90%
The Google search is complete.

00:01:42.700 --> 00:01:45.480 align:middle line:84%
So as you can see,
DNSRecon is a Python script

00:01:45.480 --> 00:01:49.320 align:middle line:84%
that provides you the ability
to perform or check all name

00:01:49.320 --> 00:01:51.290 align:middle line:84%
server records for
zone transfers,

00:01:51.290 --> 00:01:53.280 align:middle line:84%
enumerate general
DNS records, which

00:01:53.280 --> 00:01:56.880 align:middle line:84%
is what we're looking for here,
for a particular domain name.

00:01:56.880 --> 00:02:00.720 align:middle line:84%
So we're looking for the
actual mail server address,

00:02:00.720 --> 00:02:03.540 align:middle line:84%
the actual name
server A addresses,

00:02:03.540 --> 00:02:07.440 align:middle line:84%
which is IPv4 addresses,
IPv6 addresses,

00:02:07.440 --> 00:02:10.419 align:middle line:84%
and of course, the
TXT records here.

00:02:10.419 --> 00:02:14.940 align:middle line:84%
So DNSRecon comes
pre-packaged with Kali Linux.

00:02:14.940 --> 00:02:16.260 align:middle line:90%
So we don't need to install it.

00:02:16.260 --> 00:02:19.560 align:middle line:84%
To use it, we can
simply type in dnsrecon.

00:02:19.560 --> 00:02:21.780 align:middle line:84%
And I can open up
the Help menu here.

00:02:21.780 --> 00:02:24.750 align:middle line:84%
Although, we're really not
going to be performing--

00:02:24.750 --> 00:02:27.420 align:middle line:84%
we're not going to be taking
a look at how to utilize it

00:02:27.420 --> 00:02:30.450 align:middle line:84%
extensively, because
there are other resources,

00:02:30.450 --> 00:02:33.640 align:middle line:84%
like DNSdumpster, which
I'll get to in a second.

00:02:33.640 --> 00:02:35.440 align:middle line:84%
But it's fairly
easy to understand.

00:02:35.440 --> 00:02:39.060 align:middle line:84%
We simply need to say,
dnsrecon, and then specify

00:02:39.060 --> 00:02:40.870 align:middle line:84%
the domain name,
which in this case,

00:02:40.870 --> 00:02:43.830 align:middle line:84%
we're going to be
using hackersploit.org.

00:02:43.830 --> 00:02:45.120 align:middle line:90%
There we are.

00:02:45.120 --> 00:02:48.150 align:middle line:84%
And it's going to
take a few seconds.

00:02:48.150 --> 00:02:51.570 align:middle line:84%
And once it's done, it's going
to output a lot of information.

00:02:51.570 --> 00:02:54.300 align:middle line:84%
Now, in this case, this may
look a little bit confusing,

00:02:54.300 --> 00:02:56.470 align:middle line:84%
but let me explain
what's happening here.

00:02:56.470 --> 00:02:59.790 align:middle line:84%
So when we're performing
passive DNS reconnaissance,

00:02:59.790 --> 00:03:03.247 align:middle line:84%
we're essentially trying to look
for the name server addresses.

00:03:03.247 --> 00:03:04.830 align:middle line:84%
In this case, we
know it's Cloudflare.

00:03:04.830 --> 00:03:09.270 align:middle line:84%
So it provides us with the
name server, the primary name

00:03:09.270 --> 00:03:10.950 align:middle line:90%
server used by a site--

00:03:10.950 --> 00:03:13.050 align:middle line:84%
as I said, in this
case, it's Cloudflare--

00:03:13.050 --> 00:03:16.300 align:middle line:84%
and then any other
records, like the A record,

00:03:16.300 --> 00:03:19.890 align:middle line:84%
which is the IPv4 address
of the website, which

00:03:19.890 --> 00:03:22.050 align:middle line:84%
in this case because it's
going through Cloudflare

00:03:22.050 --> 00:03:24.090 align:middle line:90%
is not the accurate one.

00:03:24.090 --> 00:03:26.640 align:middle line:84%
We then have the
AAAA records, which

00:03:26.640 --> 00:03:29.370 align:middle line:90%
is referring to IPv6 addresses.

00:03:29.370 --> 00:03:32.430 align:middle line:84%
And then, of course, the other
important piece of information

00:03:32.430 --> 00:03:34.560 align:middle line:84%
is the actual mail
server address

00:03:34.560 --> 00:03:37.170 align:middle line:84%
denoted by the MX
record here, which

00:03:37.170 --> 00:03:38.580 align:middle line:90%
points to the following IP.

00:03:38.580 --> 00:03:42.120 align:middle line:84%
So that's very important,
because if you perform

00:03:42.120 --> 00:03:44.280 align:middle line:84%
your research, you know
that Cloudflare really

00:03:44.280 --> 00:03:48.960 align:middle line:84%
doesn't hide our proxy mail
server addresses really well.

00:03:48.960 --> 00:03:52.380 align:middle line:84%
So am I secretly revealing
something to you?

00:03:52.380 --> 00:03:57.330 align:middle line:84%
But if we perform this on a
site like zonetransfer.me,

00:03:57.330 --> 00:03:58.890 align:middle line:90%
which I'll just do right now.

00:03:58.890 --> 00:04:00.150 align:middle line:90%
Let me just clear my terminal.

00:04:00.150 --> 00:04:02.880 align:middle line:90%
So I'll say dnsrecon, and d.

00:04:02.880 --> 00:04:04.940 align:middle line:84%
And I can then say
zonetransfer.me.

00:04:04.940 --> 00:04:07.930 align:middle line:90%


00:04:07.930 --> 00:04:10.040 align:middle line:84%
You'll be able to see
what I'm talking about.

00:04:10.040 --> 00:04:13.700 align:middle line:84%
So you can see that, firstly,
DNSSEC is not configured.

00:04:13.700 --> 00:04:16.850 align:middle line:84%
It'll tell us the actual name
server, which in this case,

00:04:16.850 --> 00:04:20.180 align:middle line:84%
it provides the domain, and
then the mapped IP address.

00:04:20.180 --> 00:04:23.268 align:middle line:84%
And then, of course, we
have the various MX records.

00:04:23.268 --> 00:04:25.060 align:middle line:84%
Now, in this case, it
looks like it failed,

00:04:25.060 --> 00:04:27.560 align:middle line:84%
but that's not really
a problem in this case.

00:04:27.560 --> 00:04:30.760 align:middle line:84%
So we have various
MX records that

00:04:30.760 --> 00:04:33.820 align:middle line:84%
point to, in certain
cases, different addresses.

00:04:33.820 --> 00:04:35.530 align:middle line:84%
But from this, you
can pretty much

00:04:35.530 --> 00:04:38.950 align:middle line:84%
tell what email
service or email server

00:04:38.950 --> 00:04:43.360 align:middle line:84%
is being used by this
particular company organization.

00:04:43.360 --> 00:04:47.650 align:middle line:84%
In this case, it looks like
they are using Google Mail, or G

00:04:47.650 --> 00:04:51.400 align:middle line:84%
Suite, if you will, because we
can see quite a few Google Mail

00:04:51.400 --> 00:04:52.810 align:middle line:90%
MX records here.

00:04:52.810 --> 00:04:56.260 align:middle line:84%
And then, of course, we get the
IP address of the actual site,

00:04:56.260 --> 00:04:58.330 align:middle line:90%
which is the A record here.

00:04:58.330 --> 00:05:00.580 align:middle line:84%
And then, of course,
we get a TXT record,

00:05:00.580 --> 00:05:03.860 align:middle line:84%
which are essentially used
for diagnostic information.

00:05:03.860 --> 00:05:06.340 align:middle line:84%
In this case, it's
google-site-verification.

00:05:06.340 --> 00:05:09.700 align:middle line:84%
A TXT record, that
is typically used

00:05:09.700 --> 00:05:13.330 align:middle line:84%
whenever you want to track
a website's analytics

00:05:13.330 --> 00:05:14.800 align:middle line:90%
with Google.

00:05:14.800 --> 00:05:19.540 align:middle line:84%
They'll typically tell you to
add a DNS record, a TXT DNS

00:05:19.540 --> 00:05:21.940 align:middle line:84%
record, and add the
following information.

00:05:21.940 --> 00:05:24.530 align:middle line:84%
So in this case, it's
the domain name itself.

00:05:24.530 --> 00:05:26.980 align:middle line:84%
And then this is the
actual value contained

00:05:26.980 --> 00:05:30.590 align:middle line:90%
within the actual TXT record.

00:05:30.590 --> 00:05:32.170 align:middle line:90%
So that's how to use DNSRecon.

00:05:32.170 --> 00:05:34.840 align:middle line:84%
Now, a tool that I really
recommend that you use

00:05:34.840 --> 00:05:38.200 align:middle line:84%
and one that I personally
use for pen tests is a site

00:05:38.200 --> 00:05:41.530 align:middle line:84%
called DNSdumpster, which
essentially performs

00:05:41.530 --> 00:05:44.410 align:middle line:84%
DNS reconnaissance,
research, and it essentially

00:05:44.410 --> 00:05:47.500 align:middle line:84%
finds and performs a
lookup on DNS records.

00:05:47.500 --> 00:05:51.100 align:middle line:84%
Very similar to what
DNSRecon does, but the way it

00:05:51.100 --> 00:05:53.170 align:middle line:84%
sorts and organizes
the information

00:05:53.170 --> 00:05:54.920 align:middle line:90%
is absolutely fantastic.

00:05:54.920 --> 00:05:57.820 align:middle line:84%
So as it says here,
"DNSdumpster.com

00:05:57.820 --> 00:06:00.970 align:middle line:84%
is a free domain research
tool that can discover hosts

00:06:00.970 --> 00:06:02.260 align:middle line:90%
related to a domain.

00:06:02.260 --> 00:06:05.050 align:middle line:84%
Finding visible hosts from
the attacker's perspective

00:06:05.050 --> 00:06:07.780 align:middle line:84%
is an important part of the
security assessment process."

00:06:07.780 --> 00:06:08.870 align:middle line:90%
Indeed, it is.

00:06:08.870 --> 00:06:13.050 align:middle line:84%
So I'll just enter my site
here, so hackersploit.org.

00:06:13.050 --> 00:06:16.185 align:middle line:84%
We'll give this a couple of
seconds, and there we are.

00:06:16.185 --> 00:06:19.680 align:middle line:84%
So firstly, it's going to
show you the IP block owners.

00:06:19.680 --> 00:06:22.590 align:middle line:84%
In this case, they all
belong to Cloudflare.

00:06:22.590 --> 00:06:24.630 align:middle line:84%
So it'll provide us
with the DNS servers

00:06:24.630 --> 00:06:28.540 align:middle line:84%
used by this website, which in
this case are the following.

00:06:28.540 --> 00:06:31.380 align:middle line:84%
So you have
dee.ns.cloudflare.com,

00:06:31.380 --> 00:06:35.525 align:middle line:84%
and jim.ns.cloudflare.com and
the respective IP addresses.

00:06:35.525 --> 00:06:38.160 align:middle line:84%
It then provides you with
the organization name

00:06:38.160 --> 00:06:42.100 align:middle line:84%
that owns that particular
IP and the location.

00:06:42.100 --> 00:06:43.620 align:middle line:84%
And if we click
on this here, you

00:06:43.620 --> 00:06:47.610 align:middle line:84%
can see you can get the HTTP
headers from this particular IP

00:06:47.610 --> 00:06:48.270 align:middle line:90%
address.

00:06:48.270 --> 00:06:52.500 align:middle line:84%
You can attempt a zone transfer,
which we'll not do right now.

00:06:52.500 --> 00:06:56.550 align:middle line:84%
You can also trace a path
to an IP address using MTR.

00:06:56.550 --> 00:06:59.650 align:middle line:84%
You can also find hosts
sharing this DNS service.

00:06:59.650 --> 00:07:04.830 align:middle line:84%
So for example, if we identified
this particular DNS server,

00:07:04.830 --> 00:07:08.130 align:middle line:84%
we could also try and
see what other websites

00:07:08.130 --> 00:07:10.980 align:middle line:84%
or what other hosts are
using this DNS server.

00:07:10.980 --> 00:07:12.570 align:middle line:84%
And we can also
search the banners

00:07:12.570 --> 00:07:14.363 align:middle line:90%
for net block, which is passive.

00:07:14.363 --> 00:07:16.530 align:middle line:84%
And that's one of the great
things about DNSdumpster

00:07:16.530 --> 00:07:18.480 align:middle line:84%
is it will actually
classify the checks

00:07:18.480 --> 00:07:21.090 align:middle line:84%
you are performing
based on whether or not

00:07:21.090 --> 00:07:22.930 align:middle line:90%
they're passive or active.

00:07:22.930 --> 00:07:26.550 align:middle line:84%
So in this case, we can
perform the actual find

00:07:26.550 --> 00:07:29.020 align:middle line:90%
hosts sharing this DNS server.

00:07:29.020 --> 00:07:30.540 align:middle line:90%
And this will give you a list.

00:07:30.540 --> 00:07:33.000 align:middle line:84%
In this case, it tells us "No
DNS server records found."

00:07:33.000 --> 00:07:33.960 align:middle line:90%
That's perfectly fine.

00:07:33.960 --> 00:07:36.730 align:middle line:84%
We'll get back to
that in a second.

00:07:36.730 --> 00:07:38.610 align:middle line:84%
But then we have
the MX record, which

00:07:38.610 --> 00:07:41.130 align:middle line:84%
points to the mail
server, and in this case,

00:07:41.130 --> 00:07:44.130 align:middle line:90%
premium58 web-hosting.

00:07:44.130 --> 00:07:46.710 align:middle line:90%
That's owned by NAMECHEAP.

00:07:46.710 --> 00:07:48.090 align:middle line:90%
And we can then--

00:07:48.090 --> 00:07:50.100 align:middle line:90%
again, if we click on--

00:07:50.100 --> 00:07:53.220 align:middle line:84%
this is because
this is a MX record.

00:07:53.220 --> 00:07:56.370 align:middle line:84%
This is essentially pointing to
any mail server that has been

00:07:56.370 --> 00:07:58.740 align:middle line:90%
configured for this domain.

00:07:58.740 --> 00:08:03.180 align:middle line:84%
The additional checks we can
perform are an nmap port scan.

00:08:03.180 --> 00:08:04.020 align:middle line:90%
But that's active.

00:08:04.020 --> 00:08:07.320 align:middle line:84%
And by the way, this is being
done on the website itself.

00:08:07.320 --> 00:08:10.200 align:middle line:84%
But yeah, we essentially
get the TXT records,

00:08:10.200 --> 00:08:14.580 align:middle line:84%
which you can see this site
has been verified by Google.

00:08:14.580 --> 00:08:16.650 align:middle line:84%
And there are a couple
of other TXT records.

00:08:16.650 --> 00:08:19.170 align:middle line:84%
And then, of course, we
get additional A records.

00:08:19.170 --> 00:08:22.500 align:middle line:84%
And in this case, we've been
able to identify a subdomain.

00:08:22.500 --> 00:08:26.040 align:middle line:84%
In this case, it's pointing
to forum.hackersploit.org.

00:08:26.040 --> 00:08:27.420 align:middle line:90%
So we can open that up.

00:08:27.420 --> 00:08:31.260 align:middle line:84%
And indeed, we can see that
hackersploit does have a forum.

00:08:31.260 --> 00:08:32.429 align:middle line:90%
Interesting.

00:08:32.429 --> 00:08:34.230 align:middle line:84%
So you can see how
useful this is.

00:08:34.230 --> 00:08:38.340 align:middle line:84%
We've already been able
to identify subdomains

00:08:38.340 --> 00:08:41.640 align:middle line:84%
just by performing
DNS reconnaissance.

00:08:41.640 --> 00:08:43.940 align:middle line:90%
And of course, this is passive.

00:08:43.940 --> 00:08:45.950 align:middle line:84%
And of course, we have
the actual A record

00:08:45.950 --> 00:08:50.540 align:middle line:84%
for the hackersploit.org
domain here.

00:08:50.540 --> 00:08:52.910 align:middle line:90%
We can also perform a tracepath.

00:08:52.910 --> 00:08:55.100 align:middle line:84%
And in this case, a
valid key is required.

00:08:55.100 --> 00:08:57.200 align:middle line:84%
So we will not get
to that, but you

00:08:57.200 --> 00:09:00.500 align:middle line:84%
can download an Excel
spreadsheet of all the hosts,

00:09:00.500 --> 00:09:02.270 align:middle line:90%
or you can view the graph.

00:09:02.270 --> 00:09:05.420 align:middle line:84%
That essentially gives
you a graphical view

00:09:05.420 --> 00:09:08.910 align:middle line:84%
of the DNS reconnaissance
we have performed.

00:09:08.910 --> 00:09:12.890 align:middle line:84%
So the reason why I like this
is because you can actually

00:09:12.890 --> 00:09:17.510 align:middle line:84%
see that we have the following
domains within Cloudflare.

00:09:17.510 --> 00:09:19.550 align:middle line:84%
So these are being
protected by Cloudflare.

00:09:19.550 --> 00:09:21.330 align:middle line:90%
So this is the domain itself.

00:09:21.330 --> 00:09:24.063 align:middle line:84%
We then have the A
records themselves,

00:09:24.063 --> 00:09:25.730 align:middle line:84%
which are being
protected by Cloudflare.

00:09:25.730 --> 00:09:29.430 align:middle line:84%
We have the respective
domains and the IP addresses.

00:09:29.430 --> 00:09:31.260 align:middle line:84%
And then we have
the name servers.

00:09:31.260 --> 00:09:35.960 align:middle line:84%
So we have jim.ns, and
dee.ns.cloudflare.com.

00:09:35.960 --> 00:09:38.450 align:middle line:84%
The mail server is
not being protected

00:09:38.450 --> 00:09:41.450 align:middle line:84%
by Cloudflare, which is very,
very important, which is why

00:09:41.450 --> 00:09:43.280 align:middle line:90%
I wanted to showcase this tool.

00:09:43.280 --> 00:09:46.130 align:middle line:84%
The other cool thing is you can
actually export this as a PNG

00:09:46.130 --> 00:09:48.290 align:middle line:84%
or download it as an
Excel spreadsheet, which

00:09:48.290 --> 00:09:50.010 align:middle line:90%
is absolutely fantastic.

00:09:50.010 --> 00:09:54.500 align:middle line:84%
So if I download this as a PNG,
it is going to save this here.

00:09:54.500 --> 00:09:56.220 align:middle line:90%
It should be downloaded shortly.

00:09:56.220 --> 00:09:57.710 align:middle line:90%
Let's see whether this is done.

00:09:57.710 --> 00:09:59.270 align:middle line:90%
It's probably still downloading.

00:09:59.270 --> 00:10:02.970 align:middle line:90%


00:10:02.970 --> 00:10:05.940 align:middle line:84%
So that is downloaded under
my Downloads directory

00:10:05.940 --> 00:10:07.122 align:middle line:90%
as export.png.

00:10:07.122 --> 00:10:08.580 align:middle line:84%
And you can see we
pretty much have

00:10:08.580 --> 00:10:10.590 align:middle line:84%
the same image
where you actually

00:10:10.590 --> 00:10:12.840 align:middle line:90%
selected or cropped to.

00:10:12.840 --> 00:10:15.060 align:middle line:90%
So I really like that.

00:10:15.060 --> 00:10:17.340 align:middle line:84%
And of course, you can
see that it actually

00:10:17.340 --> 00:10:19.170 align:middle line:90%
maps the domain for you.

00:10:19.170 --> 00:10:21.030 align:middle line:84%
So you can actually
click on this

00:10:21.030 --> 00:10:22.470 align:middle line:90%
to get the full-size image.

00:10:22.470 --> 00:10:25.320 align:middle line:84%
But the really cool thing about
this is it maps it in a way

00:10:25.320 --> 00:10:26.470 align:middle line:90%
that you can understand.

00:10:26.470 --> 00:10:30.720 align:middle line:84%
So we have the domain
hackersploit.org.

00:10:30.720 --> 00:10:33.840 align:middle line:84%
For DNS, we have the
two name servers, right?

00:10:33.840 --> 00:10:35.290 align:middle line:84%
You can see them
right over here.

00:10:35.290 --> 00:10:38.640 align:middle line:84%
So we have dee and jim, and they
point to their own addresses.

00:10:38.640 --> 00:10:40.620 align:middle line:90%
These all belong to Cloudflare.

00:10:40.620 --> 00:10:43.410 align:middle line:84%
We then have the MX record,
which is the mail server.

00:10:43.410 --> 00:10:47.190 align:middle line:84%
It then tells us the IP
address of the mail server.

00:10:47.190 --> 00:10:50.670 align:middle line:84%
We then have an A record for
the forum, which is a subdomain,

00:10:50.670 --> 00:10:53.160 align:middle line:84%
and that points to the
following address here.

00:10:53.160 --> 00:10:55.470 align:middle line:84%
And that, of course, is
protected by Cloudflare.

00:10:55.470 --> 00:10:59.190 align:middle line:84%
And of course, we have the main
domain or the main A record,

00:10:59.190 --> 00:11:00.840 align:middle line:90%
which is hackersploit.org.

00:11:00.840 --> 00:11:03.510 align:middle line:84%
And that points to the
following IP, which is, again

00:11:03.510 --> 00:11:05.340 align:middle line:90%
protected by Cloudflare.

00:11:05.340 --> 00:11:06.820 align:middle line:90%
Really cool stuff.

00:11:06.820 --> 00:11:10.360 align:middle line:84%
So that is DNSdumpster
in a nutshell.

00:11:10.360 --> 00:11:13.020 align:middle line:84%
Now, we can also run
this on another website.

00:11:13.020 --> 00:11:17.910 align:middle line:84%
So I'll just run this
on zonetransfer.me,

00:11:17.910 --> 00:11:21.430 align:middle line:84%
because this will reveal a
little bit more information.

00:11:21.430 --> 00:11:25.050 align:middle line:84%
So I'll just click
on Search there.

00:11:25.050 --> 00:11:26.850 align:middle line:90%
And hopefully, there we are.

00:11:26.850 --> 00:11:30.870 align:middle line:84%
So it's going to perform
the DNS lookup now.

00:11:30.870 --> 00:11:33.090 align:middle line:84%
So you can see we have
the DNS servers here.

00:11:33.090 --> 00:11:36.390 align:middle line:90%
They point to the specific IPs.

00:11:36.390 --> 00:11:39.270 align:middle line:84%
And in this case, you can see
one of the host names points

00:11:39.270 --> 00:11:40.540 align:middle line:90%
to AWS.

00:11:40.540 --> 00:11:44.080 align:middle line:84%
So that means that one of these
name servers is being hosted.

00:11:44.080 --> 00:11:47.160 align:middle line:84%
One of these DNS servers
is being hosted on AWS.

00:11:47.160 --> 00:11:48.660 align:middle line:90%
Very interesting.

00:11:48.660 --> 00:11:50.200 align:middle line:90%
We then have MX records.

00:11:50.200 --> 00:11:52.470 align:middle line:84%
These are the mail
server records here

00:11:52.470 --> 00:11:54.510 align:middle line:90%
that point to Google really.

00:11:54.510 --> 00:11:58.080 align:middle line:84%
So that means that they're
using Gmail or G Suite.

00:11:58.080 --> 00:12:02.910 align:middle line:84%
And then we have a TXT record,
and the A records here.

00:12:02.910 --> 00:12:05.910 align:middle line:84%
We can view the graph here
to get a better understanding

00:12:05.910 --> 00:12:09.090 align:middle line:90%
of the target infrastructure.

00:12:09.090 --> 00:12:13.290 align:middle line:84%
So you can see we have the
zonetransfer.me website.

00:12:13.290 --> 00:12:14.700 align:middle line:90%
We then have the name server.

00:12:14.700 --> 00:12:18.450 align:middle line:84%
That's not being protected
by any proxy or any firewall.

00:12:18.450 --> 00:12:21.420 align:middle line:90%
And one of them has the IP here.

00:12:21.420 --> 00:12:26.130 align:middle line:90%
That is nsztm2.digi.ninja.

00:12:26.130 --> 00:12:28.290 align:middle line:90%
That is running on AWS.

00:12:28.290 --> 00:12:30.300 align:middle line:84%
And then we have
the primary one here

00:12:30.300 --> 00:12:34.690 align:middle line:84%
because it has the one there
with the IP address there.

00:12:34.690 --> 00:12:37.720 align:middle line:84%
And it also looks
like we have OVH here.

00:12:37.720 --> 00:12:39.120 align:middle line:90%
So that's an A record.

00:12:39.120 --> 00:12:41.280 align:middle line:90%
That's zonetransfer.me.

00:12:41.280 --> 00:12:45.240 align:middle line:84%
And then we have all
of these MX records

00:12:45.240 --> 00:12:47.730 align:middle line:90%
that all fall under Google.

00:12:47.730 --> 00:12:50.530 align:middle line:84%
So you can see that these
are all the MX records.

00:12:50.530 --> 00:12:52.860 align:middle line:84%
So I really like this
graph because it gives you

00:12:52.860 --> 00:12:57.090 align:middle line:84%
a very good hierarchical
view of the organization

00:12:57.090 --> 00:13:01.320 align:middle line:84%
and how everything
interpolates with each other

00:13:01.320 --> 00:13:04.080 align:middle line:90%
from a DNS perspective.

00:13:04.080 --> 00:13:07.380 align:middle line:84%
And of course, it provides you
with the actual domain mapping

00:13:07.380 --> 00:13:10.290 align:middle line:84%
here, which you can
explore yourself.

00:13:10.290 --> 00:13:11.890 align:middle line:90%
So really, really cool stuff.

00:13:11.890 --> 00:13:15.690 align:middle line:84%
So that is how to perform
passive DNS reconnaissance.

00:13:15.690 --> 00:13:18.690 align:middle line:84%
And that is going to conclude
the practical demonstration

00:13:18.690 --> 00:13:21.440 align:middle line:90%
side of this video.

00:13:21.440 --> 00:13:23.630 align:middle line:84%
In the next video, we're
going to be taking a look

00:13:23.630 --> 00:13:25.820 align:middle line:84%
at how to detect
firewalls or how

00:13:25.820 --> 00:13:29.420 align:middle line:84%
to identify whether a website
is being protected by a proxy

00:13:29.420 --> 00:13:30.330 align:middle line:90%
or firewall.

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

00:13:34.240 --> 00:13:35.000 align:middle line:90%