Email report for in-box.net
in-box.net is a parked domain with no mail service behind it.
62 /100
Good
Email authentication report card
What in-box.net publishes in DNS to stop other people sending mail in its name, read record by record.
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 62?
- Registered more than five years ago.
- No DMARC record, so receiving servers have no policy to apply to forged mail.
- Accepts mail through 2 MX hosts.
What to publish to close the gaps
The records in-box.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.
Publish an SPF record
Namein-box.netTypeTXTValuev=spf1 include:<your mail platform> -allList every platform that sends on your behalf, then end the record in -all so everything else fails.
Publish a DMARC record
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.
Publish an MTA-STS policy
Name_mta-sts.in-box.netTypeTXTValuev=STSv1; id=<a version string you bump on every change>Serve the policy body at https://mta-sts.in-box.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.
Publish a TLS reporting address
Without it, a sending server that could not negotiate TLS with your mail hosts has nowhere to tell you.
Questions about in-box.net
Every answer below is generated from the stored record for this domain.
Is in-box.net a disposable email domain?
Is in-box.net spoofable?
Does in-box.net publish SPF and DMARC?
Who handles email for in-box.net?
How old is the in-box.net domain?
How do I block in-box.net on my signup form?
Can I trust email from in-box.net?
Last verified . We recheck every domain on a schedule, and this report changes only when its records or its verdict do.