Analysis report on IP address: 203.242.74.136

203.242.74.136
Generated on
02 Apr 2021 15:41
Duration of the analysis
50.4s
Share

Score 100%
A
DNS
-
IP
A
MAIL
-
WEB
A

Resume

All Dns servers are responding

One or more servers are not responding (timeout, refused, ...)

DNS servers IP are in different class C

IPs have the same C class.

Domain have at least 2 DNS servers

DNS require at least 2 name servers.

SOA email is valid

Email address used in SOA is not valid

DNS

Dns servers for 74.242.203.in-addr.arpa

203.242.74.136 was detected as ipv4

Possible problem in Dns Tree

We have detected the following error on one or more server(s).
Consult Tree for more details.

  • Refuse to respond or is in timeout state.

Query informations

Server
d.root-servers.net
[ 199.7.91.13 ]
Duration
9 ms
Type
authority
Headers
RCODE : 0 AA : 0 TC : 0

Response

Query informations

Server
a.in-addr-servers.arpa
[ 199.180.182.53 ]
Duration
142 ms
Type
authority
Headers
RCODE : 0 AA : 0 TC : 0

Response

Query informations

Server
b.in-addr-servers.arpa
[ 199.253.183.183 ]
Duration
35 ms
Type
authority
Headers
RCODE : 0 AA : 0 TC : 0

Response

Query informations

Server
c.in-addr-servers.arpa
[ 196.216.169.10 ]
Duration
180 ms
Type
authority
Headers
RCODE : 0 AA : 0 TC : 0

Response

Query informations

Server
d.in-addr-servers.arpa
[ 200.10.60.53 ]
Duration
235 ms
Type
authority
Headers
RCODE : 0 AA : 0 TC : 0

Response

Query informations

Server
e.in-addr-servers.arpa
[ 203.119.86.101 ]
Duration
262 ms
Type
authority
Headers
RCODE : 0 AA : 0 TC : 0

Response

Query informations

Server
f.in-addr-servers.arpa
[ 193.0.9.1 ]
Duration
28 ms
Type
authority
Headers
RCODE : 0 AA : 0 TC : 0

Response

Query informations

Server
apnic.authdns.ripe.net
[ 193.0.9.9 ]
Duration
20 ms
Type
authority
Headers
RCODE : 0 AA : 0 TC : 0

Response

Query informations

Server
apnic1.dnsnode.net
[ 194.146.106.106 ]
Duration
16 ms
Type
authority
Headers
RCODE : 0 AA : 0 TC : 0

Response

Query informations

Server
ns2.apnic.net
[ 203.119.95.53 ]
Duration
18 ms
Type
authority
Headers
RCODE : 0 AA : 0 TC : 0

Response

Query informations

Server
ns3.lacnic.net
[ 200.3.13.14 ]
Duration
198 ms
Type
authority
Headers
RCODE : 0 AA : 0 TC : 0

Response

Query informations

Server
rirns.arin.net
[ 199.253.249.53 ]
Duration
142 ms
Type
authority
Headers
RCODE : 0 AA : 0 TC : 0

Response

Query informations

Server
b.dns.kr
[ 210.101.60.1 ]
Duration
2266 ms
Type
authority
Headers
RCODE : 0 AA : 0 TC : 0

Response

Query informations

Server
c.dns.kr
[ 210.101.61.1 ]
Duration
839 ms
Type
authority
Headers
RCODE : 0 AA : 0 TC : 0

Response

Query informations

Server
d.dns.kr
[ 203.83.159.1 ]
Duration
229 ms
Type
authority
Headers
RCODE : 0 AA : 0 TC : 0

Response

Query informations

Server
e.dns.kr
[ 202.30.124.100 ]
Duration
207 ms
Type
authority
Headers
RCODE : 0 AA : 0 TC : 0

Response

Query informations

Server
f.dns.kr
[ 210.101.62.1 ]
Duration
265 ms
Type
authority
Headers
RCODE : 0 AA : 0 TC : 0

Response

Query informations

Server
g.dns.kr
[ 202.31.190.1 ]
Duration
232 ms
Type
authority
Headers
RCODE : 0 AA : 0 TC : 0

Response

Query informations

Server
ns.nuri.net
[ 203.235.122.164 ]
Duration
272 ms
Type
refused
Headers
RCODE : 5 AA : 0 TC : 0

Le serveur refuse de répondre à la requête de type edns.

Query informations

Server
ns.skc.co.kr
[ 203.242.127.90 ]
Duration
220 ms
Type
unknown
Headers
RCODE : 0 AA : 1 TC : 0
DNSSEC analysis not possible on an IP

All Dns servers are responding

One or more servers are not responding (timeout, refused, ...)

Every DNS servers should be accessible and accept public query.

0.005s

DNS servers IP are in different class C

IPs have the same C class.

The class C of each IP must be different so that the servers are not found on the same bay and therefore there is a risk of unavailability.

RFC

0.000s

Domain have at least 2 DNS servers

DNS require at least 2 name servers.

In order for the availability rate of DNS servers to be at its highest, it is vital and recommended by the RFC to have at least 2 servers.

RFC

0.000s

SOA email is valid

Email address used in SOA is not valid

An email address must respect some conditions to be valid, accordding to the RFC 5322.

RFC

0.000s

BIND version is hidden

Passed

The Bind version should not be visible otherwise it will be possible to search for potential security vulnerabilities of the version.

1.002s

All servers return success

Passed

It's important that all servers returned a "success" code.

0.005s

Responses are not CNAME or A

Passed

The answers should not be a CNAME or A type.

RFC

0.005s

SOA are synchronized

Passed

The SOA answered by the DNS servers must be identical for each servers. The most important information is the master server and the contact email address.

0.000s

SOA refresh is valid

Passed

The refresh value be must between 1200 and 43200.

RFC

0.000s

SOA retry, refresh and expire values are correct

Passed

The Retry, Refresh and Expire values musth follow this path : retry < refresh < expire.

RFC

0.000s

DNS servers are not open relay

Passed

DNS resolvers that allow queries from all IP addresses and are exposed to the Internet can be attacked and used to conduct Denial of Service (DoS) attacks on behalf of the hacker.

0.218s

Transfer zone is disable

Passed

An attacker can use a zone transfer that contains a malicious code or an inappropriate format that crashes a DNS server vulnerable to this type of attack, which results in a DoS that destabilizes the DNS services. It is possible to test it manually with this commands: #host -T axfr or #dig axfr.

documentation

0.717s

Recursive query is disable

Passed

Having a dns server that allow recursive queries is a security risk, DDOS attack can be performed.

RFC documentation documentation

0.219s

DNS servers IP are not private

Passed

It is strictly forbidden to have private IP in DNS

documentation

0.000s

DNS servers IP are differents

Skipped

IPs for DNS servers must be different in order to have high availability.

0.000s

DNS servers are synchronized

Skipped

The synchronization of the DNS servers must be perfect in order to avoid any dns resolution error. The servers must therefore give the same answer when asked "what are the DNS servers for the domain?".

0.000s

Ip

Informations

Ip
203.242.74.136
Type
ipv4
Reverse
appl1b.skc.kr
ARPA
136.74.242.203.in-addr.arpa
Class C
203.242.74.0/24
ASN
10049 SK Co.
Organisation
IM668-AP
Maintainer
MNT-KRNIC-AP

Reputation

Blacklists
Ip
Whois server
whois.apnic.net
Raw data
% [whois.apnic.net]
% Whois data copyright terms    http://www.apnic.net/db/dbcopyright.html

% Information related to '203.242.74.0 - 203.242.74.255'

% Abuse contact for '203.242.74.0 - 203.242.74.255' is O32GiA== [at] nic.or.kr'

inetnum:        203.242.74.0 - 203.242.74.255
netname:        SK-NET
descr:          SK Co.,
country:        KR
admin-c:        IM668-AP
tech-c:         IM668-AP
status:         ALLOCATED PORTABLE
mnt-by:         MNT-KRNIC-AP
mnt-irt:        IRT-KRNIC-KR
last-modified:  2019-04-29T07:40:12Z
source:         APNIC

% Information related to '203.242.74.0 - 203.242.74.255'

inetnum:        203.242.74.0 - 203.242.74.255
netname:        SK-NET-KR
descr:          SK Co.,
country:        KR
admin-c:        IA126-KR
tech-c:         BS126-KR
status:         ALLOCATED PORTABLE
mnt-by:         MNT-KRNIC-AP
mnt-irt:        IRT-KRNIC-KR
remarks:        This information has been partially mirrored by APNIC from
remarks:        KRNIC. To obtain more specific information, please use the
remarks:        KRNIC whois server at whois.kisa.or.kr.
changed:        fIOHiIF1h4h5hg== [at] nic.or.kr
source:         KRNIC

% This query was served by the APNIC Whois Service version 1.88.15-SNAPSHOT (WHOIS-UK4)


Blacklists

RFC Ignorant
Rbl Jp
RblDns
Sorbs
Spam Eating Monkey
SpamHaus
SuRbl
Support Intelligence
Swinog
UriBl

Ip is not blacklisted

Passed

An ip must not be blacklisted or it will be penalized for referencing and deliverability of emails.

0.000s

Mail

There is no mail server. Please test appl1b.skc.kr.

Name
appl1b.skc.kr
IP
203.242.74.136
Accessible
Autodiscover analysis not possible on an IP

Web

There is no web server. Please test appl1b.skc.kr.

Url
http://203.242.74.136/
Timeout
Yes
Url
https://203.242.74.136/
Timeout
Yes

HTTP port (80) is open

Skipped

This test verifies the presence of a website for the given IP or domain. Then scans port 80.
If the domain or IP is pointing to a website then port 80 must be open so that it can be accessed from a browser.
Otherwise port 80 must be closed.

0.000s

HTTPS port (443) is open

Skipped

This test verifies the presence of a website for the given IP or domain. Then scans port 443.
If the domain or IP is pointing to a website then port 443 must be open so that it can be accessed from a browser.
Otherwise port 443 must be closed.

0.000s

Web server version is hidden

Skipped

To avoid giving details to malicious people, the version of the server should not be visible.

0.000s

Web application technology is hidden

Skipped

To avoid giving details to malicious people, the technology that supports the application should not be visible.

0.000s

Cookies are secure

Skipped

Using "HttpOnly" instruction prevents someone to access to cookies via Javascript. The secure flag will allow you to prevent a cookie from ever being communicated in simple HTTP. (RFC 6265 section 8.3)

RFC

0.000s

X-XSS-Protection header is present

Skipped

The HTTP X-XSS-Protection response header is a feature of Internet Explorer, Chrome and Safari that stops pages from loading when they detect reflected cross-site scripting (XSS) attacks.

documentation

0.000s

Content Security Policy header is present

Skipped

The HTTP Content-Security-Policy response header allows web site administrators to control resources the user agent is allowed to load for a given page. With a few exceptions, policies mostly involve specifying server origins and script endpoints. This helps guard against cross-site scripting attacks (XSS).

documentation

0.000s

Content Type Options header is present

Skipped

The only defined value, "nosniff", prevents Internet Explorer from MIME-sniffing a response away from the declared content-type. This also applies to Google Chrome, when downloading extensions.

0.000s