graffiti.net cannot receive email

graffiti.net cannot receive email at all.

No mail

84 /100

Strong

Email authentication report card

What graffiti.net publishes in DNS to stop other people sending mail in its name, read record by record.

1 pass 3 weak 1 fail

Can mail be forged as this domain?

No, a forgery is rejected

DMARC is set to p=reject and enforced on every message, so a receiver that honours it throws away any mail that fails alignment for this domain.

  • Fail

    SPF No record

    No SPF record is published, so receivers have no list of hosts allowed to send as this domain.

  • Pass

    DMARC p=reject

    Receivers are asked to reject any message that fails DMARC. This is the strongest published setting.

  • Weak

    MTA-STS Not published

    No MTA-STS policy, so a sending server has nothing that tells it to insist on verified TLS for this domain.

  • Weak

    DNSSEC Not signed

    The zone is not signed. A resolver has no cryptographic way to tell a real answer from a forged one.

  • Weak

    TLS-RPT Not published

    No reporting address, so failed TLS deliveries to this domain go unnoticed by its owner.

Why it scores 84?

  1. Registered more than five years ago.
  2. DMARC is published and enforced, so forged mail is rejected or quarantined.
  3. No MX record, but the domain resolves, so mail still reaches that host.

What to publish to close the gaps

The records graffiti.net is missing, in the order they are worth doing. Owner names are written out in full, so they work whether your DNS panel wants a full name or a relative one.

  1. Publish an SPF record

    Namegraffiti.net
    TypeTXT
    Valuev=spf1 include:<your mail platform> -all

    List every platform that sends on your behalf, then end the record in -all so everything else fails.

  2. Publish an MTA-STS policy

    Name_mta-sts.graffiti.net
    TypeTXT
    Valuev=STSv1; id=<a version string you bump on every change>

    Serve the policy body at https://mta-sts.graffiti.net/.well-known/mta-sts.txt, start it in testing mode, then switch it to enforce so senders refuse to deliver over an unverified connection.

  3. Publish a TLS reporting address

    Name_smtp._tls.graffiti.net
    TypeTXT
    Valuev=TLSRPTv1; rua=mailto:[email protected]

    Without it, a sending server that could not negotiate TLS with your mail hosts has nowhere to tell you.

  4. Sign the zone with DNSSEC

    Turn DNSSEC on with your DNS provider, then publish the DS record it hands you at your registrar. Every record above is only as trustworthy as the answer that carries it, and signing the zone is what makes the answers verifiable.

Questions about graffiti.net

Every answer below is generated from the stored record for this domain.

Is graffiti.net a disposable email domain?
No. We classify graffiti.net as no mail, not as a disposable mailbox service.
Is graffiti.net spoofable?
No, a forgery is rejected. DMARC is set to p=reject and enforced on every message, so a receiver that honours it throws away any mail that fails alignment for this domain.
Does graffiti.net publish SPF and DMARC?
graffiti.net publishes no SPF record, so no receiver is told which hosts may send in its name. DMARC is published and enforced, so a failing message is rejected or quarantined.
Who handles email for graffiti.net?
We have not matched the mail hosts for graffiti.net to a platform we track, so we do not name one. The hostnames themselves are available with an API key.
How old is the graffiti.net domain?
The graffiti.net domain was registered 30 years ago. The registrar of record is GoDaddy.com, LLC.
How do I block graffiti.net on my signup form?
We do not classify graffiti.net as disposable, so blocking it outright would turn away real people. If you want to act on it, decide on the signals listed above rather than the name.
Can I trust email from graffiti.net?
graffiti.net scores 84 out of 100, which is a strong band. The score is a summary of the classification, infrastructure, authentication, reputation and lifecycle signals we hold, not a judgment about any individual sender at that domain.

Last verified . We recheck every domain on a schedule, and this report changes only when its records or its verdict do.