{
	"id": "1af4f689-f22a-4828-9c32-5b061550f8a9",
	"created_at": "2026-04-06T00:13:17.565553Z",
	"updated_at": "2026-04-10T13:12:04.951987Z",
	"deleted_at": null,
	"sha1_hash": "3b7773529a2e27cd3332f6eedf24613d43779177",
	"title": "What Is DMARC? - Meaning, Purpose, Verification | Proofpoint US",
	"llm_title": "",
	"authors": "",
	"file_creation_date": "0001-01-01T00:00:00Z",
	"file_modification_date": "0001-01-01T00:00:00Z",
	"file_size": 195126,
	"plain_text": "What Is DMARC? - Meaning, Purpose, Verification | Proofpoint\r\nUS\r\nPublished: 2021-02-19 · Archived: 2026-04-05 13:27:49 UTC\r\nTable of Contents\r\nDMARC Definition\r\nSPF and DKIM\r\nWhat Is a DMARC Record?\r\nHow DMARC Works\r\nDMARC Requirements\r\nBenefits of DMARC\r\nDMARC Best Practices and Tools\r\nHow to Create a DMARC Record\r\nDMARC Policies\r\nDMARC Myths and Misconceptions\r\nDMARC vs. DKIM\r\nWhy Use DMARC for Email?\r\nEmail security remains a critical challenge for all types of organizations and institutions, with domain spoofing\r\nand phishing attacks becoming increasingly sophisticated. DMARC (Domain-based Message Authentication,\r\nReporting, and Conformance) stands as the only widely deployed technology that makes the sender’s “From”\r\naddress trustworthy in email communications.\r\nRecent data shows the urgency of implementing effective email security and authentication, as DMARC adoption\r\nhas doubled in the past year, with 110,000 new domains implementing it monthly. This authentication protocol is a\r\ncrucial defense mechanism, allowing organizations to protect their domains from unauthorized use while\r\nproviding detailed reporting on email authentication results.\r\nHere’s how your free trial works:\r\nMeet with our cybersecurity experts to assess your environment and identify your threat risk exposure\r\nWithin 24 hours and minimal configuration, we’ll deploy our solutions for 30 days\r\nExperience our technology in action!\r\nReceive report outlining your security vulnerabilities to help you take immediate action against\r\ncybersecurity attacks\r\nFill out this form to request a meeting with our cybersecurity experts.\r\nThank you for your submission.\r\nhttps://www.proofpoint.com/us/threat-reference/dmarc\r\nPage 1 of 10\n\nDMARC Definition\r\nDMARC, which stands for Domain-based Message Authentication, Reporting, and Conformance, is an open email\r\nauthentication protocol that provides domain-level protection of the email channel. DMARC authentication\r\ndetects and prevents email spoofing techniques used in phishing, business email compromise (BEC), and other\r\nemail-based attacks.\r\nBuilding on existing standards—Sender Policy Framework (SPF) and DomainKeys Identified Mail (DKIM)—\r\nDMARC is a critical and widely deployed technology that validates the header “From” domain authenticity. The\r\ndomain owner can publish a DMARC record in the Domain Name System (DNS) and create a policy to tell\r\nreceivers what to do with emails that fail authentication.\r\nWith DMARC, domain owners can effectively outline their authentication practices and determine specific actions\r\nthat can be taken when an email fails authentication. This powerful email authentication protocol helps domain\r\nowners combat a host of security threats.\r\nExamples\r\nDomain spoofing: An attacker spoofs a company’s domain to make an email seem legitimate.\r\nEmail spoofing: A term for spoofing activities involving email.\r\nBusiness email compromise (BEC): An email that appears to come from a senior employee within an\r\norganization requesting that money or sensitive information be sent.\r\nImpostor email: A spoofed email sent by an impostor claiming to be someone they are not.\r\nEmail phishing: An email attempting to get victims to install malware or offer their credentials. A phishing\r\nemail often looks like a familiar brand to appear legitimate.\r\nConsumer phishing: Spoofed email sent to a consumer of a company claiming to be from that company\r\nintending to steal credentials.\r\nPartner spoofing: Business-based spoofed email between supply chain partners requesting to change\r\npayment details to siphon money.\r\nWhaling email scam: Fraudulent email sent to a senior employee within an organization aiming to get a\r\nlarge financial gain.\r\nAI-enhanced phishing: Sophisticated phishing attempts using AI-generated content to create more\r\nconvincing and personalized fraudulent emails.\r\nStandards\r\nDomain-based Message Authentication Reporting and Conformance (DMARC): An email validation\r\nsystem that detects and prevents email spoofing. It helps combat certain techniques often used in phishing\r\nand email spam, such as emails with forged sender addresses that appear to come from legitimate\r\norganizations.\r\nSender Policy Framework (SPF): An email validation protocol that detects and blocks emails. It allows\r\nreceiving mail exchangers to verify that incoming mail from a domain comes from an IP address\r\nauthorized by its administrators.\r\nhttps://www.proofpoint.com/us/threat-reference/dmarc\r\nPage 2 of 10\n\nDomainKeys Identified Mail (DKIM): An email authentication method that detects email spoofing. It\r\nallows the receiver to check that an email claiming to come from a specific domain was authorized by its\r\nowner.\r\nM3AAWG sender best practices: Industry guidelines that outline email authentication requirements,\r\nincluding DMARC implementation, for bulk senders to maintain deliverability and security.\r\nGoogle-Yahoo 2024 requirements: New authentication standards requiring DMARC implementation for\r\nbulk senders (\u003e5,000 emails daily) to maintain inbox deliverability.\r\nSPF and DKIM\r\nSPF and DKIM are the two primary authentication mechanisms that play a crucial role in DMARC. Each is based\r\non unique records that help confirm the legitimacy of emails.\r\nSender Policy Framework (SPF) is an email validation protocol that allows an organization to specify who can\r\nsend emails from their domains. Organizations can authorize senders within an SPF record published in the\r\nDomain Name System (DNS). This record includes the approved IP addresses of email senders, including the IP\r\naddresses of service providers authorized to send emails on the organization’s behalf. While SPF alone has\r\nlimitations due to email forwarding and the complexity of modern email infrastructure, publishing and checking\r\nSPF records is a reliable way to stop phishing and other email-based threats that forge “From” addresses and\r\ndomains.\r\nDomain Keys Identified Mail (DKIM) is an email authentication protocol that allows the receiver to check that an\r\nemail from a specific domain was authorized by its owner. It enables an organization to take responsibility for\r\ntransmitting a message by attaching a digital signature. Verification is done through cryptographic authentication\r\nusing the signer’s public key published in the DNS. DKIM signatures should use at least 2048-bit keys, as shorter\r\nkeys are considered cryptographically weak. The signature ensures that parts of the email have not been modified\r\nsince the digital signature was attached.\r\nBoth SPF and DKIM help establish email authenticity and prevent common email security threats, like spoofing\r\nand phishing attacks. In the context of DMARC, these authentication mechanisms are used in conjunction to\r\nvalidate the sender’s identity. Major email providers now require both SPF and DKIM authentication for bulk\r\nsenders.\r\nThe DMARC policy, published as a DNS record, instructs recipient servers on how to handle emails that fail SPF\r\nor DKIM checks. By combining SPF and DKIM results with a DMARC policy, domain owners can specify\r\nwhether to quarantine or reject emails that fail authentication, allowing better control over email delivery and\r\nreducing the risk of fraudulent emails attempting to hijack their domain name.\r\nWhat Is a DMARC Record?\r\nA DMARC record is a special text entry (known as a DNS TXT record) that lives in your domain’s DNS settings,\r\nacting like a set of instructions for receiving mail servers. This record, which appears under\r\n“_dmarc.yourdomain.com,” contains specific tag-value pairs that define authentication policies and reporting\r\npreferences for incoming emails claiming to be from your domain.\r\nhttps://www.proofpoint.com/us/threat-reference/dmarc\r\nPage 3 of 10\n\nThe record consists of essential components, with the most critical being the version tag (v=DMARC1), policy tag\r\n(p=none/quarantine/reject), and reporting address tag (rua=mailto:example@domain.com). These elements work\r\ntogether to help organizations verify legitimate email sources and protect their domains from unauthorized use,\r\nproviding a robust framework for email authentication.\r\nHow DMARC Works\r\nFor a message to pass DMARC authentication, it must pass SPF authentication and SPF alignment and/or pass\r\nDKIM authentication and DKIM alignment. If a message fails DMARC, senders can instruct receivers on what to\r\ndo with that message per a DMARC policy. There are three DMARC policies the domain owner can enforce: none\r\n(the message is delivered to the recipient, and the DMARC report is sent to the domain owner), quarantine (the\r\nmessage is moved to a quarantine folder), and reject (the message is not delivered at all).\r\nWhile starting with a “none” policy is recommended, the domain owner receives DMARC reports to help ensure\r\nthat all legitimate emails are identified and pass authentication. Organizations should plan to progress beyond\r\n“none” within 12 months of implementation. Once the domain owner is confident they have identified all\r\nlegitimate senders and have fixed authentication issues, they can move to a policy of “reject” and block phishing,\r\nbusiness email compromise, and other email fraud attacks. As an email receiver, an organization can ensure that its\r\nsecure email gateway enforces the DMARC policy implemented by the domain owner. This will protect\r\nemployees against inbound email threats.\r\nSPF authentication starts by identifying all legitimate IP addresses that should send emails from a given domain\r\nand then publishes this list in the DNS. Due to DNS lookup limits, organizations should carefully manage their\r\nSPF records and consider using include mechanisms. Before delivering a message, email providers verify the SPF\r\nrecord by looking up the domain included in the “envelope from” address within the hidden technical header of\r\nhttps://www.proofpoint.com/us/threat-reference/dmarc\r\nPage 4 of 10\n\nthe email. If the IP address sending an email on behalf of this domain is not listed in the domain’s SPF record, the\r\nmessage fails SPF authentication.\r\nFor DKIM authentication, the sender first identifies what fields they want to include in their DKIM signature,\r\nsuch as the “From” address, the body of the email, the subject, and more. These fields must remain unchanged in\r\ntransit, or the message will fail DKIM authentication. The sender’s email platform will create a hash of the text\r\nfields included in the DKIM signature. Once the hash string is generated, it is encrypted with a private key only\r\nthe sender can access. After the email is sent, it’s up to the email gateway or consumer mailbox provider to\r\nvalidate the DKIM signature by locating a public key that matches the private key. Then, the DKIM signature is\r\ndecrypted back to its original hash string.\r\nDMARC Requirements\r\nMajor email providers have implemented new authentication requirements in 2024 to enhance email security and\r\nreduce fraudulent activities. These requirements primarily affect bulk email senders.\r\nGoogle and Yahoo Requirements\r\nOrganizations sending over 5,000 emails daily to Gmail or Yahoo accounts must implement:\r\nA DMARC record with a minimum policy of “p=none”\r\nSPF and DKIM records for each sending domain\r\nSPF or DKIM alignment for the “From” header\r\nARC authentication for forwarded messages\r\nOne-click unsubscribe functionality for commercial messages (by June 1, 2024)\r\nSpam rates below 0.3%, as reported in Postmaster Tools\r\nEnforcement Timeline\r\nThe implementation process follows a graduated schedule:\r\nFebruary 2024: Initial enforcement began with temporary errors for non-compliant traffic\r\nApril 2024: Google starts rejecting a percentage of non-compliant email traffic\r\nJune 2024: Full enforcement of DMARC requirements and one-click unsubscribe functionality\r\nAdditional Requirements\r\nOrganizations must also:\r\nSegregate email class types by domain\r\nAdhere to SMTP “tempfailure” and rejection errors\r\nMaintain proper email authentication setup to prevent messages from being marked as spam or rejected\r\nThese requirements represent a significant shift in email authentication standards, making DMARC\r\nimplementation no longer optional but a business necessity for maintaining effective email deliverability.\r\nhttps://www.proofpoint.com/us/threat-reference/dmarc\r\nPage 5 of 10\n\nBenefits of DMARC\r\nDMARC provides several benefits in reinforcing email-based cybersecurity measures for organizations that\r\nimplement it. Some of the core advantages of leveraging DMARC include:\r\nEnsures email deliverability: Setting a DMARC record in your DNS settings is now required for overall\r\nemail deliverability and preventing threat actors from delivering malicious emails using your domain.\r\nLowers the risk of email phishing attacks: DMARC effectively prevents and mitigates the risk of\r\nphishing attacks, which can be costly to an organization and its bottom line.\r\nEnforces sender policies: DMARC allows organizations to enforce policies via its DNS record, defining\r\nspecific practices for email authentication and providing instructions for receiving mail servers about how\r\nto enforce them.\r\nProtects brand reputation: DMARC helps protect an organization’s brand reputation by preventing cyber\r\ncriminals from impersonating their domain and deceiving customers and clients into releasing sensitive\r\ninformation.\r\nProvides thorough authentication reporting: DMARC checks provide visibility into an organization’s\r\nemail system by offering comprehensive authentication reporting and threat intelligence.\r\nFunctions at scale: DMARC is intended to perform with internet scalability, making it an effective tool for\r\nlarge-scale organizations, institutions, and corporate entities.\r\nMeets compliance requirements: DMARC implementation helps organizations comply with modern\r\nemail security standards and industry requirements from major providers like Google and Yahoo.\r\nWhile many of these benefits overlap, the underlying function of DMARC is to better protect email through\r\neffective authentication and threat mitigation.\r\nDMARC Best Practices and Tools\r\nDue to the volume of DMARC reports that an email sender can receive and the lack of clarity provided within\r\nDMARC reports, fully implementing DMARC authentication can be challenging. These tools and best practices\r\ncan help ensure your organization optimizes DMARC.\r\nPublish policies to your DNS record that clearly define your organization’s practices for email\r\nauthentication and document instructions for receiving mail servers about how to enforce those policies.\r\nUse automated DMARC monitoring and analysis tools to process aggregate (RUA) and forensic (RUF)\r\nreports effectively.\r\nAdditional data and insights beyond what’s included within DMARC reports help organizations identify\r\nemail senders faster and more accurately. This helps speed up the implementation of DMARC\r\nauthentication and reduces the risk of blocking legitimate emails.\r\nProfessional service consultants with DMARC expertise can help organizations with DMARC\r\nimplementation. Consultants help identify all legitimate senders, fix authentication issues, and even work\r\nwith email service providers to ensure they authenticate properly.\r\nOrganizations can create a DMARC record in minutes and start gaining visibility through DMARC reports\r\nby enforcing a DMARC policy of “none.” However, they should establish a clear timeline for moving to\r\nstricter policies.\r\nhttps://www.proofpoint.com/us/threat-reference/dmarc\r\nPage 6 of 10\n\nAfter identifying all legitimate email senders—including third-party email service providers—and fixing\r\nany authentication issues, organizations should progress to quarantine policy before finally enforcing a\r\nDMARC policy of “reject.”\r\nImplement strong SPF records with minimal DNS lookups and DKIM with 2048-bit keys as foundational\r\nsteps.\r\nDMARC implementation can be complicated, but it’s a critical protocol in securing your organization’s email\r\nchannels and mitigating fraudulent activity.\r\nHow to Create a DMARC Record\r\nImplementing DMARC is now essential to protect your email against impostors and fraudulent activity. Creating a\r\nDMARC record is the first step to protecting your organization, customers, and brand reputation from email fraud.\r\nYou can use Proofpoint’s DMARC Creation Wizard to create a record for your organization or follow the steps\r\nbelow to get started.\r\nDMARC records are hosted on your DNS servers as TXT entries. Every host provider grants DNS access to\r\ncustomers, so you can add this TXT entry from the registrar where the domain was registered or in a dashboard\r\nprovided by the website host. The steps to create a DMARC record differ based on the registrar or host, but\r\ncreating the record is the same for every domain. After you authenticate into your host or registrar, create a DNS\r\nentry using the following steps:\r\n1. Create a TXT record. After you start the creation process, you must enter a name and value for the record.\r\n2. Name your record “DMARC.” In some host configurations, the domain name is automatically appended to\r\nthe name. If it is not added automatically, name the record _dmarc.yourdomain.com.\r\n3. Enter the value for your record. Here’s a recommended initial DMARC record: v=DMARC1; p=none;\r\nrua=mailto:youraddress@yourdomain.com; ruf=mailto:forensics@yourdomain.com; pct=100\r\nThe key values in the entry are critical for direction when users send emails to your domain. The first “v” value is\r\nnecessary and defines the version. This value will be the same for all records. The second “p” value determines\r\nwhat happens when the email passes or fails. In this example, the value is set to “none,” indicating nothing will\r\nhappen. This value is recommended initially to ensure that DMARC works correctly before quarantining\r\nmessages.\r\nAfter you verify that DMARC works correctly, the “p” value can be changed to “quarantine” or “reject.” Start\r\nwith “none” for at least 30 days, then move to “quarantine” for another 30 days before considering “reject.” The\r\nmessage will be set aside until you review it. The “reject” option will outright drop records that don’t pass\r\nDMARC rules. The “pct” tag allows you to apply the policy gradually, though most organizations should maintain\r\nit at 100%. Only use the “reject” option when you are positive that no important messages will be dropped by your\r\nDMARC settings.\r\nDMARC Policies\r\nDMARC offers three distinct policy levels that determine how receiving mail servers handle emails that fail\r\nauthentication. Each policy is designated by the “p=” tag in the DMARC record, providing different levels of\r\nhttps://www.proofpoint.com/us/threat-reference/dmarc\r\nPage 7 of 10\n\nprotection and control.\r\nP=none Policy\r\nThis monitoring-only policy allows organizations to gain visibility into email streams without affecting delivery.\r\nWhile emails undergo authentication checks, they continue to flow normally regardless of the results. This policy\r\nserves as a crucial first step in DMARC implementation, though it provides no actual protection against domain\r\nspoofing.\r\nP=quarantine Policy\r\nThe quarantine policy instructs receiving servers to treat suspicious emails with increased scrutiny. When an email\r\nfails DMARC authentication, it is typically directed to the recipient’s spam folder rather than the primary inbox.\r\nThis provides a middle-ground approach, allowing legitimate emails that might fail authentication to remain\r\naccessible while flagging potential threats.\r\nP=reject Policy\r\nAs the strictest DMARC policy, reject tells receiving servers to block any emails that fail authentication\r\ncompletely. These messages never reach the recipient’s inbox or spam folder, offering the strongest protection\r\nagainst email spoofing and domain abuse. Recent data indicates that while p=none remains the most common\r\npolicy, organizations should consider moving toward stricter enforcement, as nearly 75% of senders using p=none\r\nhave no plans to upgrade their policies despite increasing security requirements.\r\nDMARC Myths and Misconceptions\r\nEmail authentication can be complex, and several persistent myths about DMARC continue to circulate among\r\nsecurity professionals and business leaders. Here are the most significant misconceptions that need clarification:\r\nDMARC is just a spam filter: DMARC doesn’t function as a traditional spam filter. Instead, it provides\r\nspecific instructions to receiving mail servers about how to handle emails sent from your domain.\r\nOnly large organizations need DMARC: Every organization with a public domain needs DMARC\r\nprotection, regardless of size. Cyber criminals target businesses of all scales, making authentication\r\nessential for everyone.\r\nP=none provides protection: While p=none is a necessary starting point, it only enables monitoring and\r\nprovides no actual protection against spoofing. Organizations must progress to quarantine or reject policies\r\nfor genuine security benefits.\r\nDMARC stops all email attacks: While DMARC is crucial for email security, it doesn’t prevent all types\r\nof attacks. For example, it cannot stop lookalike domain spoofing, which is why organizations need a\r\nlayered security approach.\r\nDMARC is a quick fix: Implementing DMARC requires a methodical approach. Organizations must start\r\nby monitoring and analyzing results and gradually progress through policy levels. Rushing to enforce strict\r\npolicies immediately can disrupt legitimate email flow.\r\nhttps://www.proofpoint.com/us/threat-reference/dmarc\r\nPage 8 of 10\n\nParked domains don’t need DMARC: Every domain, even those not actively sending emails, requires\r\nDMARC protection. Attackers can spoof any domain, making universal protection necessary.\r\nDMARC is purely a security project: DMARC implementation is actually a cross-functional initiative\r\nrequiring collaboration between IT, security, compliance, and marketing teams to be truly effective.\r\nDMARC vs. DKIM\r\nDMARC and DKIM (or DomainKeys Identified Mail) are email authentication protocols that help organizations\r\nfight email compromise and impersonation attacks. However, DMARC is more robust in implementing policies\r\nand utilizing reporting mechanisms. While both protocols use public key cryptography, DMARC and DKIM use\r\ndifferent methods to validate email flow. DKIM is solely an authentication method, while DMARC generates\r\naggregate reports to help optimize an organization’s email strategy.\r\nDMARC aligns both SPF and DKIM mechanisms to provide reporting across activities performed under those\r\ntwo policies. DMARC requires at least one of these mechanisms to pass authentication and alignment checks. This\r\nenables domain owners to publish policies in their DNS records specifying how to check the “From:” field\r\npresented to end-users and how the receiver should deal with failures. Under current requirements from major\r\nemail providers, both DKIM and DMARC are necessary components of a complete email authentication strategy.\r\nDKIM’s purpose is to verify whether an email is legitimate, while DMARC provides explicit instructions about\r\nwhat to do with an illegitimate email.\r\nWhy Use DMARC for Email?\r\nDMARC has become a mandatory requirement of an organization’s email security strategy, as it allows recipients\r\nof emails using the authenticated domain to trust that messages came from the domain owner and not an impostor.\r\nIn turn, organizations use DMARC for these core purposes:\r\nSecurity: DMARC helps prevent phishing scams from infiltrating an organization’s network, which can\r\ncompromise its security.\r\nVisibility: Administrators can monitor emails sent using your domain to ensure they are properly\r\nauthenticated using SPF and/or DKIM.\r\nBrand Protection: DMARC can block spoofed messages that might damage your brand’s reputation.\r\nDeliverability: Major email providers now require DMARC implementation for bulk senders to ensure\r\nreliable inbox placement.\r\nCompliance: DMARC helps organizations meet evolving security standards and regulatory requirements.\r\nDMARC provides a way for domain owners to specify their own authentication practices and determine the\r\nactions taken when an email fails to meet authentication criteria. By implementing DMARC-compliant email,\r\norganizations can secure their domain(s) from unauthorized use and protect against daily email security threats.\r\nGet Ahead of Tomorrow’s Threats with Proofpoint\r\nAnticipating the nature of certain cyber threats helps organizations identify where their defenses are weak and\r\nwhich protective measures to prioritize. Most organizations are more resilient through layered strategies that\r\nhttps://www.proofpoint.com/us/threat-reference/dmarc\r\nPage 9 of 10\n\nleverage detection and prevention technologies, real-time threat intelligence, and user-focused training programs\r\nto reduce the risk of attacks via email and cloud environments. As threats like phishing, BEC, ransomware, and\r\ncredential theft evolve, it’s important to have the right mix of tools and processes to keep your data and your\r\npeople protected. Take ownership to protect against threats and make strides to improve your cybersecurity\r\neffectiveness.\r\nLeverage the capabilities trusted by 83 of the Fortune 100 companies. Contact Proofpoint to learn more.\r\nRelated Resources\r\nThe latest news and updates from Proofpoint, delivered to your inbox.\r\nSign up to receive news and other stories from Proofpoint. Your information will be used in accordance with\r\nProofpoint’s privacy policy. You may opt out at any time.\r\nSource: https://www.proofpoint.com/us/threat-reference/dmarc\r\nhttps://www.proofpoint.com/us/threat-reference/dmarc\r\nPage 10 of 10",
	"extraction_quality": 1,
	"language": "EN",
	"sources": [
		"MITRE"
	],
	"origins": [
		"web"
	],
	"references": [
		"https://www.proofpoint.com/us/threat-reference/dmarc"
	],
	"report_names": [
		"dmarc"
	],
	"threat_actors": [
		{
			"id": "75108fc1-7f6a-450e-b024-10284f3f62bb",
			"created_at": "2024-11-01T02:00:52.756877Z",
			"updated_at": "2026-04-10T02:00:05.273746Z",
			"deleted_at": null,
			"main_name": "Play",
			"aliases": null,
			"source_name": "MITRE:Play",
			"tools": [
				"Nltest",
				"AdFind",
				"PsExec",
				"Wevtutil",
				"Cobalt Strike",
				"Playcrypt",
				"Mimikatz"
			],
			"source_id": "MITRE",
			"reports": null
		}
	],
	"ts_created_at": 1775434397,
	"ts_updated_at": 1775826724,
	"ts_creation_date": 0,
	"ts_modification_date": 0,
	"files": {
		"pdf": "https://archive.orkl.eu/3b7773529a2e27cd3332f6eedf24613d43779177.pdf",
		"text": "https://archive.orkl.eu/3b7773529a2e27cd3332f6eedf24613d43779177.txt",
		"img": "https://archive.orkl.eu/3b7773529a2e27cd3332f6eedf24613d43779177.jpg"
	}
}