Email report for rsgsv.net

rsgsv.net is sending infrastructure: it carries outbound mail and collects the bounces that come back, and no person has a mailbox on it.

Sending only

35 /100

Weak

Email authentication report card

What rsgsv.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?

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.

  • Weak

    DNSSEC Not signed

    The zone is not signed. A resolver has no cryptographic way to tell a real answer from a forged one.

  • Weak

    TLS-RPT Not published

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

Why it scores 35?

  1. This domain sends mail and receives its own bounces, but nobody has a mailbox here.
  2. No website answers on this domain.

What to publish to close the gaps

The records rsgsv.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.rsgsv.net
    TypeTXT
    Valuev=STSv1; id=<a version string you bump on every change>

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

  3. Sign the zone with DNSSEC

    Turn DNSSEC on with your DNS provider, then publish the DS record it hands you at your registrar. Every record above is only as trustworthy as the answer that carries it, and signing the zone is what makes the answers verifiable.

Questions about rsgsv.net

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

Is rsgsv.net a disposable email domain?
No. We classify rsgsv.net as sending only, not as a disposable mailbox service.
Is rsgsv.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 rsgsv.net publish SPF and DMARC?
rsgsv.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 rsgsv.net?
We have not matched the mail hosts for rsgsv.net to a platform we track, so we do not name one. The hostnames themselves are available with an API key.
How old is the rsgsv.net domain?
The rsgsv.net domain was registered 15 years ago. The registrar of record is MarkMonitor Inc.
How do I block rsgsv.net on my signup form?
We do not classify rsgsv.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 rsgsv.net?
rsgsv.net scores 35 out of 100, which is a weak 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.