Well then you should try to do actual pentesting not with a live provider which might not be amused if you think you can/should perform a pentest of your website.
Start to set up your own lab. There are nice images out there for you to play around with and try out and improve your skills without doing any harm on live servers.
And as purehate mentioned, you should reread your TOS of the provider. Most don't even allow scanning.
Tiocfaidh ár lá
As someone else suggested purposefully triggering server errors (particularly WRT http servers/services) can be very revealing. Try directory listings, 404s, requests for active page types (blef.aspx blef.ashx etc.), purposefully try to cause a HTTP 500 error by submitting a form with some invalid parameters or with the expected parameters simply removed (you might need a personal proxy for this), try requests via HTTP 0.9 and 1.0 instead of 1.1, try HEAD requests instead of full GETs or POSTs, etc.
I'm a compulsive post editor, you might wanna wait until my post has been online for 5-10 mins before quoting it as it will likely change.
I know I seem harsh in some of my replies. SORRY! But if you're doing something illegal or posting something that seems to be obvious BS I'm going to call you on it.