Mail records were not checked for this address

Mail records live in DNS, not in your code, so no coding agent touches them. The result is a password reset that lands in spam and a domain anybody can send mail as. It is one of the few serious items on a result that is fixed entirely outside the app.

The app is on a shared hosting domain ({domain}), so its mail records belong to the platform and not to you.

no TXT record beginning v=spf1 found for example.com

Every finding on a result carries a line like this one: the request that was made and the answer that came back. You can run the same request yourself and get the same answer, which is the point.

Check SPF and DMARC on your own domain once you connect one.

A result gives you this prompt written for your builder, in its own dialect, and a batch prompt that carries every fix at once.

• Not verified

  First-quarter 2026 assessment of 200 apps

  183 of 200 vibe-coded apps, 91.5 percent, contained at least one vulnerability traceable to AI hallucination or missing security context.

  2026-04

  Read the incident
• Declared

  CVE growth in AI-generated code

  CVE entries attributed to AI-generated code rose from 6 in January 2026 to more than 35 in March 2026.

  2026-03

  Read the incident
• Observed

  5,600 vibe-coded apps scanned

  More than 2,000 vulnerabilities and more than 400 exposed secrets found across vibe-coded apps.

  2026-02

  Read the incident
• Not verified

  Tenzai study of AI-built apps

  69 vulnerabilities across 15 apps built by five AI coding tools.

  2026-02

  Read the incident

This page is the explanation of the finding. The free tool runs the same check on your own app and returns the evidence line.

Email authentication check

• spf
• dmarc
• evidence