[{"data":1,"prerenderedAt":318},["ShallowReactive",2],{"docsv3-nav":3,"\u002Fdocs\u002Fv3\u002Fconcepts\u002Femail":198},[4],{"title":5,"path":6,"stem":7,"children":8,"page":188},"V3","\u002Fdocs\u002Fv3","1.docs\u002Fv3",[9,13,17,21,38,87,189],{"title":10,"path":11,"stem":12},"Introduction","\u002Fdocs\u002Fv3\u002Fintroduction","1.docs\u002Fv3\u002F1.Introduction",{"title":14,"path":15,"stem":16},"Quick start","\u002Fdocs\u002Fv3\u002Fquick-start","1.docs\u002Fv3\u002F2.Quick start",{"title":18,"path":19,"stem":20},"Challenge flow","\u002Fdocs\u002Fv3\u002Fchallenge-flow","1.docs\u002Fv3\u002F3.Challenge flow",{"title":22,"path":23,"stem":24,"children":25},"Fundamentals","\u002Fdocs\u002Fv3\u002Ffundamentals","1.docs\u002Fv3\u002F4.fundamentals",[26,30,34],{"title":27,"path":28,"stem":29},"Signup protection","\u002Fdocs\u002Fv3\u002Ffundamentals\u002Fsignup-protection","1.docs\u002Fv3\u002F4.fundamentals\u002F00.Signup protection",{"title":31,"path":32,"stem":33},"Login protection","\u002Fdocs\u002Fv3\u002Ffundamentals\u002Flogin-protection","1.docs\u002Fv3\u002F4.fundamentals\u002F01.Login protection",{"title":35,"path":36,"stem":37},"Access protection","\u002Fdocs\u002Fv3\u002Ffundamentals\u002Faccess-protection","1.docs\u002Fv3\u002F4.fundamentals\u002F02.Access protection",{"title":39,"path":40,"stem":41,"children":42},"Guides","\u002Fdocs\u002Fv3\u002Fguides","1.docs\u002Fv3\u002F5.guides",[43,47,51,55,59,63,67,71,75,79,83],{"title":44,"path":45,"stem":46},"Account sharing prevention","\u002Fdocs\u002Fv3\u002Fguides\u002Faccount-sharing-prevention","1.docs\u002Fv3\u002F5.guides\u002F1.Account sharing prevention",{"title":48,"path":49,"stem":50},"Web scraping prevention","\u002Fdocs\u002Fv3\u002Fguides\u002Fweb-scraping-prevention","1.docs\u002Fv3\u002F5.guides\u002F13.Web scraping prevention",{"title":52,"path":53,"stem":54},"Ban enforcement","\u002Fdocs\u002Fv3\u002Fguides\u002Fban-enforcement","1.docs\u002Fv3\u002F5.guides\u002F14.Ban enforcement",{"title":56,"path":57,"stem":58},"Chargeback dispute","\u002Fdocs\u002Fv3\u002Fguides\u002Fchargeback-dispute","1.docs\u002Fv3\u002F5.guides\u002F15.Chargeback dispute",{"title":60,"path":61,"stem":62},"Multi-accounting prevention","\u002Fdocs\u002Fv3\u002Fguides\u002Fmulti-accounting-prevention","1.docs\u002Fv3\u002F5.guides\u002F16.Multi-accounting prevention",{"title":64,"path":65,"stem":66},"Account takeover prevention","\u002Fdocs\u002Fv3\u002Fguides\u002Faccount-takeover-prevention","1.docs\u002Fv3\u002F5.guides\u002F2.Account takeover prevention",{"title":68,"path":69,"stem":70},"Risky transaction prevention","\u002Fdocs\u002Fv3\u002Fguides\u002Frisky-transaction-prevention","1.docs\u002Fv3\u002F5.guides\u002F20.Risky transaction prevention",{"title":72,"path":73,"stem":74},"Fake account detection","\u002Fdocs\u002Fv3\u002Fguides\u002Ffake-account-detection","1.docs\u002Fv3\u002F5.guides\u002F3.Fake account detection",{"title":76,"path":77,"stem":78},"Bot detection","\u002Fdocs\u002Fv3\u002Fguides\u002Fbot-detection","1.docs\u002Fv3\u002F5.guides\u002F4.Bot detection",{"title":80,"path":81,"stem":82},"Card testing prevention","\u002Fdocs\u002Fv3\u002Fguides\u002Fcard-testing-prevention","1.docs\u002Fv3\u002F5.guides\u002F5.Card testing prevention",{"title":84,"path":85,"stem":86},"Incentive abuse prevention","\u002Fdocs\u002Fv3\u002Fguides\u002Fincentive-abuse-prevention","1.docs\u002Fv3\u002F5.guides\u002F9.Incentive abuse prevention",{"title":88,"path":89,"stem":90,"children":91,"page":188},"Concepts","\u002Fdocs\u002Fv3\u002Fconcepts","1.docs\u002Fv3\u002F6.concepts",[92,96,100,104,108,112,116,120,124,128,132,136,140,144,148,152,156,160,164,168,172,176,180,184],{"title":93,"path":94,"stem":95},"Evaluations","\u002Fdocs\u002Fv3\u002Fconcepts\u002Fevaluations","1.docs\u002Fv3\u002F6.concepts\u002F01.evaluations",{"title":97,"path":98,"stem":99},"Actions","\u002Fdocs\u002Fv3\u002Fconcepts\u002Factions","1.docs\u002Fv3\u002F6.concepts\u002F02.actions",{"title":101,"path":102,"stem":103},"Signals","\u002Fdocs\u002Fv3\u002Fconcepts\u002Fsignals","1.docs\u002Fv3\u002F6.concepts\u002F03.signals",{"title":105,"path":106,"stem":107},"Checks","\u002Fdocs\u002Fv3\u002Fconcepts\u002Fchecks","1.docs\u002Fv3\u002F6.concepts\u002F04.checks",{"title":109,"path":110,"stem":111},"Risks","\u002Fdocs\u002Fv3\u002Fconcepts\u002Frisks","1.docs\u002Fv3\u002F6.concepts\u002F05.risks",{"title":113,"path":114,"stem":115},"Verdicts","\u002Fdocs\u002Fv3\u002Fconcepts\u002Fverdicts","1.docs\u002Fv3\u002F6.concepts\u002F06.verdicts",{"title":117,"path":118,"stem":119},"Policies","\u002Fdocs\u002Fv3\u002Fconcepts\u002Fpolicies","1.docs\u002Fv3\u002F6.concepts\u002F07.policies",{"title":121,"path":122,"stem":123},"Challenges","\u002Fdocs\u002Fv3\u002Fconcepts\u002Fchallenges","1.docs\u002Fv3\u002F6.concepts\u002F08.challenges",{"title":125,"path":126,"stem":127},"Concurrency","\u002Fdocs\u002Fv3\u002Fconcepts\u002Fconcurrency","1.docs\u002Fv3\u002F6.concepts\u002F09.concurrency",{"title":129,"path":130,"stem":131},"Impossible travel","\u002Fdocs\u002Fv3\u002Fconcepts\u002Fimpossible-travel","1.docs\u002Fv3\u002F6.concepts\u002F10.impossible-travel",{"title":133,"path":134,"stem":135},"Bots","\u002Fdocs\u002Fv3\u002Fconcepts\u002Fbots","1.docs\u002Fv3\u002F6.concepts\u002F11.bots",{"title":137,"path":138,"stem":139},"Devices","\u002Fdocs\u002Fv3\u002Fconcepts\u002Fdevices","1.docs\u002Fv3\u002F6.concepts\u002F12.devices",{"title":141,"path":142,"stem":143},"Fingerprints","\u002Fdocs\u002Fv3\u002Fconcepts\u002Ffingerprints","1.docs\u002Fv3\u002F6.concepts\u002F13.fingerprints",{"title":145,"path":146,"stem":147},"People","\u002Fdocs\u002Fv3\u002Fconcepts\u002Fpeople","1.docs\u002Fv3\u002F6.concepts\u002F14.people",{"title":149,"path":150,"stem":151},"Lists","\u002Fdocs\u002Fv3\u002Fconcepts\u002Flists","1.docs\u002Fv3\u002F6.concepts\u002F15.lists",{"title":153,"path":154,"stem":155},"Account takeover","\u002Fdocs\u002Fv3\u002Fconcepts\u002Faccount-takeover","1.docs\u002Fv3\u002F6.concepts\u002F16.account-takeover",{"title":157,"path":158,"stem":159},"Account sharing","\u002Fdocs\u002Fv3\u002Fconcepts\u002Faccount-sharing","1.docs\u002Fv3\u002F6.concepts\u002F17.account-sharing",{"title":161,"path":162,"stem":163},"Fake account","\u002Fdocs\u002Fv3\u002Fconcepts\u002Ffake-account","1.docs\u002Fv3\u002F6.concepts\u002F18.fake-account",{"title":165,"path":166,"stem":167},"Scraping","\u002Fdocs\u002Fv3\u002Fconcepts\u002Fscraping","1.docs\u002Fv3\u002F6.concepts\u002F19.scraping",{"title":169,"path":170,"stem":171},"Linked accounts","\u002Fdocs\u002Fv3\u002Fconcepts\u002Flinked-accounts","1.docs\u002Fv3\u002F6.concepts\u002F20.linked-accounts",{"title":173,"path":174,"stem":175},"New IP","\u002Fdocs\u002Fv3\u002Fconcepts\u002Fip","1.docs\u002Fv3\u002F6.concepts\u002F21.ip",{"title":177,"path":178,"stem":179},"Anonymizing network","\u002Fdocs\u002Fv3\u002Fconcepts\u002Fanonymizing-network","1.docs\u002Fv3\u002F6.concepts\u002F22.anonymizing-network",{"title":181,"path":182,"stem":183},"Email quality","\u002Fdocs\u002Fv3\u002Fconcepts\u002Femail","1.docs\u002Fv3\u002F6.concepts\u002F23.email",{"title":185,"path":186,"stem":187},"Velocity","\u002Fdocs\u002Fv3\u002Fconcepts\u002Fvelocity","1.docs\u002Fv3\u002F6.concepts\u002F24.velocity",false,{"title":190,"path":191,"stem":192,"children":193,"page":188},"Advanced","\u002Fdocs\u002Fv3\u002Fadvanced","1.docs\u002Fv3\u002F7.Advanced",[194],{"title":195,"path":196,"stem":197},"Proxy setup","\u002Fdocs\u002Fv3\u002Fadvanced\u002Fproxy-setup","1.docs\u002Fv3\u002F7.Advanced\u002F1.Proxy-setup",{"id":199,"title":181,"body":200,"description":309,"extension":310,"meta":311,"navigation":312,"path":182,"rawbody":313,"seo":314,"stem":183,"__hash__":317},"docsv3\u002F1.docs\u002Fv3\u002F6.concepts\u002F23.email.md",{"type":201,"value":202,"toc":303},"minimark",[203,207,224,229,275,279,297],[204,205,181],"h1",{"id":206},"email-quality",[208,209,210,211,215,216,219,220,223],"p",{},"When you pass an email to an ",[212,213,214],"a",{"href":94},"evaluation",", Rupt inspects the address and the domain behind it. None of these ",[212,217,218],{"href":106},"checks"," judges a person, they judge the address, but together they're the backbone of ",[212,221,222],{"href":162},"fake-account"," detection, because bulk registration almost always cuts corners on email.",[225,226,228],"h2",{"id":227},"the-checks","The checks",[230,231,232,243,251,259,267],"ul",{},[233,234,235,242],"li",{},[236,237,238],"strong",{},[239,240,241],"code",{},"email_is_disposable",": the domain is a throwaway provider built to self-destruct (Mailinator, 10minutemail, and thousands like them). A real customer rarely signs up with one; a bot farm almost always does.",[233,244,245,250],{},[236,246,247],{},[239,248,249],{},"email_is_invalid",": the domain can't actually receive mail (no valid MX records) or the address is malformed. Often a typo, sometimes a fabricated address.",[233,252,253,258],{},[236,254,255],{},[239,256,257],{},"email_is_webmail",": a free consumer provider like Gmail or Outlook. This is the weakest of the set, since most real people use webmail. It only carries weight stacked with other signals.",[233,260,261,266],{},[236,262,263],{},[239,264,265],{},"email_is_accept_all",": the domain accepts mail to any address, so you can't tell a real mailbox from an invented one. Common with catch-all business domains, which makes it ambiguous rather than damning.",[233,268,269,274],{},[236,270,271],{},[239,272,273],{},"is_email_verified",": whether the user has confirmed they control the inbox. An unverified address is just a claim.",[225,276,278],{"id":277},"using-it","Using it",[208,280,281,282,285,286,288,289,292,293,296],{},"Each check is a ",[212,283,284],{"href":118},"policy"," condition and weights into the ",[212,287,222],{"href":162}," ",[212,290,291],{"href":110},"risk"," score. Disposable and invalid are strong enough to act on almost by themselves; webmail and accept-all are softer signals you weigh in rather than block on. The usual approach is to weigh them together rather than block on any one. A disposable address from a ",[212,294,295],{"href":142},"fingerprint"," that just created ten accounts is a far cleaner signal than the email property alone.",[208,298,299,300,302],{},"Rupt reads the email you send it. It never sends mail, and it doesn't verify the inbox for you: ",[239,301,273],{}," reflects what you've told Rupt about the user.",{"title":304,"searchDepth":305,"depth":305,"links":306},"",2,[307,308],{"id":227,"depth":305,"text":228},{"id":277,"depth":305,"text":278},"[object Object]","md",{},true,"---\ntitle: Email quality\ndescription: Email checks judge the address attached to a signup or login: disposable, invalid, webmail, accept-all, and whether it's verified. The backbone of fake-account detection.\n---\n\n# Email quality\n\nWhen you pass an email to an [evaluation](\u002Fdocs\u002Fv3\u002Fconcepts\u002Fevaluations), Rupt inspects the address and the domain behind it. None of these [checks](\u002Fdocs\u002Fv3\u002Fconcepts\u002Fchecks) judges a person, they judge the address, but together they're the backbone of [fake-account](\u002Fdocs\u002Fv3\u002Fconcepts\u002Ffake-account) detection, because bulk registration almost always cuts corners on email.\n\n## The checks\n\n- **`email_is_disposable`**: the domain is a throwaway provider built to self-destruct (Mailinator, 10minutemail, and thousands like them). A real customer rarely signs up with one; a bot farm almost always does.\n- **`email_is_invalid`**: the domain can't actually receive mail (no valid MX records) or the address is malformed. Often a typo, sometimes a fabricated address.\n- **`email_is_webmail`**: a free consumer provider like Gmail or Outlook. This is the weakest of the set, since most real people use webmail. It only carries weight stacked with other signals.\n- **`email_is_accept_all`**: the domain accepts mail to any address, so you can't tell a real mailbox from an invented one. Common with catch-all business domains, which makes it ambiguous rather than damning.\n- **`is_email_verified`**: whether the user has confirmed they control the inbox. An unverified address is just a claim.\n\n## Using it\n\nEach check is a [policy](\u002Fdocs\u002Fv3\u002Fconcepts\u002Fpolicies) condition and weights into the [fake-account](\u002Fdocs\u002Fv3\u002Fconcepts\u002Ffake-account) [risk](\u002Fdocs\u002Fv3\u002Fconcepts\u002Frisks) score. Disposable and invalid are strong enough to act on almost by themselves; webmail and accept-all are softer signals you weigh in rather than block on. The usual approach is to weigh them together rather than block on any one. A disposable address from a [fingerprint](\u002Fdocs\u002Fv3\u002Fconcepts\u002Ffingerprints) that just created ten accounts is a far cleaner signal than the email property alone.\n\nRupt reads the email you send it. It never sends mail, and it doesn't verify the inbox for you: `is_email_verified` reflects what you've told Rupt about the user.\n",{"title":181,"description":315},{"Email checks judge the address attached to a signup or login":316},"disposable, invalid, webmail, accept-all, and whether it's verified. The backbone of fake-account detection.","H3VdvqzCnz315yj8Brq2djatzyrF_rMTpm-jbS_2FlE",1780344893815]