Security

Keep templates useful, not dangerous.

Community templates are reviewed before publication. Submit and comment endpoints use Turnstile and rate limiting. Admin actions require a password-authenticated, short-lived secure session.

Template safety

SEOJump accepts public http(s) URL templates with fixed public domains and supported placeholders. Localhost, direct IP hosts, embedded credentials and unsupported placeholders are rejected for community submissions.

Do not submit secrets

Never place passwords, authentication tokens, cookies, private account URLs or other secrets inside a URL template or comment.

Report a vulnerability

For non-sensitive bugs, use the SEOJumpSite issue tracker ↗. For a security vulnerability, do not publish exploit details in a public issue; use GitHub private vulnerability reporting from the repository Security tab when available.