Resolution for Chrome's lookalike warning for bungie-net.github.io

[braddadocio]

Chrome (or rather the Chromium engine) has a warning that it presents to users visiting the https://bungie-net.github.io/ site, prompting the user to visit bungie.net instead.

They offer some documentation on this and how to mitigate the problem for legitimate cases. There's a manual submission form, and I presume that is reviewed by a real person. So it isn't reliable as to whether a submission would be approved or not. But there's also an automated means to associate the two domains and is also documented on that page under the "automated removal" section.

The solution involves adding a resource for both the bungie.net and bungie-net.github.io domains for this path: /.well-known/assetlinks.json. It appears that bungie.net already has a resource by that name, but it would require an additional entry.

The bungie.net assetlinks.json would have to be updated to (the first entry in the array here is the existing content; if it changes after this post, adjust accordingly... the relevant additions are the two entries below it).

[
    {
        "relation": [
            "delegate_permission/common.handle_all_urls"
        ],
        "target": {
            "namespace": "android_app",
            "package_name": "com.bungieinc.bungiemobile.debug",
            "sha256_cert_fingerprints": [
                "1D:A7:0B:01:00:94:86:92:C3:E8:58:FE:24:0D:54:1C:5E:86:F2:A0:26:4D:B9:B9:FA:D4:F5:06:7B:16:76:AD"
            ]
        }
    },
    {
        "relation": ["lookalikes/allowlist"],
        "target" : { "namespace": "web", "site": "https://bungie.net"}
    },
    {
        "relation": ["lookalikes/allowlist"],
        "target" : { "namespace": "web", "site": "https://bungie-net.github.io"}
    }
]

The bungie-net.github.io domain does not have this resource already. To publish it, this repository would need to include this entry in a top-level config.yml file:

include: [".well-known"]

Then, add a .well-known top-level directory, and include a file named assetlinks.json in it, with this:

[
    {
        "relation": ["lookalikes/allowlist"],
        "target" : { "namespace": "web", "site": "https://bungie.net"}
    },
    {
        "relation": ["lookalikes/allowlist"],
        "target" : { "namespace": "web", "site": "https://bungie-net.github.io"}
    }
]

[braddadocio]

I did attempt to do a manual report to the Chromium project for this lookalike domain. They have declined the request.