phpto.us is a disposable email domain

phpto.us hands out throwaway mailboxes, so an address there identifies nobody.

Disposable No authenticationSpoofable

0 /100

Poor

Email authentication report card

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

1 pass 2 weak 2 fail

Can mail be forged as this domain?

Yes, a forgery is delivered

no DMARC record is published, so a receiver that honours what this domain publishes is not told to reject a message with it in the From header, and delivers it.

  • Fail

    SPF No record

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

  • Fail

    DMARC No record

    No DMARC record is published, so receivers get no instruction and judge a forged message on SPF and DKIM alone.

  • 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 0?

  1. Mailboxes on this domain are throwaway, so no identity stands behind them.
  2. No DMARC record, so receiving servers have no policy to apply to forged mail.
  3. No SPF record, so anyone can send as this domain.

What to publish to close the gaps

The records phpto.us 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

    Namephpto.us
    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 a DMARC record

    Name_dmarc.phpto.us
    TypeTXT
    Valuev=DMARC1; p=none; rua=mailto:[email protected]; fo=1

    Start at p=none with a reporting address, read the reports for a few weeks to find the senders you forgot, then move the policy up.

  3. Publish an MTA-STS policy

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

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

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

Is phpto.us a disposable email domain?
Yes. phpto.us hands out throwaway mailboxes, so an address there tells you nothing about who is behind it.
Is phpto.us spoofable?
Yes, a forgery is delivered. no DMARC record is published, so a receiver that honours what this domain publishes is not told to reject a message with it in the From header, and delivers it.
Does phpto.us publish SPF and DMARC?
phpto.us publishes no SPF record, so no receiver is told which hosts may send in its name. No DMARC record is published, so a failing message is left to each receiver to judge.
Who handles email for phpto.us?
Mail for phpto.us is handled by emailfake.com, which carries 453 other domains we track.
How old is the phpto.us domain?
The registry for .us does not publish a registration date we can read, so we do not state an age.
How do I block phpto.us on my signup form?
Blocking the exact string phpto.us is not enough on its own: a disposable provider adds domains, and some hand out unlimited subdomains under one name. Match the mail platform behind the domain rather than the domain alone, which is what the lookup behind this page does.
Can I trust email from phpto.us?
phpto.us scores 0 out of 100, which is a poor 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.