voip.ms - DNS, WHOIS, DMARC and SPF of the domain name

Summary

Registrar: Key-Systems
Status: active
Created on: November 29, 2006
Expires on: November 29, 2026
Name servers: chan.ns.cloudflare.com, langston.ns.cloudflare.com
Mail servers: voip-ms.mail.protection.outlook.com
DMARC: Reject
SPF: Soft
DKIM: 2 keys found
Website: See the website

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 voip.ms 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: —

Record

v=DMARC1; p=reject; sp=reject; pct=100; rua=mailto:[email protected]

Authorized senders (SPF)

Soft

E-mails sent by any other server are accepted but flagged as suspicious.

SPF lists the servers allowed to send e-mails for voip.ms.

Rule	Value	Result
a	—	Allowed
mx	—	Allowed
ip4	208.100.31.27	Allowed
ip4	45.32.161.161	Allowed
include	spf.protection.outlook.com	Allowed
include	spf.cyberimpact.com	Allowed
include	6640358.spf01.hubspotemail.net	Allowed
all	—	Suspicious

Top-level DNS lookups: 5 of 10 allowed

Record

v=spf1 a mx ip4:208.100.31.27 ip4:45.32.161.161 include:spf.protection.outlook.com include:spf.cyberimpact.com include:6640358.spf01.hubspotemail.net ~all

E-mail signing (DKIM)

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

Selector	Likely service	Key	Status
selector1	Microsoft 365	RSA 2048 bits	Active
default	—	RSA 1024 bits · short	Active

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 voip.ms arrive; SPF, DKIM and DMARC let mail servers check that an e-mail claiming to come from voip.ms 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 @voip.ms 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

voip.ms  MX  10 mx1.voip.ms.
voip.ms  MX  20 mx2.voip.ms.

What the record contains

10, 20: Priority: the server with the lowest number is tried first. Servers with equal priority share the load.
mx1.voip.ms.: 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

voip.ms  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.voip.ms, 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.voip.ms  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.voip.ms, 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.voip.ms  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 voip.ms

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.

Type	IP address
A	104.18.36.102
A	172.64.151.154

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.

Server	IP address
chan.ns.cloudflare.com	173.245.58.82
langston.ns.cloudflare.com	108.162.195.252

Mail servers (MX)

MX records point to the servers that receive e-mails sent to the domain, that is to @voip.ms 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.

Priority	Server	IP address
10	voip-ms.mail.protection.outlook.com	52.101.190.2

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.voip.ms.

Name	Content
voip.ms	google-site-verification=PMtjwpTobm1I_fFddFMoHc2_XdzO0VFjU9qI_atM1zQ
voip.ms	google-site-verification=adICSF3r0D0YJ8mVHnGU7fM_eq6U13K75o2PuPcngJI
voip.ms	google-site-verification=ni8aGwsZW-WS0bUWii1nrdGC8dE--uux5TrIoPlV1j8
voip.ms	google-site-verification=np6hXiG-TD4XVEbqb1-3WeuBivXj2tWKcmwbK8qfiEc
voip.ms	google-site-verification=zpViYwhio5zfFYNGyG7CbqufsWJYeHNBT4-4BJ5lCZ8
voip.ms	v=spf1 a mx ip4:208.100.31.27 ip4:45.32.161.161 include:spf.protection.outlook.com include:spf.cyberimpact.com include:6640358.spf01.hubspotemail.net ~all
voip.ms	yahoo-verification-key=URSVpEgz3YR10CFB5JeP3xrSLZGgJjgky7mOH0o+s28=
voip.ms	MS=1BBABE17F897F7E6CCBC1AE98CA21914EF46C10D
voip.ms	bw=O4U7NWGOvPjPOt0x63926cURaXfu2Ou6baOmmMSm1sRa
voip.ms	ca3-87fbe78f1fec41afaf660b00e2608e37
voip.ms	facebook-domain-verification=st05e3jr4cqq8qykgm0s8mpjfullb4
_dmarc.voip.ms	v=DMARC1; p=reject; sp=reject; pct=100; rua=mailto:[email protected]
selector1._domainkey.voip.ms	v=DKIM1; k=rsa; p=MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAvhblcvZ+pbfwt9dxWPJ/OaXDd2lz28CDAYtqg/zr+2BHdTZCnYO7H2uiXKpi01W5Q8IoKvAS8sQgtn4jcz+G63n9I3cbWQgUx7lRGQyk3WS65OweoL8ojJyfW77LUwg42YV0gpHeLnyM7g5ZxiOpXrzbaqhVipz3le6yPib/vXylTb3PenJJue21ErIp+XaCCrobxuDrt9B7Gyif7ereFO0qJUZ6dnP2mCT+dcBMj1lO8ONXN9nqGgi5FocRCbGl9n1GYFxxwnb2uGX6nzP37l6QR3Hd1t4qE7/SlrG0b1defTxTF9R4C8DUSI2pl9uBG7LKymJ3pfYvy5z68B3vQQIDAQAB;
default._domainkey.voip.ms	v=DKIM1;k=rsa;p=MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQCahuCL6cpTdxO8oNOC/3IYqZbsrDKfyxnTT/W29SgGqTYZA2rf4wYPt+kuAGc/b5rJVLCliTG6vBDujsLXJKE9Z66Vju9b8d9Xtv3rrrqYiBaniHiZz1VX1zx4ktx/5hE0yh0h0aEA70nOEC8Z820jG90Y/spIvdPkLAaHS5iFbwIDAQAB

Related IP addresses

IPv4 addresses used by voip.ms: website, name servers, mail servers and senders authorized by SPF.

IP address	Used for	/24 block
104.18.36.102	Website	104.18.36.0/24
172.64.151.154	Website	172.64.151.0/24
173.245.58.82	Name server chan.ns.cloudflare.com	173.245.58.0/24
108.162.195.252	Name server langston.ns.cloudflare.com	108.162.195.0/24
52.101.190.2	Mail server voip-ms.mail.protection.outlook.com	52.101.190.0/24
208.100.31.27	Authorized by SPF	208.100.31.0/24
45.32.161.161	Authorized by SPF	45.32.161.0/24

WHOIS of the domain voip.ms

Domain Name: voip.ms
Registry Domain ID: 10015-CoCCA
Updated Date: 2025-11-26T20:58:36Z
Creation Date: 2006-11-29T11:00:00Z
Registry Expiry Date: 2026-11-29T11:00:00Z
Registrar Registration Expiration Date: 2026-11-29T11:00:00Z
Registrar: Key-Systems
Registrar Street Address: Key-Systems GmbH, Im Oberen Werk 1, 66386 St. Ingbert
Registrar Email: [email protected]
Domain Status: active https://icann.org/epp#active
Domain Status: clientRenewProhibited https://icann.org/epp#clientRenewProhibited
Domain Status: clientTransferProhibited https://icann.org/epp#clientTransferProhibited
Domain Status: clientUpdateProhibited https://icann.org/epp#clientUpdateProhibited
Domain Status: clientDeleteProhibited https://icann.org/epp#clientDeleteProhibited
Registry Registrant ID: 613524-CoCCA
Name Server: chan.ns.cloudflare.com
Name Server: langston.ns.cloudflare.com
DNSSEC: unsigned
>>> Last update of WHOIS database: 2026-10-02T19:14:19.571Z <<<

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

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.  

The data is for information purposes only. MNINET 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. The compilation, repackaging, dissemination or other use of this Data is expressly prohibited.

% Query time: 416 msec
% WHEN: Fri Oct 02 19:16:00 UTC 2026