Editing Transport Layer Security (section)

====Alert protocol====
This record should normally not be sent during normal handshaking or application exchanges. However, this message can be sent at any time during the handshake and up to the closure of the session. If this is used to signal a fatal error, the session will be closed immediately after sending this record, so this record is used to give a reason for this closure. If the alert level is flagged as a warning, the remote can decide to close the session if it decides that the session is not reliable enough for its needs (before doing so, the remote may also send its own signal).

{|class="wikitable"style=width:95%;text-align:center
|+TLS record format for alert protocol
|-
!scope=col|Offset
!scope=col style=width:22%|Byte+0
!scope=col style=width:22%|Byte+1
!scope=col style=width:22%|Byte+2
!scope=col style=width:22%|Byte+3
|-
!scope=row|Byte<br />0
|style=background:#dfd|21
|colspan=3{{N/A}}
|-
!scope=row rowspan=2|Bytes<br />1–4
|colspan=2 style=background:#fdd|Legacy version
|colspan=2 style=background:#fdd|Length
|-style=background:#fdd
|''(Major)''
|''(Minor)''
|0
|2
|-
!Bytes<br />5–6
|Level
|Description
|colspan=2{{N/A}}
|-
!Bytes<br />''7''–(''p''−1)
|colspan=4 style=background:#fbb|[[message authentication code|MAC]] (optional)
|-
!Bytes<br />''p''–(''q''−1)
|colspan=4 style=background:#fbb|Padding (block ciphers only)
|}

;Level
:This field identifies the level of alert. If the level is fatal, the sender should close the session immediately. Otherwise, the recipient may decide to terminate the session itself, by sending its own fatal alert and closing the session itself immediately after sending it. The use of Alert records is optional, however if it is missing before the session closure, the session may be resumed automatically (with its handshakes).
:Normal closure of a session after termination of the transported application should preferably be alerted with at least the ''Close notify'' Alert type (with a simple warning level) to prevent such automatic resume of a new session. Signalling explicitly the normal closure of a secure session before effectively closing its transport layer is useful to prevent or detect attacks (like attempts to truncate the securely transported data, if it intrinsically does not have a predetermined length or duration that the recipient of the secured data may expect).
{|class="wikitable"style=width:90%
|+Alert level types
|-
!scope=col|Code
!scope=col|Level type
!scope=col|Connection state
|-
!scope=row|1
|style=background:yellow;text-align:center|'''warning'''
|connection or security may be unstable.
|-
!scope=row|2
|style=background:red;text-align:center|'''fatal'''
|connection or security may be compromised, or an unrecoverable error has occurred.
|}

;Description
:This field identifies which type of alert is being sent.
{|class="wikitable"style=width:90%
|+Alert description types
|-
!scope=col|Code
!scope=col|Description
!scope=col|Level types
!scope=col|Note
|-
!scope=row|0
|Close notify
|style=background:orange;text-align:center|'''warning'''/'''fatal'''
|
|-
!scope=row|10
|Unexpected message
|style=background:red;text-align:center|'''fatal'''
|
|-
!scope=row|20
|Bad record MAC
|style=background:red;text-align:center|'''fatal'''
|Possibly a bad SSL implementation, or payload has been tampered with e.g. FTP firewall rule on [[FTPS]] server.
|-
!scope=row|21
|Decryption failed
|style=background:red;text-align:center|'''fatal'''
|TLS only, reserved
|-
!scope=row|22
|Record overflow
|style=background:red;text-align:center|'''fatal'''
|TLS only
|-
!scope=row|30
|Decompression failure
|style=background:red;text-align:center|'''fatal'''
|
|-
!scope=row|40
|Handshake failure
|style=background:red;text-align:center|'''fatal'''
|
|-
!scope=row|41
|No certificate
|style=background:orange;text-align:center|'''warning'''/'''fatal'''
|SSL 3.0 only, reserved
|-
!scope=row|42
|Bad certificate
|style=background:orange;text-align:center|'''warning'''/'''fatal'''
|
|-
!scope=row|43
|Unsupported certificate
|style=background:orange;text-align:center|'''warning'''/'''fatal'''
|e.g. certificate has only server authentication usage enabled and is presented as a client certificate
|-
!scope=row|44
|Certificate revoked
|style=background:orange;text-align:center|'''warning'''/'''fatal'''
|
|-
!scope=row|45
|Certificate expired
|style=background:orange;text-align:center|'''warning'''/'''fatal'''
|Check server certificate expire also check no certificate in the chain presented has expired
|-
!scope=row|46
|Certificate unknown
|style=background:orange;text-align:center|'''warning'''/'''fatal'''
|
|-
!scope=row|47
|Illegal parameter
|style=background:red;text-align:center|'''fatal'''
|
|-
!scope=row|48
|Unknown CA ([[Certificate authority]])
|style=background:red;text-align:center|'''fatal'''
|TLS only
|-
!scope=row|49
|Access denied
|style=background:red;text-align:center|'''fatal'''
|TLS only – e.g. no client certificate has been presented (TLS: Blank certificate message or SSLv3: No Certificate alert), but server is configured to require one.
|-
!scope=row|50
|Decode error
|style=background:red;text-align:center|'''fatal'''
|TLS only
|-
!scope=row|51
|Decrypt error
|style=background:orange;text-align:center|'''warning'''/'''fatal'''
|TLS only
|-
!scope=row|60
|Export restriction
|style=background:red;text-align:center|'''fatal'''
|TLS only, reserved
|-
!scope=row|70
|Protocol version
|style=background:red;text-align:center|'''fatal'''
|TLS only
|-
!scope=row|71
|Insufficient security
|style=background:red;text-align:center|'''fatal'''
|TLS only
|-
!scope=row|80
|Internal error
|style=background:red;text-align:center|'''fatal'''
|TLS only
|-
!scope=row|86
|Inappropriate fallback
|style=background:red;text-align:center|'''fatal'''
|TLS only
|-
!scope=row|90
|User canceled
|style=background:red;text-align:center|'''fatal'''
|TLS only
|-
!scope=row|100
|No renegotiation
|style=background:yellow;text-align:center|'''warning'''
|TLS only
|-
!scope=row|110
|Unsupported extension
|style=background:yellow;text-align:center|'''warning'''
|TLS only
|-
!scope=row|111
|Certificate unobtainable
|style=background:yellow;text-align:center|'''warning'''
|TLS only
|-
!scope=row|112
|Unrecognized name
|style=background:orange;text-align:center|'''warning'''/'''fatal'''
|TLS only; client's [[Server Name Indication|Server Name Indicator]] specified a [[hostname]] not supported by the server
|-
!scope=row|113
|Bad certificate status response
|style=background:red;text-align:center|'''fatal'''
|TLS only
|-
!scope=row|114
|Bad certificate hash value
|style=background:red;text-align:center|'''fatal'''
|TLS only
|-
!scope=row|115
|Unknown [[Pre-shared key|PSK]] identity (used in [[TLS-PSK]] and [[TLS-SRP]])
|style=background:red;text-align:center|'''fatal'''
|TLS only
|-
!scope=row|116
|Certificate required
|style=background:red;text-align:center|'''fatal'''
|TLS version 1.3 only
|-
!scope=row|120 or 255
|No application protocol
|style=background:red;text-align:center|'''fatal'''
|TLS version 1.3 only
|}