runbox.no is a free email provider

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

Free provider

94 /100

Strong

Email authentication report card

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

3 pass 1 weak 1 fail

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.

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

  • Pass

    TLS-RPT Published

    Sending servers have an address to report failed TLS deliveries to.

Why it scores 94?

  1. Registered more than five years ago.
  2. DMARC is published and enforced, so forged mail is rejected or quarantined.
  3. Accepts mail through 1 MX host.

What to publish to close the gaps

The records runbox.no 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

    Namerunbox.no
    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. Raise DMARC to p=reject

    Name_dmarc.runbox.no
    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.runbox.no
    TypeTXT
    Valuev=STSv1; id=<a version string you bump on every change>

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

Questions about runbox.no

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

Is runbox.no a disposable email domain?
No. runbox.no is a consumer mailbox provider, so addresses are permanent, but anyone can open one in a minute.
Is runbox.no 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 runbox.no publish SPF and DMARC?
runbox.no 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 runbox.no?
Mail for runbox.no is handled by Runbox, which carries 36 other domains we track.
How old is the runbox.no domain?
The runbox.no domain was registered 26 years ago. The registrar of record is COPYLEFT, HOST1, KLONER, GRAVITY ASSIST, MIKKELSEN REGISTRARTJENESTE.
How do I block runbox.no on my signup form?
We do not classify runbox.no 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 runbox.no?
runbox.no scores 94 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.