The WHOIS page displays data pulled from Cloudflare's RDAP API including a domain's relevant contact information (Name, Organization, Address, Phone, Fax). Frequently all these contact fields are redacted for privacy which clutters the contact information section. To improve readability, when all contact information for a WHOIS contact is redacted, we should display a single line below each contact that says REDACTED FOR PRIVACY.
Current WHOIS page - all contact fields are individually listed
Desired WHOIS page display - single REDACTED FOR PRIVACY when all contact info is redacted
Acceptance criteria
[ ] Display a single line with the message REDACTED FOR PRIVACY for contacts with all their contact information redacted for privacy.
Additional context
This ticket introduces more dynamic handling of data on our static 11ty site. If someone else other than me (@erinysong) is working on this ticket, feel free to ping me to work out possible ways to include implement this on get.gov. There were some workarounds to support the WHOIS page's JS and data handling (sorry 😅) so feel free to either assign this ticket to me or ping me to give context to this ticket's assignee.
Issue description
The WHOIS page displays data pulled from Cloudflare's RDAP API including a domain's relevant contact information (Name, Organization, Address, Phone, Fax). Frequently all these contact fields are redacted for privacy which clutters the contact information section. To improve readability, when all contact information for a WHOIS contact is redacted, we should display a single line below each contact that says
REDACTED FOR PRIVACY.Reference the WHOIS page Figma
Current WHOIS page - all contact fields are individually listed
Desired WHOIS page display - single REDACTED FOR PRIVACY when all contact info is redacted
Acceptance criteria
REDACTED FOR PRIVACYfor contacts with all their contact information redacted for privacy.Additional context
This ticket introduces more dynamic handling of data on our static 11ty site. If someone else other than me (@erinysong) is working on this ticket, feel free to ping me to work out possible ways to include implement this on get.gov. There were some workarounds to support the WHOIS page's JS and data handling (sorry 😅) so feel free to either assign this ticket to me or ping me to give context to this ticket's assignee.
Links to other issues
No response