Can I use
?

DNSSEC and DANE

- OTHER

Method of validating a DNS response against a trusted root server. Mitigates various attacks that could reroute a user to a fake site while showing the real URL for the original site.

Chrome

  1. ◐ 4 - 5: Partial support
  2. ◐ 6 - 30: Partial support
  3. ◐ 31 - 130: Partial support
  4. ◐ 131: Partial support
  5. ◐ 132 - 134: Partial support

Edge

  1. ◐ 12 - 130: Partial support
  2. ◐ 131: Partial support

Safari

  1. ◐ 3.1 - 18.0: Partial support
  2. ◐ 18.1: Partial support
  3. ◐ 18.2 - TP: Partial support

Firefox

  1. ◐ 2 - 131: Partial support
  2. ◐ 132: Partial support
  3. ◐ 133 - 135: Partial support

Opera

  1. ◐ 9 - 113: Partial support
  2. ◐ 114: Partial support

IE

  1. ◐ 5.5 - 10: Partial support
  2. ◐ 11: Partial support

Chrome for Android

  1. ◐ 131: Partial support

Safari on iOS

  1. ◐ 3.2 - 18.0: Partial support
  2. ◐ 18.1: Partial support
  3. ◐ 18.2: Partial support

Samsung Internet

  1. ◐ 4 - 25: Partial support
  2. ◐ 26: Partial support

Opera Mini

  1. ◐ all: Partial support

Opera Mobile

  1. ◐ 10 - 12.1: Partial support
  2. ◐ 80: Partial support

UC Browser for Android

  1. ◐ 15.5: Partial support

Android Browser

  1. ◐ 2.1 - 4.4.4: Partial support
  2. ◐ 131: Partial support

Firefox for Android

  1. ◐ 132: Partial support

QQ Browser

  1. ◐ 14.9: Partial support

Baidu Browser

  1. ◐ 13.52: Partial support

KaiOS Browser

  1. ◐ 2.5: Partial support
  2. ◐ 3: Partial support

Browsers have generally decided to not implement DNSSEC validation because the added complexity outweighs the improvements to the browser. DNSSEC is still useful as it is widely used to protect delivery of records between DNS servers, only failing to protect the delivery from the last DNS server to the browser.

Certificate transparency is widely used and tries to provide the same security as DNSSEC but by very different means.

Resources:
Chrome implementation bug
Firefox implementation bug
Wikipedia - DNSSEC