I wasn't referencing base64 encoding as that can be quickly decoded by anyone familiar enough to pick out what base64 looks like and I don't believe you can base64 encode a chunk of the source code inside a php file without doing something obscure to it like passing it through an eval statement or such.
I was referencing something like Zend Guard or ionCube PHP encoder.
As far as your function:
<?php
function call()
{
if( ini_get( 'allow_url_fopen' ) == '1' )
{
$response = file_get_contents( 'http://yourdomain.com/answer.php' );
if( $response != 'TRUE' )
{
//Cause some catastrophic death?
exit();
}
}
else
{
//Maybe implement a curl fail over if the curl extension is installed.
//But allow_url_fopen *SHOULD* be enabled by default;
}
}
answer.php
<?php
//Something to log $_SERVER variables as necessary.
//maybe referrer or maybe we are validating a key passed as a GET variable?
//if we're happy return true
echo 'TRUE';
Now if you were to use curl, you could actually have curl post an almost infinite amount of information to your server and then verify or log it etc.
This is very basic and untested but you should be able to grasp the general concept. If you wanted to get more advanced you could post xml and return xml or JSON etc.