<html xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<meta name="Generator" content="Microsoft Word 15 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:Helvetica;
panose-1:0 0 0 0 0 0 0 0 0 0;}
@font-face
{font-family:Wingdings;
panose-1:5 0 0 0 0 0 0 0 0 0;}
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Roboto;
panose-1:2 0 0 0 0 0 0 0 0 0;}
@font-face
{font-family:-webkit-standard;
panose-1:2 11 6 4 2 2 2 2 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:#0563C1;
text-decoration:underline;}
span.EmailStyle19
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
/* List Definitions */
@list l0
{mso-list-id:718209262;
mso-list-template-ids:-1578568580;}
@list l0:level1
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l0:level2
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:1.0in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:"Courier New";
mso-bidi-font-family:"Times New Roman";}
@list l0:level3
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:1.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l0:level4
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:2.0in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l0:level5
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:2.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l0:level6
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:3.0in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l0:level7
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:3.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l0:level8
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:4.0in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l0:level9
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:4.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l1
{mso-list-id:718940028;
mso-list-template-ids:-552059430;}
@list l1:level1
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l1:level2
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:1.0in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l1:level3
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:1.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l1:level4
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:2.0in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l1:level5
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:2.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l1:level6
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:3.0in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l1:level7
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:3.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l1:level8
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:4.0in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l1:level9
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:4.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l2
{mso-list-id:1164056088;
mso-list-template-ids:-1581888134;}
@list l2:level1
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l2:level2
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:1.0in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:"Courier New";
mso-bidi-font-family:"Times New Roman";}
@list l2:level3
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:1.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l2:level4
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:2.0in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l2:level5
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:2.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l2:level6
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:3.0in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l2:level7
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:3.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l2:level8
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:4.0in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l2:level9
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:4.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
ol
{margin-bottom:0in;}
ul
{margin-bottom:0in;}
--></style>
</head>
<body lang="EN-US" link="#0563C1" vlink="purple">
<div class="WordSection1">
<p class="MsoNormal">Re-sending. Seems to have been blocked…<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b><span style="font-size:12.0pt;color:black">From: </span></b><span style="font-size:12.0pt;color:black">Denise Michel <denisemichel@fb.com><br>
<b>Date: </b>Wednesday, April 8, 2020 at 8:38 AM<br>
<b>To: </b>SSR2 <ssr2-review@icann.org><br>
<b>Subject: </b>FYI - COVID-19, WHOIS, and the Pressing Need for Help With Domain Name System Abuse<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<p class="MsoNormal"><span style="font-family:-webkit-standard;color:black">This blog addresses domain name abuse, abuse of domains associated with the COVID-19 crisis, and how ICANN has failed to respond.</span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-family:-webkit-standard;color:black"> </span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-family:-webkit-standard;color:black"><a href="https://urldefense.proofpoint.com/v2/url?u=http-3A__www.circleid.com_posts_20200407-2Dcovid19-2Dwhois-2Dand-2Dpressing-2Dneed-2Dfor-2Dhelp-2Dwith-2Ddns-2Dabuse_&d=DwMFaQ&c=udBTRvFvXC5Dhqg7UHpJlPps3mZ3LRxpb6__0PomBTQ&r=7di7LNGSGzmwxp3loB34zbzCEdPQRyxqVsoK6jh4TjE&m=wlU0PSTriP7qkrQ0O9CYLUhdG9mcqskA1_7p26ag89A&s=tyPtyVL-mBHe4cTtQPMvyQO6etDN7kcFop_CEv_IjBM&e=" target="_blank">http://www.circleid.com/posts/20200407-covid19-whois-and-pressing-need-for-help-with-dns-abuse/</a></span><o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal" style="margin-bottom:15.0pt;line-height:31.5pt;background:white">
<b><span style="font-size:25.5pt;font-family:Roboto;color:black;letter-spacing:-.1pt"><a href="http://www.circleid.com/posts/20200407-covid19-whois-and-pressing-need-for-help-with-dns-abuse/"><span style="color:#003366">COVID-19, WHOIS, and the Pressing Need
for Help With Domain Name System Abuse</span></a></span></b><o:p></o:p></p>
<p class="MsoNormal" style="background:white"><span style="font-size:10.0pt;font-family:Helvetica;color:#666666">By <a href="http://www.circleid.com/members/552/"><b><span style="color:#003366;text-decoration:none">Mason Cole</span></b></a></span><o:p></o:p></p>
<p class="MsoNormal" style="margin-left:0in;text-indent:-.25in;line-height:14.25pt;mso-list:l0 level1 lfo2;background:white">
<![if !supportLists]><span style="font-size:10.0pt;font-family:Symbol"><span style="mso-list:Ignore">·<span style="font:7.0pt "Times New Roman"">
</span></span></span><![endif]><span style="font-size:10.0pt;font-family:Helvetica;color:#666666">Apr 07, 2020 2:27 PM PDT</span><o:p></o:p></p>
<p class="MsoNormal" style="background:white"><span style="font-size:10.0pt;font-family:Helvetica;color:#666666"> </span><o:p></o:p></p>
<p class="MsoNormal" style="line-height:19.5pt;background:white"><span style="font-size:12.0pt;font-family:Helvetica;color:black">As widely reported, and not surprising, <a href="https://arstechnica.com/information-technology/2020/03/the-internet-is-drowning-in-covid-19-related-malware-and-phishing-scams/"><span style="color:#663366">the
internet is swimming in COVID-19 online scams</span></a>. Criminals, accustomed to rapidly grabbing online territory during times of crisis and profiting from public fear, are working overtime in the face of the coronavirus. Unfortunately, ICANN's failure
to enforce its minimal WHOIS and DNS abuse requirements has resulted in delayed mitigation efforts at a time when swift responses are needed to protect the public from COVID-19 scams.</span><o:p></o:p></p>
<p class="MsoNormal" style="line-height:19.5pt;background:white"><span style="font-size:12.0pt;font-family:Helvetica;color:black"> </span><o:p></o:p></p>
<p class="MsoNormal" style="line-height:19.5pt;background:white"><span style="font-size:12.0pt;font-family:Helvetica;color:black">For years, ICANN Org has been challenged to proactively address DNS abuse — with calls to action intensifying over the course of
the past two ICANN meetings. The problem, already acute, is now even more visible due to the pandemic and is exacerbating this tragic public health crisis. ICANN Org has the tools, via enforcement of its contracts with registrars and registries, to do something
about this — but it's not. The COVID crisis calls for an immediate response from the ICANN Board to ensure that ICANN's contracts are enforced, timely WHOIS access is granted, and ICANN's operations actively support DNS abuse mitigation efforts, to the greatest
extent possible.</span><o:p></o:p></p>
<p class="MsoNormal" style="line-height:19.5pt;background:white"><span style="font-size:12.0pt;font-family:Helvetica;color:black"> </span><o:p></o:p></p>
<p class="MsoNormal" style="line-height:19.5pt;background:white"><span style="font-size:12.0pt;font-family:Helvetica;color:black">Here's the proof: In the domain name sector, over the course of the last several weeks, <a href="https://unit42.paloaltonetworks.com/covid19-cyber-threats/"><span style="color:#663366">security
researchers have documented a spike in the number of coronavirus-related domains</span></a> — more than 100,000 registered in March alone — with attacks sourced from those registrations growing in conjunction with the disease's spread. An estimated half (and
probably more by now) were <a href="https://blog.checkpoint.com/2020/03/05/update-coronavirus-themed-domains-50-more-likely-to-be-malicious-than-other-domains/"><span style="color:#663366">identified as sources of malware or other harms</span></a>. It's bad
enough that even as her state is reeling from the medical crisis, <a href="https://ag.ny.gov/sites/default/files/3.19.20_letter_concerning_godaddy_and_coronavirus.pdf"><span style="color:#663366">New York's attorney general had to ask registrars what they're
doing to protect the online public</span></a> from cybercriminals.</span><o:p></o:p></p>
<p class="MsoNormal" style="line-height:19.5pt;background:white"><span style="font-size:12.0pt;font-family:Helvetica;color:black"> </span><o:p></o:p></p>
<p class="MsoNormal" style="line-height:19.5pt;background:white"><span style="font-size:12.0pt;font-family:Helvetica;color:black">What started as a few registrations a day earlier this year are now thousands of new domains popping up daily, containing terms
like coronavirus, COVID, pandemic, virus, or vaccine. Few, if any, of these registrations are for domain names meant to be authentic, authoritative sources of information about the ongoing public health crisis. Case in point: CoronaVirusApp[.]site is a documented
ransomware site that distributes malware by holding targeted systems hostage. Registrants like these seek to capitalize on the public's fear to, at best, propagate misinformation or, at worst, spread their own versions of harm. Some are even <a href="https://www.washingtonpost.com/national-security/coronavirus-vaccine-fraud-case-justice-department/2020/03/22/3ac4014e-6c72-11ea-b148-e4ce3fbd85b5_story.html"><span style="color:#663366">claiming
to provide vaccines against the virus</span></a>. Just as the world is facing a pandemic, so is the online world facing a spreading case of domain name system abuse.</span><o:p></o:p></p>
<p class="MsoNormal" style="line-height:19.5pt;background:white"><span style="font-size:12.0pt;font-family:Helvetica;color:black"> </span><o:p></o:p></p>
<p class="MsoNormal" style="line-height:19.5pt;background:white"><span style="font-size:12.0pt;font-family:Helvetica;color:black">Unfortunately, if one wanted to stop the harm even <i>after</i> these types of domains go into use, no one can look up ownership
and other relevant WHOIS data details for these parasitic names, thanks to ICANN's overly restrictive WHOIS policy, <a href="http://www.interisle.net/sub/DomainRegistrationData.pdf"><span style="color:#663366">widespread non-compliance by registrars and registries</span></a>,
and ICANN's refusal to implement its own privacy/proxy policy. Compounding the problem is the fact that it's highly unlikely registrars bothered to validate the information provided by these registrants because ICANN has refused to require even the simplest
steps to validate information at the point of registration. As a result, the WHOIS system — the number one instrument available to know who's behind a domain name and to track scammers (a legitimate and legal investigatory use of WHOIS to mitigate abuse, even
under GDPR) — has been rendered useless.</span><o:p></o:p></p>
<p class="MsoNormal" style="line-height:19.5pt;background:white"><span style="font-size:12.0pt;font-family:Helvetica;color:black"> </span><o:p></o:p></p>
<p class="MsoNormal" style="line-height:19.5pt;background:white"><span style="font-size:12.0pt;font-family:Helvetica;color:black">For several years, a majority of the stakeholder groups in ICANN (even many of the world's governments) have pleaded with ICANN's
Board, staff, and community to do something about DNS abuse — at least, ramp up WHOIS compliance efforts. So far, however, the response has been underwhelming. While <a href="https://rrsg.org/wp-content/uploads/2020/03/Registrar-approaches-to-the-COVID-19-Crisis.pdf"><span style="color:#663366">a
recent voluntary effort by some registrars against COVID-related domains</span></a> is a positive step, it's clear that those still harboring the bad guys don't care about frameworks — and that this cohort of registrars won't ever take part in voluntary work
to address DNS abuse. Still, while ICANN abrogates its responsibilities and tries to defend its limited and largely ineffectual actions, the problem continues to grow unabated and unchecked.</span><o:p></o:p></p>
<p class="MsoNormal" style="line-height:19.5pt;background:white"><span style="font-size:12.0pt;font-family:Helvetica;color:black"> </span><o:p></o:p></p>
<p class="MsoNormal" style="line-height:19.5pt;background:white"><span style="font-size:12.0pt;font-family:Helvetica;color:black">When queried during ICANN67 about its anemic response to such a growing problem, ICANN executives <i>could</i> have said, "You're
right, we're in a unique position to do more about this — not only can we, we're obligated to, so let's get to work together." Instead, we heard meandering replies, again pointing to community voluntary initiatives aimed at curtailing abuse. Voluntary statements
targeting political hot-button abuses of domains with no accountability mechanisms is not a substitute for fixing WHOIS, ensuring compliance with ICANN's contracts, and improving DNS abuse mitigation.</span><o:p></o:p></p>
<p class="MsoNormal" style="line-height:19.5pt;background:white"><span style="font-size:12.0pt;font-family:Helvetica;color:black"> </span><o:p></o:p></p>
<p class="MsoNormal" style="line-height:19.5pt;background:white"><span style="font-size:12.0pt;font-family:Helvetica;color:black">It's abundantly clear that it's time for ICANN to stop toying with the abuse concept and actually do something meaningful. The
recently published <a href="http://www.interisle.net/sub/DomainRegistrationData.pdf"><span style="color:#663366">findings of the security research-focused Interisle Consulting Group</span></a> following its review of WHOIS practices among registrars highlights
the severity of the problem. As documented in the report, Interisle found that registrars failed basic inquiries regarding WHOIS accessibility and compliance 40% of the time, and that there were notable usability issues in an additional 16% of cases. A significant
percentage of registrars do not fully comply with ICANN's Temporary Specification that was adopted in 2018 to address GDPR concerns. This widespread non-compliance with ICANN's contractual policies involving both large and small registrars is alarming, and
points to failures in ICANN's compliance procedures. This study illustrated clear "failures to provide the access, predictability, and reliability that ICANN exists to deliver, and that registrars are obligated to provide." In the face of these statistics,
it's hard to argue otherwise.</span><o:p></o:p></p>
<p class="MsoNormal" style="line-height:19.5pt;background:white"><span style="font-size:12.0pt;font-family:Helvetica;color:black"> </span><o:p></o:p></p>
<p class="MsoNormal" style="line-height:19.5pt;background:white"><span style="font-size:12.0pt;font-family:Helvetica;color:black">Worse yet, these failures created significant obstacles for those responding the COVID-19 scams. As noted by Interisle, "[t]he
pandemic has led to an explosion of cybercrime, preying upon a population desperate for safety and reassurance, and that 'legal authorities are currently struggling with this wave of domain-based crime.'"</span><o:p></o:p></p>
<p class="MsoNormal" style="line-height:19.5pt;background:white"><span style="font-size:12.0pt;font-family:Helvetica;color:black"> </span><o:p></o:p></p>
<p class="MsoNormal" style="line-height:19.5pt;background:white"><span style="font-size:12.0pt;font-family:Helvetica;color:black">There's a way out of this mess. ICANN Org can:</span><o:p></o:p></p>
<ul style="margin-top:0in" type="disc">
<li class="MsoNormal" style="color:black;line-height:18.0pt;mso-list:l2 level1 lfo5;background:white">
<span style="font-size:12.0pt;font-family:Helvetica">enforce its contracts and, where needed, strengthen the contracts it finds toothless — contracts that are currently under negotiation — in order to target industry players that don't participate in DNS abuse
mitigation efforts;</span><o:p></o:p></li><li class="MsoNormal" style="color:black;line-height:18.0pt;mso-list:l2 level1 lfo5;background:white">
<span style="font-size:12.0pt;font-family:Helvetica">issue advisories or guidance to contracted parties regarding options available for mitigation of DNS abuse; and</span><o:p></o:p></li><li class="MsoNormal" style="color:black;line-height:18.0pt;mso-list:l2 level1 lfo5;background:white">
<span style="font-size:12.0pt;font-family:Helvetica">take action on overdue matters, such as the unanimously-supported <a href="https://www.icann.org/resources/pages/ppsai-2016-08-18-en"><span style="color:#663366">privacy/proxy accreditation policy</span></a>,
approved years ago but never implemented, and the cross-field validation requirement set in 2013 but also never implemented.</span><o:p></o:p></li></ul>
<p class="MsoNormal" style="line-height:19.5pt;background:white"><span style="font-size:12.0pt;font-family:Helvetica;color:black"> </span><o:p></o:p></p>
<p class="MsoNormal" style="line-height:19.5pt;background:white"><span style="font-size:12.0pt;font-family:Helvetica;color:black">What ICANN <i>cannot</i> do is continue to stand idly by, opening and resolving a few single, low-level complaint tickets, while
the real problem persists in greater and greater magnitude and is perpetrated by known bad actors. Nor can ICANN Org, including its Board, continue to point to voluntary industry best practice "frameworks" as a replacement for its own responsibilities and
contracts with registrars, registries and privacy/proxy service providers.</span><o:p></o:p></p>
<p class="MsoNormal" style="line-height:19.5pt;background:white"><span style="font-size:12.0pt;font-family:Helvetica;color:black"> </span><o:p></o:p></p>
<p class="MsoNormal" style="line-height:19.5pt;background:white"><span style="font-size:12.0pt;font-family:Helvetica;color:black">Patience is growing thin by those watching damage occur to the world's online identifier system in the midst of the COVID-19 crisis.
This includes the registrars and registries who today expend great efforts and resources to combat abuse, only to be painted with broad brush alongside these bad actors. ICANN is overdue to respond in a meaningful and impactful way to the DNS abuse problem.</span><o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal"><span style="color:black">Denise Michel</span><o:p></o:p></p>
<p class="MsoNormal"><u><span style="color:black"><a href="mailto:denisemichel@fb.com" title="mailto:denisemichel@fb.com"><span style="color:#954F72">denisemichel@fb.com</span></a></span></u><span style="color:black"> </span><o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
</div>
</body>
</html>