Dataweaz

dsv.com

Summary

Registrar
CSC Corporate Domains, Inc.
Status
clientTransferProhibited
Created on
October 27, 1995
Expires on
October 26, 2026
Name servers
udns1.cscdns.net, udns2.cscdns.uk
Mail servers
mx1.dsv.c3s2.iphmx.com, mx2.dsv.c3s2.iphmx.com
DMARC
Reject

Spoofing protection (DMARC)

Reject

E-mails spoofing this domain are rejected.

DMARC tells mail servers what to do with an e-mail that claims to come from dsv.com but fails SPF and DKIM checks.

Policy
Reject
Subdomain policy
Reject
Messages covered
100%
DKIM alignment
Relaxed
SPF alignment
Relaxed
Aggregate reports
[email protected]
Failure reports
[email protected]

Record

v=DMARC1; p=reject; sp=reject; fo=1; rua=mailto:[email protected]; ruf=mailto:[email protected]

Authorized senders (SPF)

Strict

E-mails sent by any other server are rejected.

SPF lists the servers allowed to send e-mails for dsv.com.

RuleValueResult
includespf.dsv.comAllowed
all—Rejected

Top-level DNS lookups: 1 of 10 allowed

Record

v=spf1 include:spf.dsv.com -all

E-mail signing (DKIM)

DKIM keys published by dsv.com under the most common selectors. Other keys may exist under selectors specific to each sending service.

SelectorLikely serviceKeyStatus
selector1Microsoft 365RSA 2048 bitsActive
selector2Microsoft 365RSA 2048 bitsActive
s1SendGridRSA 2048 bitsActive
s2SendGridRSA 1024 bits · shortActive

RSA keys shorter than 2048 bits, called short keys, are discouraged: they are easier to break.

MX, SPF, DKIM and DMARC: the e-mail records

Four DNS records make a domain's e-mail work. MX says where e-mails sent to dsv.com arrive; SPF, DKIM and DMARC let mail servers check that an e-mail claiming to come from dsv.com was really sent by this domain, which protects it against spoofing.

MX

An MX (Mail Exchanger) record designates a server that receives e-mails sent to the domain. When someone writes to an @dsv.com address, their mail server queries the DNS for the domain's MX records, then delivers the message to the server they point to.

Example record

dsv.com  MX  10 mx1.dsv.com.
dsv.com  MX  20 mx2.dsv.com.

What the record contains

10, 20
Priority: the server with the lowest number is tried first. Servers with equal priority share the load.
mx1.dsv.com.
Host name of the mail server. It must point to an A or AAAA record: an IP address or an alias (CNAME) is not allowed here.
0 .
An MX "0 .", called a null MX, declares that the domain accepts no e-mail: sending servers give up at once instead of retrying.

Declaring at least two servers with different priorities avoids losing e-mails during an outage: sending servers retry for several days and fall back on the backup server. Without any MX, they try to deliver directly to the IP address of the domain.

SPF

SPF (Sender Policy Framework) is a TXT record listing the servers allowed to send e-mails on behalf of the domain. The receiving server checks that the sender is on this list. The final "all" rule says what to do with other servers: reject them (-all), flag their e-mails as suspicious (~all) or make no decision (?all).

Example record

dsv.com  TXT  "v=spf1 mx include:_spf.google.com ip4:192.0.2.10 -all"

What the record contains

v=spf1
Identifies the record as an SPF policy. It must come first.
ip4, ip6
Allows a specific IP address or an address range, for example ip4:192.0.2.0/24.
a, mx
Allows the addresses of the domain itself (A record) or those of its mail servers (MX).
include
Allows the servers of another domain, usually a sending service: include:_spf.google.com for Google Workspace.
-all, ~all
Final rule, applied to every other server. Its qualifier decides what happens to them: - rejects them, ~ flags their e-mails as suspicious, ? makes no decision, + accepts them (avoid it).

A domain must publish only one SPF record, and its evaluation cannot exceed 10 DNS lookups (include, a, mx, exists, redirect). Beyond that, mail servers treat it as invalid.

DKIM

DKIM (DomainKeys Identified Mail) signs every outgoing e-mail with a private key. The matching public key is published in a TXT record at selector._domainkey.dsv.com, so the recipient can check that the message really comes from the domain and was not altered on the way. The selector is chosen by each sending service and cannot be guessed: Dataweaz checks the most common ones (Google Workspace, Microsoft 365, Mailchimp, SendGrid…), so a key published under another selector may exist without appearing here.

Example record

google._domainkey.dsv.com  TXT  "v=DKIM1; k=rsa; p=MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEA…"

What the record contains

v=DKIM1
Protocol version. Optional but recommended, in which case it must come first.
k
Key algorithm: rsa, the most common, or ed25519.
p
Public key, base64-encoded. An empty value means the key has been revoked.
t
Flags: y marks a key in testing, whose failures must not be penalized; s forbids its use for subdomains.

Each sending service publishes its key under its own selector (google, selector1, k1…), which allows several keys and seamless rotation. A 2048-bit RSA key is recommended today.

DMARC

DMARC (Domain-based Message Authentication, Reporting and Conformance) builds on SPF and DKIM. Published on _dmarc.dsv.com, it tells mail servers what to do with an e-mail that fails these checks (let it through, send it to spam or reject it) and where to send reports.

Example record

_dmarc.dsv.com  TXT  "v=DMARC1; p=quarantine; rua=mailto:[email protected]; adkim=r; aspf=r"

What the record contains

v=DMARC1
Identifies the record as a DMARC policy. It must come first.
p
Policy applied to e-mails that fail the checks: none (monitoring only), quarantine (spam folder) or reject.
sp
Subdomain policy. Without it, subdomains follow the domain's policy.
rua
Address that receives daily aggregate reports about e-mails sent on behalf of the domain, whether they pass the checks or not.
ruf
Address that receives detailed failure reports, message by message. Few providers still send them.
pct
Percentage of e-mails subject to the policy, for a gradual rollout. 100 by default.
adkim, aspf
DKIM and SPF alignment: r (relaxed, a subdomain of the same domain is enough) or s (strict, the domain must be identical).

To roll out DMARC without blocking legitimate e-mails, start with p=none and an rua address, analyze the reports to find every service sending on behalf of the domain, then move to quarantine and finally to reject.

DNS records of dsv.com

IP addresses (A and AAAA)

An A record maps the domain name to an IPv4 address: the address of the server that browsers contact to display the website. The AAAA record does the same for an IPv6 address. A domain can have several of them to spread visits across several servers.

Name servers (NS)

NS records designate the authoritative DNS servers of the domain: they answer every question about its other records (A, MX, TXT…). They are provided by the registrar, the hosting provider or a dedicated DNS service, and several servers are declared so that the domain keeps working if one of them fails.

ServerIP address
udns1.cscdns.net204.74.66.1
udns2.cscdns.uk204.74.111.1

Mail servers (MX)

MX records point to the servers that receive e-mails sent to the domain, that is to @dsv.com addresses. Each server has a priority: the one with the lowest number is tried first, the others take over if it fails. Without an MX record, the domain cannot receive e-mails.

PriorityServerIP address
10mx1.dsv.c3s2.iphmx.com216.71.158.66
20mx2.dsv.c3s2.iphmx.com216.71.158.66

TXT records

TXT records hold free text. They are used to prove ownership of the domain to online services (Google, Microsoft, Facebook…) and to publish e-mail security rules: SPF on the domain itself, DMARC on _dmarc.dsv.com.

NameContent
dsv.comgoogle-site-verification=eK464iDhAZr23MGRY7WZrIJCcnH0WI0mNCUXf32VHjw
dsv.comgoogle-site-verification=eNipI_qk2T9rKeJQGFG3466c2ixuCfgVSwo7zXk7EZw
dsv.comnotion-domain-verification=yJDOlu0nmlirOoAj5m3PR0j4B0l2D56cbQr70RxmAAG
dsv.compardot_97572_*=8f3beb3ee0e1a878abda7f636dedb7cfb64058902c2b12791b1bc96e343214a0
dsv.compardot_97572_*=e433c65bf5158792e0e739d5db4f072bfc0679db2934d4bf5f00a6f60b1d2106
dsv.comduo_sso_verification=HeutsnyS5r3Se5g0tHHndSdt6NLXiOoVftoHQi6OqHARSN1Wzdc4F4EzoCtetG6u
dsv.comduo_sso_verification=oj9lPUPsqQfXzddJGcqLLikZbjMf0BWm66XvamctTJt7lbYM8iZhl3oM48Nk3iJK
dsv.comBrOzePWmHLqlA1sNq8qCAKLjclpVYA2JmX76gOVHWJGQl//NV3rVoPrhTVFtu6KCnqLPYnLTyZL9Y0NkINMrVA==
dsv.comyg1Vseq6NDalw/06JWRqwpn8S7EHSi4yHAa9Q0NjH4VGDbdYdl3jUrXVYgl5q6IyXZDQVw0Ivwy7kIQCeJx4XA==
dsv.comadobe-idp-site-verification=7b1416f6fb3a787dcbab05784448d6643f59039dda0e81dd2be557c8f891b230
dsv.comCisco-ci-domain-verification=59dea0f96111d602f4d4e478b0aaec00eeed8e8d16c67e95af928c29be908dad
dsv.comcisco-ci-domain-verification=165365b739e4442eed9e8f448dc9b1335a951261832fdb205169a601e7b6fb70
dsv.comatlassian-domain-verification=VlhUP6RcpoE6H3dLGiV-aQ4N/SndxxxlkfwvhUOA+6kX+Lm1wXOxDRMwXj4Qxoyx
dsv.comMS=ms49189497
dsv.comv=spf1 include:spf.dsv.com -all
dsv.com52hksmrym96b97q0qz3jqsr8tkqhjb57
dsv.com_0ygb78ridcld8t7j2hngfo5wweaph91
dsv.com_6ka5cdnbeplocq4ce7b4oggwjrnufga
dsv.com_9ghmk2ziexklghoh8zpochjp021xyfp
dsv.com_c2dlo10n62hqqrnudr5lldrf6qoe27a
dsv.com_dgqyj9tuaw6wy45201oaaz38irvvw9m
dsv.com_h4vhe28sk2qme3ypze7v1tv20eramij
dsv.com_mrqscg47s65a454hiljrli8vtmh7gkz
dsv.com_umjamvc0m93xw6zws3yhscguk4nsa6a
dsv.com_wxujsn15y3swh92e95r3tdonl3bjm9w
dsv.comd365mktkey=2xoy844ou47wpwi6kkksbtg1v
dsv.comd365mktkey=5dowg8gciq2kz4eof12rjb02m
dsv.come6002200-e322-4ad9-9778-9f23de2214fc
dsv.comapple-domain-verification=DbRcjmrwJS3Qsolx
dsv.comibmid=f711a761-0a35-424c-a2db-baeafccf6496
dsv.comflexera-domain-verification-xthdjgbfjaqrigfj
dsv.comzscaler-verification-3771841-23072025-2974947216
dsv.comdocker-verification=c3ea9463-6a64-400a-b39c-42e7803b8af1
dsv.commiro-verification=ca00cfa4d844a429430d7efa74834269e2c854ed
dsv.commongodb-site-verification=epVqF4kEOp9eRbnFqs0s2TEGW1cce9WS
dsv.commongodb-site-verification=rSqYk6GofTcXvbaRE2GQntdsOIZc7fQB
dsv.comfacebook-domain-verification=snosp0aum8pqt4x9585w1w54fyx7go
dsv.comonetrust-domain-verification=6bf78fd0c091419e93e07bb4f8b1cd6e
dsv.comonetrust-domain-verification=79e9a33fe8cb41cb8e1c0e185939faf2
dsv.comanthropic-domain-verification-bebtsv=Hc2aZuDd0JIiiXxVUv1HVGDCv
dsv.comA7DA03DF402A810783995CFB279B17C2CEE99B5E54A2E235D792C5C6D98E7838
_dmarc.dsv.comv=DMARC1; p=reject; sp=reject; fo=1; rua=mailto:[email protected]; ruf=mailto:[email protected]
selector1._domainkey.dsv.comv=DKIM1; k=rsa; p=MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEA4CXFTWknumA0l+9uz1P7mn4u/m1QnIYKsb9SX97TXbNGziJ3K8vpAl/ua+cdyOBZzGMFwFJ4Ms4caqKrFaHlHKMOWJ5yV6CW9zL+aaRF7RFaLJmnC+Ad25C829LBDO0NNoZjAlNDj+SGaJoeoZ83aBOqkXeKIBrTN/tzSHUwk0k97ih1DJxJ+7YZBNWAwdsB8wngvtsvp0nQ3ntvv3ZBpOX/STh7bRlwEcbi+3d/9UVnDgSLu7/4J8x6iKI9Nl2o4pwxCnTwxqCkXNHlYTRNF3N4SC8moCugZcG8Yc6g8L8hg7BL0LkioSmztMxTymDfRAhG/xE4x53oYHjUZI8E7QIDAQAB;
selector2._domainkey.dsv.comv=DKIM1; k=rsa; p=MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAoy/484Ogz6tJNlrLrQW0WN2lh6D/IhvQ5upQJDp1l2NHXzBuvQXGOfORV5Vz/AVN4R0mNg/tRJiPwUoABN5NDLoYgyV5l1p91euQUsO+acZQeWtgRay7SOeiFoAtoOkkPfiK5urvY8G9dIA0iSxhN6veJFrdYglTVXWRo7stpCFqorJF9moHwzIp/bXSnbx+/2KaiKU/xteVTirwFK0gqaq7MVjkbyWK9xQiQpM0ZrgOUHzW3vyZtBHZytrVnigeje7FhoiPRmhGHF6AGeW59YHYBrdTKwbr7Sxa5cUTSeIawViEvgux/p1AUTk064UE/8lfSEDz8KMK61R9JSPThQIDAQAB;
s1._domainkey.dsv.comk=rsa; t=s; p=MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAxjlkOoa+JdfEUKWP7d98UmIJK5Rgxf/SSjFCku828TSzJjgkTn3wO8MUV5E1vOb1pOBSC2N2Pngjr4Wcj1iQ7W6q1EH/iE7z8J5PBIQcPQIesU2luLAhgdGzN8z4Vbh5btYz5GBVSMWVSJ2OoODNZoQB2fcx7Czcsv/H7K+XaYRK0FrU17rKAJXy8bs9BiZSiQ+oUW6+if/sAcTBBwybqpqnu5bDjSlKtCkG0yYNBpB1MWSVEkTbcrmLmDHh/tur6Lkc0JEoxXYXwgZNOBc+p4UBD39TYatC2B5CLFnOJ5qXbajwqew/1czoko9KetW1lZpg5veusrjwXcc7JUsqdwIDAQAB
s2._domainkey.dsv.comk=rsa; t=s; p=MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQCuvXT7DMFVOgPjH7N3oSUy+EvnFZMiB5UBqSwK3yCxotPF1HT+EIt9AWHsNv+pIQSxO6Y7xZKAYwgP8WeeHgFrUcElI9tiXnPChgv0k6nOL91q0COctV7cM7fGsJp+v+C5zaBASFbo89qMvhmVqMGXEZpQrCekhh11jBFpbjlZxQIDAQAB

Related IP addresses

IPv4 addresses used by dsv.com: website, name servers, mail servers and senders authorized by SPF.

IP addressUsed for/24 block
3.65.217.77Website3.65.217.0/24
3.79.142.253Website3.79.142.0/24
63.181.128.77Website63.181.128.0/24
204.74.66.1Name server udns1.cscdns.net204.74.66.0/24
204.74.111.1Name server udns2.cscdns.uk204.74.111.0/24
216.71.158.66Mail server mx1.dsv.c3s2.iphmx.com, Mail server mx2.dsv.c3s2.iphmx.com216.71.158.0/24

WHOIS of the domain dsv.com

Domain Name: DSV.COM
   Registry Domain ID: 719545_DOMAIN_COM-VRSN
   Registrar WHOIS Server: whois.corporatedomains.com
   Registrar URL: http://cscdbs.com
   Updated Date: 2026-09-21T16:20:56Z
   Creation Date: 1995-10-27T04:00:00Z
   Registry Expiry Date: 2026-10-26T04:00:00Z
   Registrar: CSC Corporate Domains, Inc.
   Registrar IANA ID: 299
   Registrar Abuse Contact Email: [email protected]
   Registrar Abuse Contact Phone: 8887802723
   Domain Status: clientTransferProhibited https://icann.org/epp#clientTransferProhibited
   Domain Status: serverDeleteProhibited https://icann.org/epp#serverDeleteProhibited
   Domain Status: serverTransferProhibited https://icann.org/epp#serverTransferProhibited
   Domain Status: serverUpdateProhibited https://icann.org/epp#serverUpdateProhibited
   Name Server: UDNS1.CSCDNS.NET
   Name Server: UDNS2.CSCDNS.UK
   DNSSEC: signedDelegation
   DNSSEC DS Data: 38781 13 2 5F53458D1181054B9DC31AB2F884A8F6D8A263DA15CE4CECA18DC83B004549C8
   URL of the ICANN Whois Inaccuracy Complaint Form: https://www.icann.org/wicf/
>>> Last update of whois database: 2026-10-02T10:58:28Z <<<

For more information on Whois status codes, please visit https://icann.org/epp

NOTICE: The expiration date displayed in this record is the date the
registrar's sponsorship of the domain name registration in the registry is
currently set to expire. This date does not necessarily reflect the expiration
date of the domain name registrant's agreement with the sponsoring
registrar.  Users may consult the sponsoring registrar's Whois database to
view the registrar's reported date of expiration for this registration.

TERMS OF USE: You are not authorized to access or query our Whois
database through the use of electronic processes that are high-volume and
automated except as reasonably necessary to register domain names or
modify existing registrations; the Data in VeriSign Global Registry
Services' ("VeriSign") Whois database is provided by VeriSign for
information purposes only, and to assist persons in obtaining information
about or related to a domain name registration record. VeriSign does not
guarantee its accuracy. By submitting a Whois query, you agree to abide
by the following terms of use: You agree that you may use this Data only
for lawful purposes and that under no circumstances will you use this Data
to: (1) allow, enable, or otherwise support the transmission of mass
unsolicited, commercial advertising or solicitations via e-mail, telephone,
or facsimile; or (2) enable high volume, automated, electronic processes
that apply to VeriSign (or its computer systems). The compilation,
repackaging, dissemination or other use of this Data is expressly
prohibited without the prior written consent of VeriSign. You agree not to
use electronic processes that are automated and high-volume to access or
query the Whois database except as reasonably necessary to register
domain names or modify existing registrations. VeriSign reserves the right
to restrict your access to the Whois database in its sole discretion to ensure
operational stability.  VeriSign may restrict or terminate your access to the
Whois database for failure to abide by these terms of use. VeriSign
reserves the right to modify these terms at any time.

The Registry database contains ONLY .COM, .NET, .EDU domains and
Registrars.