- No spaces before or after the URL—manually copying from a document may introduce this issue.
- Must include the http(s):// protocol.
- Cannot contain a port number (indicating it is not a public-facing service).
- The hostname cannot be an IP address or an internal network host that is inaccessible externally.
If the format is correct but the URL is still blocked, it is likely due to our security screening process. To ensure uninterrupted service, PicSee must verify the safety of destination URLs and websites. Our policy follows a "better safe than sorry" approach, applying the highest security standards to protect legitimate users. Therefore, if we detect any potential risks, the system will automatically block the URL by default.
The following platforms are commonly blocked because users can freely edit content, making it difficult to verify authenticity, and JavaScript can be injected for further redirection:
- sites.google.com
- *.mystrikingly.com
- *.blogspot.com
Google Sites is blocked entirely because all users share the same domain, making it impossible to verify individual safety. However, if you can guarantee the content for a specific domain or subdomain (e.g., Strikingly allows setting a dedicated subdomain like picsee.mystrikingly.com), you can submit the URL to PicSee Support. After manual review and approval, the domain will be whitelisted, allowing future short links under that domain to be created freely on PicSee.
Additionally, if you use a branded short domain, it will have a unique security rating independent of other PicSee users, so it will not be subject to security blocking. However, PicSee reserves the final right to review content. If any URLs or accounts are determined to contain malicious content, they may still be blacklisted and restricted from use.