DNS Security (DNSSEC) Hashed Authenticated Denial of Existence
E746788
DNS Security (DNSSEC) Hashed Authenticated Denial of Existence is a DNSSEC extension that uses cryptographic hashing to provide verifiable, secure proof that a requested DNS name or type does not exist without revealing the full contents of a zone.
All labels observed (1)
| Label | Occurrences |
|---|---|
| DNS Security (DNSSEC) Hashed Authenticated Denial of Existence canonical | 1 |
How this entity was disambiguated
This entity first appeared as the object of triple T8619335 — resolving that mention is where its identity was fixed. The disambiguator weighed these candidate entities and picked the highlighted one (or “None”, minting a new entity). This is how homonymy is resolved: the same surface form can point to different entities.
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: DNS Security (DNSSEC) Hashed Authenticated Denial of Existence Context triple: [RFC 5155, title, DNS Security (DNSSEC) Hashed Authenticated Denial of Existence]
-
A.
Use of SHA-2 Algorithms with RSA in DNSKEY and RRSIG Resource Records for DNSSEC
"Use of SHA-2 Algorithms with RSA in DNSKEY and RRSIG Resource Records for DNSSEC" (RFC 5702) is an IETF standards-track document that specifies how to employ SHA-2 hash algorithms with RSA signatures in DNSSEC to enhance the security of DNS authentication.
-
B.
Protocol Modifications for the DNS Security Extensions
"Protocol Modifications for the DNS Security Extensions" is an IETF standards-track document (RFC 4035) that specifies how DNSSEC is operationally implemented and processed by DNS resolvers and authoritative servers.
-
C.
DNSSEC
DNSSEC (Domain Name System Security Extensions) is a suite of specifications that adds cryptographic authentication and integrity protection to DNS data to prevent attacks such as cache poisoning and spoofing.
-
D.
DNSSEC root key signing ceremony
The DNSSEC root key signing ceremony is a highly controlled, regularly scheduled cryptographic event where trusted personnel generate and manage the root cryptographic keys that secure the global Domain Name System.
-
E.
Clarifications to the DNS Specification
Clarifications to the DNS Specification is an IETF document (RFC 2181) that refines and corrects aspects of the original Domain Name System standards to ensure more consistent and interoperable DNS implementations.
- F. None of above. chosen
- G. Unsure - the case is ambiguous/there is not enough information to decide.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: DNS Security (DNSSEC) Hashed Authenticated Denial of Existence Target entity description: DNS Security (DNSSEC) Hashed Authenticated Denial of Existence is a DNSSEC extension that uses cryptographic hashing to provide verifiable, secure proof that a requested DNS name or type does not exist without revealing the full contents of a zone.
-
A.
Use of SHA-2 Algorithms with RSA in DNSKEY and RRSIG Resource Records for DNSSEC
"Use of SHA-2 Algorithms with RSA in DNSKEY and RRSIG Resource Records for DNSSEC" (RFC 5702) is an IETF standards-track document that specifies how to employ SHA-2 hash algorithms with RSA signatures in DNSSEC to enhance the security of DNS authentication.
-
B.
Protocol Modifications for the DNS Security Extensions
"Protocol Modifications for the DNS Security Extensions" is an IETF standards-track document (RFC 4035) that specifies how DNSSEC is operationally implemented and processed by DNS resolvers and authoritative servers.
-
C.
DNSSEC
DNSSEC (Domain Name System Security Extensions) is a suite of specifications that adds cryptographic authentication and integrity protection to DNS data to prevent attacks such as cache poisoning and spoofing.
-
D.
DNSSEC root key signing ceremony
The DNSSEC root key signing ceremony is a highly controlled, regularly scheduled cryptographic event where trusted personnel generate and manage the root cryptographic keys that secure the global Domain Name System.
-
E.
Clarifications to the DNS Specification
Clarifications to the DNS Specification is an IETF document (RFC 2181) that refines and corrects aspects of the original Domain Name System standards to ensure more consistent and interoperable DNS implementations.
- F. None of above. chosen
Statements (35)
| Predicate | Object |
|---|---|
| instanceOf |
DNS security mechanism
ⓘ
DNSSEC extension ⓘ |
| addressesProblem |
information leakage about non-requested domain names
ⓘ
zone enumeration risk ⓘ |
| basedOn | hash values of domain names ⓘ |
| category |
DNS privacy enhancement
ⓘ
DNSSEC denial-of-existence mechanism ⓘ |
| comparedTo |
NSEC
ⓘ
NSEC3 NERFINISHED ⓘ |
| designGoal |
limit disclosure of zone contents
ⓘ
support efficient DNSSEC validation ⓘ |
| doesNotRequire | disclosure of neighboring domain names in zone order ⓘ |
| ensures |
authenticity of denial-of-existence responses
ⓘ
integrity of denial-of-existence responses ⓘ |
| evidenceType | cryptographically verifiable proof of non-existence ⓘ |
| goal |
to avoid revealing full DNS zone contents
ⓘ
to prove non-existence of DNS names or types ⓘ |
| mitigates | offline zone-walking attacks ⓘ |
| operatesIn | Domain Name System (DNS) NERFINISHED ⓘ |
| operatesWith | DNS Security Extensions (DNSSEC) NERFINISHED ⓘ |
| operationalContext |
authoritative DNS servers
ⓘ
validating DNS resolvers ⓘ |
| property |
cryptographically secure
ⓘ
privacy-preserving ⓘ verifiable ⓘ |
| provides | authenticated denial of existence ⓘ |
| relatedConcept | authenticated denial of existence ⓘ |
| relatedTo |
DNS zone privacy
ⓘ
DNSSEC proof construction ⓘ |
| requires | DNSSEC validation by resolvers ⓘ |
| securityProperty |
protection against forged NXDOMAIN responses
ⓘ
resistance to zone enumeration ⓘ |
| usedFor |
proving that a DNS name does not exist
ⓘ
proving that a DNS record type does not exist at an existing name ⓘ |
| uses | cryptographic hashing ⓘ |
How these facts were elicited
The pipeline generated the facts above by prompting gpt-5.1 with this entity's name + description and the instruction below.
Instruction
You are a knowledge base construction expert. Given a subject entity and a description of it, return factual statements that you know for the subject as a JSON list of dictionaries(triples), where keys must be "subject", "predicate" and "object". The number of facts may be very high, between 25 to 50 or more, for very popular subjects. For less popular subjects, the number of facts can be very low, like 5 or 10. # Requirements - If you don't know the subject at all, return an empty list. - If the subject is not a named entity, return an empty list. - Include at least one triple where predicate is "instanceOf". - Do not get too wordy. - Separate several objects into multiple triples with one object.
Input
Subject: DNS Security (DNSSEC) Hashed Authenticated Denial of Existence Description of subject: DNS Security (DNSSEC) Hashed Authenticated Denial of Existence is a DNSSEC extension that uses cryptographic hashing to provide verifiable, secure proof that a requested DNS name or type does not exist without revealing the full contents of a zone.
Referenced by (1)
Full triples — surface form annotated when it differs from this entity's canonical label.