Generate
Back to Blog
Security audit checklist with anonymous test accounts verifying website protections

Not every website deserves your real email and personal information. Before committing real data, you can evaluate a site's security by registering with a synthetic identity first.

Why Test Before You Trust?

New websites, small businesses, and unfamiliar services may not have invested in security. Common red flags only become visible after you create an account:

  • Passwords emailed back in plaintext (means they are not hashed)
  • No HTTPS on login or registration pages
  • No two-factor authentication option
  • Password reset tokens that do not expire

Step-by-Step Security Check

  1. Generate a synthetic identity: Use Another.IO to create a test profile
  2. Register on the target site: Use the synthetic email and profile data
  3. Check the confirmation email: Does it contain your password in plaintext? That is a critical failure
  4. Test password reset: Request a reset and examine the email. Is there a time-limited token? Or a permanent link?
  5. Review the account settings: Can you enable two-factor? Can you download your data? Can you delete your account?
  6. Check privacy policy: Does it mention third-party data sharing?

Red Flags That Mean "Do Not Use Real Data"

  • Plaintext passwords: The site stores passwords without hashing. A breach would expose every user's password
  • No HTTPS: Your credentials are transmitted in the clear
  • Excessive data collection: A blog comment system should not need your phone number and address
  • No deletion option: If you cannot delete your account, your data stays forever

If the Site Passes

If the security checks look acceptable and you actually want to use the service long-term, you can create a new account with your real information. If it fails, you walk away knowing your real data was never at risk.