NYSSR.NET / RESOURCES
License Status Verification
Check the validity and key details of a commercial license for nyssr.net or RemoteSkin by entering the license number into the official License Check database.

License lookup is not active yet.
The database query is currently disabled because no commercial licenses have been issued. For the first pilots, license status will be confirmed manually by email. A secure online verification service will be announced here once the licensing terms, privacy rules, and technical safeguards are finalized.
A license lookup can be useful for customers who operate several nodes and need to confirm the status of an issued license. It is not a public customer database.
What the future service may show
After the service has been implemented, a license ID supplied by sillysky software labs may return limited information such as:
- license status;
- license type;
- covered product or node scope;
- validity period and renewal date;
- licensee or organization name, where appropriate.
The exact fields and display rules will be defined before the first commercial license is issued.
Privacy by design
The public website remains completely static. License records, customer details, and the verification logic must live behind a separate HTTPS endpoint or a protected service. The static page must never contain the license database and must not expose a list of valid IDs.
The future service should reveal no more information than necessary. A license ID should be treated as a secret-like identifier, not as a password or proof of identity. Customers should receive a clear result such as valid, expired, revoked, or not found, with only the contractual details needed for verification.
Technical direction
A small API around a private database is more appropriate than trying to make Hugo dynamic. Hugo will continue to generate and deploy the public website on the build server. The lookup service can be deployed separately and linked from this page or embedded through a narrowly scoped form later.
Possible implementation stages:
- continue with manual verification by email for the first pilots;
- define the license record and privacy rules;
- implement a minimal read-only API with rate limiting and audit logging;
- add a small form that sends the ID to that API without placing database credentials in the Hugo site;
- publish the verification service only after the licensing terms and data protection review are complete.
No public lookup endpoint is active yet. No commercial license has been sold, and there are currently no customer records to verify.