HRIA guidelines for DNS abuse mitigation

Mon Mar 10 11:15:11 EET 2025

INTERNAL

INTERNAL

Hi Tapani,

Thank you for your feedback on the session! I’m really glad to hear it went well (it can be hard to gauge when participating remotely!).

On your suggestion, I completely agree that a resource with that kind of information (what each actor can vs cannot in the process of DNS abuse mitigation) would be helpful. This is something that @farzaneh badii<mailto:farzaneh.badii at gmail.com> and I can certainly think about developing as we work with registrars to finalize the set of guidelines/principles for DNS abuse mitigation.

This is something we could either integrate into the guidelines themselves or as a separate accompanying doc laying out the pathways for DNS abuse mitigation, which would show in what situations and at what stage of the DNS abuse mitigation the registrar should reach out to another actor (for example, if in the investigation phase it’s determined that the abuse is at the level of the hosting provider rather than at the domain level, the registrar should then contact them to address the issue).

Best,

Michaela

Michaela Nakayama Shapiro (she/her/hers)
Programme Officer - Censorship
[Logo.png]<https://www.article19.org>   Defending freedom of expression
and information
www.article19.org<https://www.article19.org>            Subscribe to our Newsletter<https://www.article19.org/ie-sign-up/>      [cid:newsletter_02744340-c607-4374-8a37-11b8b216096d.png] <https://www.article19.org/ie-sign-up>
Follow us
[Bluesky1x.png]<https://bsky.app/profile/article19.bsky.social>         [cid:facebook_2853baa0-f060-42e6-b448-6a8788c1b5dd.png] <https://www.facebook.com/article19org/>                [cid:youtube_ffe95af1-d962-4acd-ab59-4eb4ea07466e.png] <https://www.youtube.com/channel/UCDB6E_x0xRSfF62b872n9YQ>               [cid:linkedin_199dc89c-14aa-41cd-b2a7-37b8ae8d667d.png] <https://www.linkedin.com/company/article19>            [cid:instagram_05fbcc72-6df2-442b-8c34-146d0e9d8c41.png] <https://www.instagram.com/article19org/>              [cid:x_d21e0607-da5a-44a7-80c7-e2d86bc18a92.png] <https://twitter.com/intent/follow?screen_name=article19org>
[women-journalists-banner.jpeg]<https://www.article19.org/equally-safe/?mtm_campaign=Clicks%20on%20email%20signature%20banner>
From: NCSG-Discuss <NCSG-DISCUSS at LISTSERV.SYR.EDU> on behalf of Tapani Tarvainen <ncsg at TAPANI.TARVAINEN.INFO>
Date: Monday, 10 March 2025 at 15:41
To: NCSG-DISCUSS at LISTSERV.SYR.EDU <NCSG-DISCUSS at LISTSERV.SYR.EDU>
Subject: HRIA guidelines for DNS abuse mitigation
[You don't often get email from ncsg at tapani.tarvainen.info. Learn why this is important at https://aka.ms/LearnAboutSenderIdentification ]

Dear all,

On the session on developing human rights impact assessment guidelines
for DNS abuse mitigation Farzaneh had us do a little exercise in
hypothetical scenarios. It went very well, especially given how little
time there was, with some very illuminating ideas - like, demanding a
quick response from the registrant can be a problem if the registrant
is in jail - and if we keep pushing we could well come up with
actually useful guidelines.

One thing I wanted to highlight is our discussion about what the
registrar can do directly and where they'd have to reach out to the
hosting provider or dns provider. The latter we didn't actually
discuss much, it was only mentioned in passing, most people perhaps
thinking that dns provider is usually same as registrar. That is
indeed often the case (some registrars even insist on it) but not
always (some registrars don't even offer it as a service, notably
including ISNIC where ncsg.is is registered).

Perhaps it would be a good exercise to make a list of what things each
actor - registrar, dns provider, hosting provider - can and can't do.

--
Tapani Tarvainen
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ncsg.is/pipermail/ncsg-discuss/attachments/20250310/db47f5d0/attachment.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: logo_1c766458-35ee-431a-9a22-e00b47cd2091.png
Type: image/png
Size: 6889 bytes
Desc: logo_1c766458-35ee-431a-9a22-e00b47cd2091.png
URL: <http://lists.ncsg.is/pipermail/ncsg-discuss/attachments/20250310/db47f5d0/attachment.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: newsletter_02744340-c607-4374-8a37-11b8b216096d.png
Type: image/png
Size: 379 bytes
Desc: newsletter_02744340-c607-4374-8a37-11b8b216096d.png
URL: <http://lists.ncsg.is/pipermail/ncsg-discuss/attachments/20250310/db47f5d0/attachment-0001.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: bluesky1x_864ef831-9476-4116-88b8-2a3410741630.png
Type: image/png
Size: 788 bytes
Desc: bluesky1x_864ef831-9476-4116-88b8-2a3410741630.png
URL: <http://lists.ncsg.is/pipermail/ncsg-discuss/attachments/20250310/db47f5d0/attachment-0002.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: facebook_2853baa0-f060-42e6-b448-6a8788c1b5dd.png
Type: image/png
Size: 670 bytes
Desc: facebook_2853baa0-f060-42e6-b448-6a8788c1b5dd.png
URL: <http://lists.ncsg.is/pipermail/ncsg-discuss/attachments/20250310/db47f5d0/attachment-0003.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: youtube_ffe95af1-d962-4acd-ab59-4eb4ea07466e.png
Type: image/png
Size: 678 bytes
Desc: youtube_ffe95af1-d962-4acd-ab59-4eb4ea07466e.png
URL: <http://lists.ncsg.is/pipermail/ncsg-discuss/attachments/20250310/db47f5d0/attachment-0004.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: linkedin_199dc89c-14aa-41cd-b2a7-37b8ae8d667d.png
Type: image/png
Size: 720 bytes
Desc: linkedin_199dc89c-14aa-41cd-b2a7-37b8ae8d667d.png
URL: <http://lists.ncsg.is/pipermail/ncsg-discuss/attachments/20250310/db47f5d0/attachment-0005.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: instagram_05fbcc72-6df2-442b-8c34-146d0e9d8c41.png
Type: image/png
Size: 840 bytes
Desc: instagram_05fbcc72-6df2-442b-8c34-146d0e9d8c41.png
URL: <http://lists.ncsg.is/pipermail/ncsg-discuss/attachments/20250310/db47f5d0/attachment-0006.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: x_d21e0607-da5a-44a7-80c7-e2d86bc18a92.png
Type: image/png
Size: 895 bytes
Desc: x_d21e0607-da5a-44a7-80c7-e2d86bc18a92.png
URL: <http://lists.ncsg.is/pipermail/ncsg-discuss/attachments/20250310/db47f5d0/attachment-0007.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: women-journalists-banner_b1cece5c-a86d-452f-b9f8-9e72943680f6.jpeg
Type: image/jpeg
Size: 15471 bytes
Desc:  women-journalists-banner_b1cece5c-a86d-452f-b9f8-9e72943680f6.jpeg
URL: <http://lists.ncsg.is/pipermail/ncsg-discuss/attachments/20250310/db47f5d0/attachment.jpeg>