HTTPS Socket

You can also connect by using the following HTTP(s) call.

The API commands are passed on through the parameters.

Connection data for the HTTPS-socket

Notice: If you do not add the parameter "s_opmode=OTE", you will connect to our live system and may be charged for operations.

# OT&E - URL
https://api.rrpproxy.net/api/call?s_opmode=OTE&s_login=demo&s_pw=demoote

# LIVE - URL
https://api.rrpproxy.net/api/call?s_login=demo&s_pw=demoote

Wget

wget -nv "https://api.rrpproxy.net/api/call?
s_opmode=OTE&s_login=demo&s_pw=demoote&command=checkdomain&domain=example.org" -O

[RESPONSE]
code = 210
description = Domain name available

queuetime=0
runtime=0.054
EOF
2009-11-06 09:25:45 URL:https://api.rrpproxy.net/api/call?
s_opmode=OTE&s_login=demo&s_pw=demoote&command=checkdomain&domain=example.org [90] -> "" [1]

Curl

curl "https://api.rrpproxy.net/api/call?
s_opmode=OTE&s_login=demo&s_pw=demoote&command=checkdomain&domain=example.org"

[RESPONSE]
code = 210
description = Domain name not available

queuetime=0
runtime=0.15
EOF