Graphic. OL3S™ logo.
Critical First Step
Official Licensed Stealth Site or Service™ (OL3S™) provides very important services for verification and authentication.
OFFICIAL SITE: This web page is a part of the official website of StealthPitch™. To make sure of this, please use the OL3S™ for verification and authentication. This is very important as we are under constant and intense attacks from various state and other hostile actors seeking to damage, subvert, capture and/or destroy the Site and/or Service. You can verify the information presented on the Site in multiple ways. We also provide public and private authentication.
Public Authentication Code (PubAC)
The Public Authentication Code (PubAC) is PUB-AUTH-P-1. Visit OL3S™ [ext.] or OL3S™ [ext. | no CA] to check that this code matches.
ANYONE CAN CHECK IT: The following is the PubAC:
PUB-AUTH-P-1
COMPARE AGAINST: Visit Kytaka™ / OL3S™ [ext.] or Kytaka™ / OL3S™ [ext. | no CA] to check that this code matches. Also, make sure that there has been no changes to this code or that it has changed consistently over time. You can use website archive services to check this out. Confirming that the PubAC is correct helps to verify that the general information presented on the Site is likely to be valid.
Official Current StealthPitch Address™ (OCSA™)
Before contacting us, please make sure that the address you use to contact us is correct. Visit OL3S™ [ext.] or OL3S™ [ext. | no CA] to check that this address matches. The Secrets™ policy means that we will never ask you to reveal any of your secrets before, during and/or after your use of the Service.20
VERY IMPORTANT: Before contacting us, please make sure that the address you use to contact us is correct. Visit OL3S™ [ext.] or OL3S™ [ext. | no CA] to check that this address matches. The Secrets™ policy means that we will never ask you to reveal any of your secrets before, during and/or after your use of the Service.20
CHECK OTHER SOURCES: Check the address from multiple sources. If you are interested in using the Service now or in the future you should look at the historical changes to the Site by checking website archive services (use the URL "https://stealthpitch.com/go-dark") or making your own screenshots etc. You can also search social media, forums and/or news about any changes regarding the Site and/or Service.20
ADDRESS: The following address, the Official Current StealthPitch Address™ (OCSA™ [pron.: ok-sa]) [v:ocsa.1], can be used in the private messenger Session:20
052e571a398a80dd4b6a349ed6cf1f8b5f2db278893e34ef9e42c7b4a9118ae873
This is the same address for manual copying (do not copy the spaces!):20
052e57
1a398a
80dd4b
6a349e
d6cf1f
8b5f2d
b27889
3e34ef
9e42c7
b4a911
8ae873
VERIFY: You may verify the following signed message that contains OCSA™ [please copy the full miniaturized formatted texts with the line feeds (LFs)]:20
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA384 The Official Current StealthPitch Address (OCSA): 052e571a398a80dd4b6a349ed6cf1f8b5f2db278893e34ef9e42c7b4a9118ae873 -----BEGIN PGP SIGNATURE----- iJUEARMJAB0WIQTESdVqmJTu+Y6r82uOZi1isM/TVwUCaE6ZwwAKCRCOZi1isM/T VwYGAXwOixwixyZ/B5Krky8Unzr7gn4RnU/kAkfOWgbwS2l2FwmAX/Dnbne90yfv JkXoyE4BfRBb2dRNSnrdoTbkBOCNAQgwN6m1BDFa8hZ06PyFI1hmbE4WQROXPB/R 8PBXz/uybg== =cbYO -----END PGP SIGNATURE-----
PUBLIC KEY: Start by importing the public key (PGP) by going to the terminal and writing "gpg --import" (free version of PGP) and then copying the following public key and pasting it (or right clicking and then selecting paste). Finally, press CTRL+D (and/or Enter or Return).20
-----BEGIN PGP PUBLIC KEY BLOCK----- mG8EaE6V/BMFK4EEACIDAwQOoTfbQHzsHmnK7l66lj8Bu91+RYPTjcxNIUCzR3wf 4DFd+TW8Esy//gJKQrIk+pA7KinFhB6BIyLK573xthFBbw8Cs0liB+1Q+hfhYD00 PrGW9xdBB6HbyZ0yCi9C8eC0PVN0ZWFsdGhQaXRjaCAoRUNDOlNPLCBOSVNUIFAt Mzg0KSA8bm8tcmVwbHlAc3RlYWx0aHBpdGNoLmNvbT6IswQTEwkAOxYhBMRJ1WqY lO75jqvza45mLWKwz9NXBQJoTpX8AhsDBQsJCAcCAiICBhUKCQgLAgQWAgMBAh4H AheAAAoJEI5mLWKwz9NXmtUBf1moXU81znpqjaTEvyHy+fF9gD2yn/PuoriM+28X hX8ArTl2DsUkfWKz2hkYRpfv0QF/SryeoWh4JWUqddYDLsJlcki1UyeuCKpEOn2l Eb8yzzuRdgGGFUT/0U511sPtl1Ft =Tzc4 -----END PGP PUBLIC KEY BLOCK-----
SCRIPT: Next, verify the signed message by copying the following script. The script contains the signed message and signature as the output of the echo command that is piped as input to the gpg command for verification.20
echo "-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA384 The Official Current StealthPitch Address (OCSA): 052e571a398a80dd4b6a349ed6cf1f8b5f2db278893e34ef9e42c7b4a9118ae873 -----BEGIN PGP SIGNATURE----- iJUEARMJAB0WIQTESdVqmJTu+Y6r82uOZi1isM/TVwUCaE6ZwwAKCRCOZi1isM/T VwYGAXwOixwixyZ/B5Krky8Unzr7gn4RnU/kAkfOWgbwS2l2FwmAX/Dnbne90yfv JkXoyE4BfRBb2dRNSnrdoTbkBOCNAQgwN6m1BDFa8hZ06PyFI1hmbE4WQROXPB/R 8PBXz/uybg== =cbYO -----END PGP SIGNATURE-----" | gpg --verify
FINISHED: Good? You should see a message stating that the signature is "good". Please note that the ECDSA key should be "C449D56A9894EEF98EABF36B8E662D62B0CFD357".20
gpg: Signature made Sun 15 Jun 2025 03:00:35 AM PDT gpg: using ECDSA key C449D56A9894EEF98EABF36B8E662D62B0CFD357 gpg: Good signature from "StealthPitch (ECC:SO, NIST P-384)" [ultimate]
TAMPERED: Bad? If you see a message stating that the signature is "bad", then it means that someone has tampered with the message or OCSA™. You may want to repeat the verification process to be sure that you did not accidentally change anything. If the verification fails again, then you should not use the address to contact us. Find out what happened.20
gpg: Signature made Sun 15 Jun 2025 03:00:35 AM PDT gpg: using ECDSA key C449D56A9894EEF98EABF36B8E662D62B0CFD357 gpg: BAD signature from "StealthPitch (ECC:SO, NIST P-384)" [ultimate]
ISSUES WITH SIGNATURE: Error? If you see a message stating that there is "error", then someone has tampered with the signature. You may want to repeat the verification process to be sure that you did not accidentally change anything. If the verification fails again, then you should not use the address to contact us. Find out what happened.20
gpg: CRC error; B46162 - 71B60E gpg: no signature found gpg: the signature could not be verified. Please remember that the signature file (.sig or .asc) should be the first file given on the command line.
HISTORY: Finally, please review different sources to confirm that OCSA™ and the public key have never changed (or that the changes were explained well). List of updates to OCSA™ and the public key (use the URL "https://stealthpitch.com/go-dark" when checking website archive services):20
No updates have been made so far.
Private Authentication Code (PriAC)
The Private Authentication Code (PriAC) enables you to make sure that in the future you are contacting us securely. The PriAC works by putting you in the driver's seat and is available for your current device or one other device, which does not presently exist. Take the opportunity to ask questions. If you are interested, please contact us and mention the PriAC.
FUTUREPROOF: If you are considering using the Service now or in the future you should definitely use this opportunity to get the PriAC and be able to contact us in the future using the same or another device. When contacting us, please select the most secure device you have, as you will only be able to use the code on that device later on or on one other device in the future.
The purpose of getting the PriAC is to make sure that you are contacting us using the correct address in the future or in scenarios where you are served a false address by hostile actors as an attack against you or us. With this single-use code, you will be able to reliably authenticate our identity in the future with a much higher likelihood of being accurate than doing searches in a sitution where the Site has been captured temporarily or permanently.
ASK YOUR QUESTIONS TOO: While getting your code, you might as well use the opportunity to ask questions that you have been wondering regarding the Site and/or Service. So, use OCSA™ to contact us on the Session app as per our instructions on the contact page and remember to mention that you wish to request the PriAC plus your questions or feedback.
Self-Destruct Code
If the self-destruct code (called KABOOM) is provided to you, as specified below, then you should immediately stop engaging with your contact regarding the Service Provider (SP). Alternatively, you should stop following the normal operational procedures.
KABOOM: If the self-destruct code (called KABOOM) is provided to you, then you should immediately stop engaging with your contact regarding the SP. Alternatively, you should stop following the normal operational procedures.
KABOOM can be provided to you through a number of ways. If KABOOM is provided to you, delete all message histories, delete all apps and/or software related to your digital use of the Service, destroy all physical cards and/or documents related to your physical use of the Service and establish a new contact with the SPs.
WHEN IT IS GONE: Note that the contact or SP may be taken out by us due to a number of reasons that we cannot list or discuss now or in the future. Once a contact or SP is taken out, it will be completely removed from service and can no longer exist, in its current form, to facilitate the Service. However, a cloned shadow version will remain and operate in isolation for a pre-defined duration that is partially randomized.
KABOOM will likely never be used in relation to your use of the Service, but it is good for you to know that there exists this added security feature. If the worst happens, we will provide you with free time extensions and/or upgrades to more than compensate for any time and/or effort wasted on your part.
FULL: The following is KABOOM (full) presented in letters and may appear in any part of the message (which does not include any special characters):
JRVJ JJPT KTAJ PJIJ ILJJ MLAL EWIW ELOW
SHORT: For some digital and physical forms of the Service, KABOOM (short) is presented with numbers (and only at the start of the message without any other content):
4168 4149
For most versions of the Service, KABOOM is automatically destroyed after two weeks (the "destruction notice" or "Deno"). Therefore, if you do not check your messages for that two week period, then you will never see the KABOOM message or hear from us again, until you re-establish connection with us, if applicable to you.
It is very important to understand that after the KABOOM is presented, no other contact or communication may ever be received from us, using the same contact or SP (in their current forms). So, if you receive any messages after receiving the KABOOM message, then those messages are not from us!