It would seem that 'n/a' just shows up whenever it can't grok what is going on. It could be a defect in the Netsol.pm parsing module, which can occur when data is misaligned. Here's the juicy bit from that module:

sub regex_created { '^Record created on (.*).$' }
sub regex_expires { '^Record expires on (.*).$' }
[download]

Personally, I'd put \s* wherever there could be space-like characters, since you never really know what they're going to think of doing next. Stuff tends to float. You've practically got to assume that where there is one space, there might be dozens. This might be better written as:

sub regex_created { '^\s*Record created on\s+(.*).' }
sub regex_expires { '^\s*Record expires on\s+(.*).' }
[download]

There's no trimming going on either, apparently:

my $text = $self->_send_to_sock( $sock );
# ...

$self->parse_text($text);
[download]

No evidence of s/^\s+//, which I would've figured had to be in there somewhere since Netsol records are typically indented with spaces.

I had a program that used to parse these things into little pieces, tearing apart even the address into city, state, zip, with a high degree of accuracy. I wonder if it's still workable.