I develop products for VelikSoft Limited and have an active Apple Developer Program membership. Safari displays Fraudulent Website Warnings for four company-owned domains that we believe are false positives.
Domains and IPv4 addresses checked on October 17, 2026:
veliksoft.com - 77.110.106.89
tizigo.net - 77.110.106.89
vstranslate.net - 77.110.106.89
translatorphone.com - 94.228.163.126
The first three share a server. The newer translatorphone.com was placed on a different server and IP, but also received the warning shortly after launch. A shared IP alone therefore cannot explain all four warnings. The classification provider and trigger remain unknown.
The latest site is an informational translator-device project website, with no EXE downloads. Its homepage serves HTTPS with HTTP 200; www redirects to the same domain. A limited check of homepage references and the primary application script found local assets and interface interactions, without an executable download or automatic redirect to the old server. This is not an exhaustive security audit. It identifies VelikSoft Limited and links to our company site. Chrome opens it normally on this Mac.
Earlier checks of the older domains using Search Console and independent security services did not explain the Safari warnings. These historical checks are not current verdicts for the newer domain.
We already submitted Website Review requests multiple times and Feedback Assistant report FB24448660. Apple Developer Support case 102967798534 records contact events on September 19, September 30 and October 1, 2026. As of October 17, we have no substantive explanation or resolution. Telephone support is not a usable option for us.
Can an Apple engineer or a website owner who resolved a comparable issue advise:
-
How can we identify whether the warning comes from Apple, Google Safe Browsing or another provider?
-
Is there an owner-accessible diagnostic identifying the affected URL and reason?
-
Which escalation path works when Website Review and an existing support case have not produced a substantive response?
-
Can the existing case and FB report be routed for a manual review of all four domains?
-
If you resolved this, what evidence and contact channel actually led to a review?
Reproduction: open one of the affected HTTPS domains in Safari with Fraudulent Website Warning enabled; the red warning appears instead of the site. Safari 26 on macOS has been affected. I can provide exact current version details and further evidence through the support case if requested.
I am seeking an investigation and correction of any mistaken classification, not instructions to disable protection or bypass warnings.