hideaddress.net is an email alias domain

hideaddress.net issues forwarding aliases that hide a real mailbox, so the person is reachable but not identifiable.

Privacy relay

50 /100

Fair

Email authentication report card

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

3 pass 2 weak

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.

  • Pass

    SPF -all

    The record ends in -all, so a receiver is told to treat mail from any host outside the list as a forgery.

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

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

  1. Addresses here are forwarding aliases that hide the real mailbox, so one person can hold any number of identities on this domain.
  2. This domain hands out forwarding aliases that mask a real mailbox.

What to publish to close the gaps

The records hideaddress.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 MTA-STS policy

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

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

  2. Publish a TLS reporting address

    Name_smtp._tls.hideaddress.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 hideaddress.net

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

Is hideaddress.net a disposable email domain?
No, but it is a privacy relay. hideaddress.net mints forwarding aliases that hide a real mailbox, so the person is reachable while the identity stays masked.
Is hideaddress.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 hideaddress.net publish SPF and DMARC?
hideaddress.net publishes an SPF record that ends in -all, the strict form. DMARC is published and enforced, so a failing message is rejected or quarantined.
Who handles email for hideaddress.net?
Mail for hideaddress.net is handled by Forward Email, which carries 17 other domains we track.
How old is the hideaddress.net domain?
The hideaddress.net domain was registered 6 years ago. The registrar of record is NameCheap, Inc.
How do I block hideaddress.net on my signup form?
We do not classify hideaddress.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 hideaddress.net?
hideaddress.net scores 50 out of 100, which is a fair 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.