fatcock.net is a free email provider

fatcock.net is a consumer mailbox provider, so anyone can open an address there in a minute.

Free provider

87 /100

Strong

Email authentication report card

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

2 pass 3 weak

Can mail be forged as this domain?

A forgery is sent to spam, not the inbox

DMARC is set to p=quarantine and enforced on every message, so a receiver that honours it does not reject a forgery outright but files it in spam rather than the inbox. Moving to p=reject would drop it entirely.

  • Weak

    SPF ~all

    The record ends in ~all. Mail from a host outside the list is only marked, not rejected, so it usually still arrives.

  • Pass

    DMARC p=quarantine

    Receivers are asked to send failing mail to spam rather than the inbox.

  • 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.

  • Pass

    DNSSEC Signed

    The zone is signed, so the MX, SPF and DMARC answers above cannot be quietly rewritten in transit.

  • Weak

    TLS-RPT Not published

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

Why it scores 87?

  1. DMARC is published and enforced, so forged mail is rejected or quarantined.
  2. Registered more than a year ago.
  3. Accepts mail through 2 MX hosts.

What to publish to close the gaps

The records fatcock.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. Tighten SPF to -all

    Namefatcock.net
    TypeTXT
    Valuev=spf1 <your existing mechanisms> -all

    Keep the mechanisms you already have and change the final qualifier. Anything softer leaves the forgery path open.

  2. Raise DMARC to p=reject

    Name_dmarc.fatcock.net
    TypeTXT
    Valuev=DMARC1; p=reject; pct=100; rua=mailto:[email protected]

    Quarantine sends forgeries to spam, where people still find them. Reject stops delivery.

  3. Publish an MTA-STS policy

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

    Serve the policy body at https://mta-sts.fatcock.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.

  4. Publish a TLS reporting address

    Name_smtp._tls.fatcock.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.

Questions about fatcock.net

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

Is fatcock.net a disposable email domain?
No. fatcock.net is a consumer mailbox provider, so addresses are permanent, but anyone can open one in a minute.
Is fatcock.net spoofable?
A forgery is sent to spam, not the inbox. DMARC is set to p=quarantine and enforced on every message, so a receiver that honours it does not reject a forgery outright but files it in spam rather than the inbox. Moving to p=reject would drop it entirely.
Does fatcock.net publish SPF and DMARC?
fatcock.net publishes an SPF record, though it does not end in -all, so hosts outside the list are not treated as forgeries. DMARC is published and enforced, so a failing message is rejected or quarantined.
Who handles email for fatcock.net?
Mail for fatcock.net is handled by Proton Mail, which carries 8 other domains we track.
How old is the fatcock.net domain?
The fatcock.net domain was registered 4 years ago. The registrar of record is Cloudflare, Inc.
How do I block fatcock.net on my signup form?
We do not classify fatcock.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 fatcock.net?
fatcock.net scores 87 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.