What carries the weight
Website encryption weighs most: recorded traffic is exposed today, and most sites can fix it with a setting.
| Category | What it covers | Weight |
|---|---|---|
| Website encryption | Whether your website agrees its keys in a quantum-safe way. | 40% |
| Certificates and signatures | The keys and signatures your site proves itself with. | 15% |
| Security settings | Protocol versions and ciphers, judged by today's standards. | 15% |
| Remote access | How your SSH servers agree keys; checked in the deep scan. | 10% |
| Spoofing protection and encrypted delivery, read from DNS. | 5% | |
| Login keys | The keys your login service publishes; not scored yet. | 5% |
| Signed DNS | Whether your domain's records are signed and validated. | 5% |
| Coverage | How much of your estate the scan could see; not scored yet. | 5% |
A category QuantGuard™ cannot check on your domain is left out, and its weight is shared among the rest.
Grades and their limits
Some findings cap the grade, whatever the rest scores.
| Grade | Score from |
|---|---|
| A | 90 |
| B | 80 |
| C | 65 |
| D | 50 |
| F | 0 |
| If | Score at most |
|---|---|
| TLS 1.0 or 1.1 is enabled | 89 |
| The website's key exchange is not post-quantum for current clients | 79 |
| An RSA key shorter than 2048 bits is in use | 64 |
What QuantGuard™ never penalises
- What nobody can fix yet
- Public authorities cannot issue post-quantum certificates, and DNS has no post-quantum signatures. QuantGuard™ tells you, and scores it as information.
- Good practice
- Email and HTTPS settings count as hygiene. QuantGuard™ never calls them quantum-vulnerable.
- Bot protection
- When a firewall blocks its web requests, QuantGuard™ says so. It is not a finding about you.
Want the reasoning behind your grade?
We walk your team through the findings, and what moves the score.
Every QuantGuard™ engagement is delivered by Dirhami Investment Technology Ltd.