You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The default "public contact" defaults need to be updated in alignment with this doc.
Acceptance criteria
Update the default Registrant, Tech, and Security contact values to be the same as the new Admin values except Security Email, which must remain as is (connected to what a user enters for a security contact in the registrar)
Verify that Registrant, Tech and Security contacts for all new domains will be redacted (except the Security Email, where present). Admin fields should follow their current pattern for redaction.
Additional context
The main outcome here is that the Admin contact values represent CISA and are all visible except the Admin email, and all other fields are redacted (except the Security Email, where a user has entered one).
The next sub-issue will fill in the Registrant values with actual registrant (org) details and make it visible in WHOIS/RDAP.
The text was updated successfully, but these errors were encountered:
removing the ac for the script "Write a script that updates each existing domain's Registrant/Admin/Tech/Security values to match the updated defaults and visibility". I will make a ticket for the script update as well
Sub-issue description
The default "public contact" defaults need to be updated in alignment with this doc.
Acceptance criteria
Registrant
,Tech
, andSecurity
contact values to be the same as the newAdmin
values exceptSecurity Email
, which must remain as is (connected to what a user enters for a security contact in the registrar)Registrant
,Tech
andSecurity
contacts for all new domains will be redacted (except theSecurity Email
, where present).Admin
fields should follow their current pattern for redaction.Additional context
The main outcome here is that the Admin contact values represent CISA and are all visible except the Admin email, and all other fields are redacted (except the Security Email, where a user has entered one).
The next sub-issue will fill in the
Registrant
values with actual registrant (org) details and make it visible in WHOIS/RDAP.The text was updated successfully, but these errors were encountered: