Analysis report on domain: 22.245.103.in-addr.arpa favicon

22.245.103.in-addr.arpa has no website

Generated on
26 Sep 2021 01:06
Duration of the analysis
72.2s
Share

Score 72%
E
DNS
E
DOMAIN
A
MAIL
A
WEB
A

Resume

All Dns servers are responding

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

SOA are synchronized

SOA of servers from SList aren't the same.

Transfer zone is disable

ns0.mahaonline.gov.in [103.245.22.10] allows DNS transfer zone.

ns1.mahaonline.gov.in [103.245.22.9] allows DNS transfer zone.

ns5.mahaonline.gov.in [125.16.115.20] allows DNS transfer zone.

BIND version is hidden

Dns version is visible for ns0.mahaonline.gov.in with IP 103.245.22.10 : 9.11.26-RedHat-9.11.26-4.el8_4.

Dns version is visible for ns1.mahaonline.gov.in with IP 103.245.22.9 : 9.11.26-RedHat-9.11.26-4.el8_4.

Dns version is visible for ns5.mahaonline.gov.in with IP 125.16.115.20 : 9.11.26-RedHat-9.11.26-4.el8_4.

SPF is configured for domain

The Domain does not have SPF.

DMARC is configured for domain

The Domain does not have DMARC.

DKIM is configured for domain

We do not detect any DKIM record for this domain.

DNS

Dns servers for 22.245.103.in-addr.arpa

22.245.103.in-addr.arpa was detected as domain

Possible problem in Dns Tree

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

  • Refuse to respond or is in timeout state.

Query informations

Server
k.root-servers.net
[ 193.0.14.129 ]
Duration
21 ms
Type
authority
Headers
RCODE : 0 AA : 0 TC : 0

Response

Query informations

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

Response

Query informations

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

Response

Query informations

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

Response

Query informations

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

Response

Query informations

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

Response

Query informations

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

Response

Query informations

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

Response

Query informations

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

Response

Query informations

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

Response

Query informations

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

Response

Query informations

Server
ns0.mahaonline.gov.in
[ 103.245.22.10 ]
Duration
262 ms
Type
answer
Headers
RCODE : 0 AA : 1 TC : 0

Response

Query informations

Server
ns1.irinn.in
[ 172.67.12.153 ]
Duration
5008 ms
Type
timeout
Headers
RCODE : - AA : - TC : -

Server timeout

Query informations

Server
ns1.irinn.in
[ 104.22.61.80 ]
Duration
5007 ms
Type
timeout
Headers
RCODE : - AA : - TC : -

Server timeout

Query informations

Server
ns1.irinn.in
[ 104.22.60.80 ]
Duration
5013 ms
Type
timeout
Headers
RCODE : - AA : - TC : -

Server timeout

Query informations

Server
ns1.mahaonline.gov.in
[ 103.245.22.9 ]
Duration
136 ms
Type
answer
Headers
RCODE : 0 AA : 1 TC : 0

Response

Query informations

Server
ns1.myirinn.in
[ 162.159.8.208 ]
Duration
35 ms
Type
authority
Headers
RCODE : 0 AA : 0 TC : 0

Server refused to answer when dns query is performed.

Response

Query informations

Server
ns2.irinn.in
[ 162.159.9.245 ]
Duration
15 ms
Type
authority
Headers
RCODE : 0 AA : 0 TC : 0

Server refused to answer when dns query is performed.

Response

Query informations

Server
ns2.myirinn.in
[ 162.159.9.245 ]
Duration
11 ms
Type
authority
Headers
RCODE : 0 AA : 0 TC : 0

Server refused to answer when dns query is performed.

Response

Query informations

Server
ns0.mahaonline.gov.in
[ 103.245.22.10 ]
Duration
136 ms
Type
answer
Headers
RCODE : 0 AA : 1 TC : 0

Response

Query informations

Server
ns1.mahaonline.gov.in
[ 103.245.22.9 ]
Duration
128 ms
Type
answer
Headers
RCODE : 0 AA : 1 TC : 0

Response

Query informations

Server
ns5.mahaonline.gov.in
[ 125.16.115.20 ]
Duration
126 ms
Type
answer
Headers
RCODE : 0 AA : 1 TC : 0

Response

Query informations

Server
ns1.irinn.in
[ 172.67.12.153 ]
Duration
5007 ms
Type
timeout
Headers
RCODE : - AA : - TC : -

Server timeout

Query informations

Server
ns1.irinn.in
[ 104.22.61.80 ]
Duration
5007 ms
Type
timeout
Headers
RCODE : - AA : - TC : -

Server timeout

Query informations

Server
ns1.irinn.in
[ 104.22.60.80 ]
Duration
5011 ms
Type
timeout
Headers
RCODE : - AA : - TC : -

Server timeout

Query informations

Server
ns1.myirinn.in
[ 162.159.8.208 ]
Duration
12 ms
Type
authority
Headers
RCODE : 0 AA : 0 TC : 0

Server refused to answer when dns query is performed.

Response

Query informations

Server
ns2.irinn.in
[ 162.159.9.245 ]
Duration
12 ms
Type
authority
Headers
RCODE : 0 AA : 0 TC : 0

Server refused to answer when dns query is performed.

Response

Query informations

Server
ns2.myirinn.in
[ 162.159.9.245 ]
Duration
12 ms
Type
authority
Headers
RCODE : 0 AA : 0 TC : 0

Server refused to answer when dns query is performed.

Response

Name servers

SOA

From
ns0.mahaonline.gov.in
Master server
ns0.mahaonline.gov.in
TTL
300 (5 minutes)
Contact
hoODiA==@mahaonline.gov.in
Serial
2011071001
Refresh
3600 (1 hour)
Retry
1800 (30 minutes)
Expire
1209601 (2 weeks)
Minimum
300 (5 minutes)
From
ns1.mahaonline.gov.in
Master server
ns1.mahaonline.gov.in
TTL
300 (5 minutes)
Contact
hoODiA==@mahaonline.gov.in
Serial
2011071001
Refresh
3600 (1 hour)
Retry
1800 (30 minutes)
Expire
1209601 (2 weeks)
Minimum
300 (5 minutes)
From
ns5.mahaonline.gov.in
Master server
ns5.mahaonline.gov.in
TTL
300 (5 minutes)
Contact
hoODiA==@mahaonline.gov.in
Serial
1997022700
Refresh
3600 (1 hour)
Retry
1800 (30 minutes)
Expire
1209601 (2 weeks)
Minimum
300 (5 minutes)
Your domain is not protected by DNSSEC DNSSEC Definition

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.011s

SOA are synchronized

SOA of servers from SList aren't the same.

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

Transfer zone is disable

ns0.mahaonline.gov.in [103.245.22.10] allows DNS transfer zone.

ns1.mahaonline.gov.in [103.245.22.9] allows DNS transfer zone.

ns5.mahaonline.gov.in [125.16.115.20] allows DNS transfer zone.

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

1.265s

BIND version is hidden

Dns version is visible for ns0.mahaonline.gov.in with IP 103.245.22.10 : 9.11.26-RedHat-9.11.26-4.el8_4.

Dns version is visible for ns1.mahaonline.gov.in with IP 103.245.22.9 : 9.11.26-RedHat-9.11.26-4.el8_4.

Dns version is visible for ns5.mahaonline.gov.in with IP 125.16.115.20 : 9.11.26-RedHat-9.11.26-4.el8_4.

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

0.373s

Domain have at least 2 DNS servers

Passed

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

All servers return success

Passed

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

0.010s

Responses are not CNAME or A

Passed

The answers should not be a CNAME or A type.

RFC

0.009s

DNS servers IP are differents

Passed

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

0.000s

DNS servers IP are in different class C

Passed

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

DNS servers are synchronized

Passed

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

SOA email is valid

Passed

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

RFC

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.374s

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.372s

DNS servers IP are not private

Passed

It is strictly forbidden to have private IP in DNS

documentation

0.000s

Same MX are returned

Passed

It is extremely important that each DNS return the same MX records in order to avoid contacting an SMTP server that no longer exists.

0.372s

Domain

Whois

We have no registration information about this domain

Reputation

Google Safe Browsing
Web of trust
Blacklists
Virus Total
Domain
Whois server
whois.apnic.net
Status
Domain registration status is unknown

Google Safe Browsing

Status

Web of Trust

Status

Blacklists

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

Virus Total

Detection ratio
0 / 87

Scans

ADMINUSLabs
AICC (MONITORAPP)
AlienVault
Antiy-AVL
Armis
Artists Against 419
Avira
BADWARE.INFO
Baidu-International
Bfore.Ai PreCrime
BitDefender
BlockList
Blueliv
CINS Army
CLEAN MX
CMC Threat Intelligence
CRDF
Certego
Comodo Valkyrie Verdict
CyRadar
CyberCrime
Cyren
DNS8
Dr.Web
ESET
EmergingThreats
Emsisoft
EonScope
Feodo Tracker
Fortinet
FraudScore
G-Data
Google Safebrowsing
GreenSnow
Hoplite Industries
IPsum
K7AntiVirus
MalBeacon
MalSilo
MalwareDomainList
MalwarePatrol
Malwared
Nucleon
OpenPhish
PREBYTES
Phishing Database
Phishtank
Quick Heal
Quttera
Rising
SCUMWARE.org
Sangfor
Scantitan
SecureBrain
Snort IP sample list
Sophos
Spam404
Spamhaus
StopForumSpam
Sucuri SiteCheck
Tencent
ThreatHive
Threatsourcing
Trustwave
URLhaus
VX Vault
Virusdie External Site Scan
Web Security Guard
Webroot
Yandex Safebrowsing
ZeroCERT
alphaMountain.ai
benkow.cc
desenmascara.me
malwares.com URL checker
securolytics
zvelo
AutoShun
Cyan
Forcepoint ThreatSeeker
Kaspersky
Lumu
Netcraft
NotMining
PhishLabs
SafeToOpen
StopBadware

Domain is not blacklisted

Passed

A domain must not be blacklisted or it will be penalized for referencing and deliverability of emails.

0.000s

Domain is not listed in Google Safe Browsing

Passed

Google safe browsing categorizes a domain as bad if something suspicious is detected.

0.000s

Domain is not listed in VirusTotal

Passed

Virus Total analyze your domain or IP address with 66 antivirus.

0.000s

Domain have good reputation on Web of Trust

Passed

Web Of Trust rates thousands of websites and find threats if they exist.

0.000s

DNS servers are same in dns tree and whois

Skipped

The dns servers given in the domain whois must be the same as those returned by a dns resolution request.

0.000s

Mail

There is no mail server. Please test 103.in-addr.arpa.

This domain has no MX server

Autodiscover not configured

SPF is configured for domain

The Domain does not have SPF.

To avoid identity theft, it is strongly recommended to configure SPF.

SPF definition

0.000s

DMARC is configured for domain

The Domain does not have DMARC.

To avoid identity theft, it is strongly recommended to configure DMARC.

DMARC definition

0.000s

DKIM is configured for domain

We do not detect any DKIM record for this domain.

It is strongly recommended to configure DKIM. Note: You could use a service like Mailout to fix this problem. Click on below link to know more

mailout DKIM definition

0.000s

MX servers are accessibles

Skipped

Smtp servers that are listed in DNS area must be accessible, otherwise, there is a risk that emails may be lost

0.000s

MX IPs have reverse

Skipped

When a sending server makes a connection to the recipient server, the recipient server notes the sending IP address and performs a reverse lookup, called a PTR lookup, named after the type of DNS record used. If the result of the reverse lookup matches the result of a forward DNS Lookup, then it's much more likely that the message is legitimate. If the IP address doesn't match, it's much more likely that the sending address was spoofed and therefore much more likely that it's unwanted and could be considered spam.

documentation

0.000s

HELO command is accepted

Skipped

According to the RFC 2181, smtp server should accept HELO command

RFC

0.000s

EHLO command is accepted

Skipped

According to the RFC 2181, smtp server should accept EHLO command

RFC

0.000s

STARTTLS command is accepted

Skipped

STARTTLS turns an unencrypted connection into a secure connection. Note: You can use a service like altospam to solve this problem. Click on the link below to learn more

0.000s

EXPN command is refused

Skipped

EXPN command is now considered to be a security risk, spammers being able to harvest valid e-mail addresses via each mailing list.

0.000s

VRFY command is refused

Skipped

As the EXPN command, VRFY is used by spammers to verify an address.

0.000s

MX servers are not open relay

Skipped

If a server is open relay, there is a risk that spammers use your server to send illegitimate mail.

0.000s

MX servers accept abuse@ address

Skipped

According to the RFC 2142, SMTP server should accept abuse@yourDomain as a recipient.

RFC

0.000s

MX servers accept postmaster@ address

Skipped

According to the RFC 5321, SMTP server should accept postmaster@yourDomain as a recipient.

RFC

0.000s

Banner return 2xx or 4xx code

Skipped

The banner must return (2xx) a valid (4xx) or temporary code.

0.000s

Banner return server name

Skipped

Banner must contain the name of the server

0.000s

SMTP server type is hidden

Skipped

There is a risk to display the type and the version of the server, because people can find a breach for a specific version and use it

0.000s

MX records are FQDN

Skipped

MX must be a domain, not an IP.

RFC

0.000s

MX records are not CNAME

Skipped

According to the RFC 1034 and 2181 CNAME records should not be used with NS and MX

RFC RFC

0.000s

SMTP server number

Skipped

Domain should have at least 2 SMTP servers according to the RFC. Note: You can use a service like altospam to solve this problem. Click on the link below to learn more

0.000s

MX IPs are differents

Skipped

The IP of the SMTP servers must be different if it is no longer reachable.

0.000s

MX IPs are in different class C

Skipped

The class C of every IPs should be differents

0.000s

SPF record is TXT type

Skipped

SPF record is no longer used, SPF must be into TXT record because many servers do not support SPF record. If SPF record exist, it should be the same as TXT

RFC

0.000s

Domain have only 1 SPF record

Skipped

To avoid issue with SPF, it is strongly recommended to configure only one.

0.000s

SPF version exists

Skipped

According to the RFC, the SPF version must be specified.

RFC

0.000s

SPF version at first position

Skipped

SPF has to start with version's tag.

RFC

0.000s

SPF "all" exists

Skipped

According to the RFC, the mecanism "all" must be specified in the SPF record, except if there is a Redirect tag.

RFC

0.000s

SPF "all" at last position

Skipped

The mecanism "All" has to be the last tag in SPF record. Be sure you don't have any dupplicates entry in your field.

RFC

0.000s

IPv4 & IPv6 syntaxes are corrects in SPF

Skipped

IPs must be valid, otherwise the SPF will be useless.

RFC

0.000s

SPF haven't PTR

Skipped

PTR has become obselete in SPF, should not be found in it.

RFC

0.000s

SPF "Redirect" at last position

Skipped

The mecanism "Redirect" has to be the last tag in SPF record. Be sure you don't have any dupplicates entry in your field.

RFC

0.000s

SPF records of type TXT & SPF are the same

Skipped

SPF record has become obselete, if it is configured then it must be the same as the one present in the TXT record

0.000s

PTR must be just before All statement

Skipped

The mecanism "PTR" has to be the last tag in SPF record. Be sure you don't have any dupplicates entry in your field.

0.000s

Domain have only 1 DMARC record

Skipped

To avoid issue with DMARC, it is strongly recommended to configure only one.

0.000s

DMARC version exist

Skipped

According to the RFC 7489 section 6.3, the DMARC version is required.

RFC

0.000s

DMARC version at first position

Skipped

According to the RFC 7489 section 6.3, the DMARC version must be the first tag in the list.

RFC

0.000s

DMARC procedure exists

Skipped

According to the RFC 7489 section 6.3, the procedure is required.

RFC

0.000s

DMARC "p" field is valid

Skipped

According to the RFC 7489 section 6.3, the procedure value must be none, quarantine or reject.

RFC

0.000s

DMARC "sp" field is valid

Skipped

According to the RFC 7489 section 6.3, the subdomain procedure value must be none, quarantine or reject.

RFC

0.000s

DMARC "pct" field is valid

Skipped

According to the RFC 7489 section 6.3, the percentage's value must be between 0 and 100.

RFC

0.000s

DMARC "adkim" field is valid

Skipped

According to the RFC 7489 section 6.3, the adkim tag value must be the letter R or S.

RFC

0.000s

DMARC "aspf" field is valid

Skipped

According to the RFC 7489 section 6.3, the aspf tag value must be the letter R or S.

RFC

0.000s

DMARC "rf" field is valid

Skipped

According to the RFC 7489 section 6.3, the RF tag's value must be afrf or iodef.

RFC

0.000s

DMARC "ri" field is valid

Skipped

According to the RFC 7489 section 6.3, the RI tag's value must be an integer.

RFC

0.000s

DMARC "ruf" field is valid

Skipped

According to the RFC 7489 section 6.3, the RUF tag's value must be a valid email.

RFC

0.000s

DMARC "rua" field is valid

Skipped

According to the RFC 7489 section 6.3, the RUA tag's value must be a valid email.

RFC

0.000s

DKIM version exist

Skipped

According to the RFC 6376 section 3.6.1, the DKIM version is required.

RFC

0.000s

DKIM Service Type is valid

Skipped

This Tag is optionnal but when use, it must be equal to "*" or "email".

RFC

0.000s

DKIM Testing flag is valid

Skipped

This Tag is optionnal but when use, it must be equal to "s", "y" or "y:s".

RFC

0.000s

DKIM public key is valid

Skipped

According to the RFC 6376 section 3.6.1, the public key is required and must be valid.

RFC

0.000s

DKIM public key is secure

Skipped

The size of the public key must be bigger than 1024 bits.

0.000s

Web

There is no web server. Please test 103.in-addr.arpa.

Url
http://22.245.103.in-addr.arpa/
Reachable
No
Url
https://22.245.103.in-addr.arpa/
Reachable
No

Domain have "A" field

Skipped

The domain must have an A field in order for the website to be accessible.

0.000s

Host "www" have "A" field

Skipped

WWW host is not required for a website, but it's better to have one.

0.000s

Domain have "AAAA" field

Skipped

It is highly recommended to have an IPv6 for the website.

0.000s

Host "www" have "AAAA" field

Skipped

If you configure a WWW host for your website, it is recommended to have an IPv6.

0.000s

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