Dataweaz

ayvens.com

Summary

Registrar
Nameshield SAS
Status
clientDeleteProhibited
Created on
December 22, 2022
Expires on
December 22, 2026
Name servers
tigdns01.socgen.com, tigdns02.socgen.com, tigdns06.socgen.com, tigdns05.socgen.com
Mail servers
mail.iap.socgen.com, secmail.iap.socgen.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 ayvens.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; fo=1; ri=3600; 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 ayvens.com.

RuleValueResult
includespf.mailjet.comAllowed
include_spf-a.iap.socgen.comAllowed
includesendgrid.netAllowed
exists%{i}._spf.mta.salesforce.comAllowed
includeamazonses.comAllowed
includespf1.satmetrix.comAllowed
ip4217.29.35.204Allowed
ip62a00:b580:8000:12:95b1:c54e:2537:d0d9Allowed
ip62a00:b580:8000:12:9d60:e579:b853:ea41Allowed
ip491.221.100.22Allowed
all—Rejected

Top-level DNS lookups: 6 of 10 allowed

Record

v=spf1 include:spf.mailjet.com include:_spf-a.iap.socgen.com include:sendgrid.net exists:%{i}._spf.mta.salesforce.com include:amazonses.com include:spf1.satmetrix.com ip4:217.29.35.204 ip6:2a00:b580:8000:12:95b1:c54e:2537:d0d9 ip6:2a00:b580:8000:12:9d60:e579:b853:ea41 ip4:91.221.100.22 -all

E-mail signing (DKIM)

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

SelectorLikely serviceKeyStatus
s1SendGridRSA 2048 bitsActive
s2SendGridRSA 1024 bits · shortActive
mailjetMailjetRSA 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 ayvens.com arrive; SPF, DKIM and DMARC let mail servers check that an e-mail claiming to come from ayvens.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 @ayvens.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

ayvens.com  MX  10 mx1.ayvens.com.
ayvens.com  MX  20 mx2.ayvens.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.ayvens.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

ayvens.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.ayvens.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.ayvens.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.ayvens.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.ayvens.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 ayvens.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
tigdns01.socgen.com193.178.155.113
tigdns02.socgen.com193.178.155.114
tigdns06.socgen.com194.119.1.10
tigdns05.socgen.com194.119.0.10

Mail servers (MX)

MX records point to the servers that receive e-mails sent to the domain, that is to @ayvens.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
10mail.iap.socgen.com194.119.31.10
10secmail.iap.socgen.com194.119.41.10

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.ayvens.com.

NameContent
ayvens.comgnfwjn66ympdqk4rv5nlybqxyehivu7o.dkim.amazonses.com
ayvens.com3qndecpriryvku63apmlcdksjyfh6yye.dkim.amazonses.com
ayvens.comxnwdyyn4fbtmprcax6df7keymkogohup.dkim.amazonses.com
ayvens.com87cd17adabe7b3dec53cbe0267b633ea
ayvens.com_hfgkrybfrdm9bzor2729uffr6q1azbt
ayvens.comv=spf1 include:spf.mailjet.com include:_spf-a.iap.socgen.com include:sendgrid.net exists:%{i}._spf.mta.salesforce.com include:amazonses.com include:spf1.satmetrix.com ip4:217.29.35.204 ip6:2a00:b580:8000:12:95b1:c54e:2537:d0d9 ip6:2a00:b580:8000:12:9d60:e579:b853:ea41 ip4:91.221.100.22 -all
ayvens.comMS=ms78715967
ayvens.comxb596rfgcsqv0lb056brb3ylnwgxpcxz
ayvens.comSFMC-s2Odd2opwFz7Mn3Avibl62IRTG8Csifs-XOOsPjV
ayvens.comatlassian-domain-verification=hyqvcRF3j/BGSLsCVKBbpK5FjcTh3jolKH1/Zu3qM1YTs/ogt+7guL5GqmcMZjyK
ayvens.comq6zd7wxgkytbh5zgy460pknngfzp837j
ayvens.comgoogle-site-verification=iBUFn8YQGLYxz83YD394Vgis4B666173zKlPZ7T4WIE
ayvens.commandrill_verify.iB9GmFsP1PgpNHNe6TkGBg
ayvens.compexip-ms-tenant-domain-verification=afadc7d4-1eca-4fcd-a958-2c6407fb52aa
ayvens.compexip-portal-domain-verification=afadc7d4-1eca-4fcd-a958-2c6407fb52aa
ayvens.com_98lrhbtj4ii2hjcld8j6x1jmg36th32
ayvens.com4qywg15ypnq31kmzy7vkfybr4mv33ndj
ayvens.comfacebook-domain-verification=4jbj172dd46mm33479g99a1t9qyp3c
ayvens.commandrill_verify.7PcZcROYhJ5aii17d-TwwQ
ayvens.comduo_sso_verification=8zu4A9a9DJ8jTBjRW0Pu3PIHO14nqPjhyyfQSKksOzwywPskAvXJq2LQa7g3x7ss
ayvens.comk=rsa; p=MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQCbG3u9iZm0Kgmfo7gGeWmlQpYZuhIISpWQK4gA3pypbp55VfeI3TY+RcQ4EYuxw4qEyINCWhygXQnM5jMdg2F78kS277DiVoyOuLwcBexZlq+rIc1GDvpwpVkdu81tMRl2Xma+2Ip64y+7xpXeDKqoO8BNf9Ha2q8YS4EpyamwowIDAQAB
ayvens.com_sguew4e7ywztvhqpuzbcvq2m9zc1y9k
ayvens.comgoogle-site-verification=rX0JM_nEnBtA7e8jlxMemWTUgVGv7INJA9vUz8F1Yg8
ayvens.comzoho-verification=zb88165779.zmverify.zoho.in
ayvens.comsendgrid.net
ayvens.comdtm-domain-verification=9RLMndXCXlfsaoywS0lYys96DRt6tWYmagq0T_IHjQ4
ayvens.com_6ikq5c6j09ffgms5u9t61zoiolp1c6m
_dmarc.ayvens.comv=DMARC1; p=reject; fo=1; ri=3600; rua=mailto:[email protected]; ruf=mailto:[email protected]
s1._domainkey.ayvens.comk=rsa; t=s; p=MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEA2X3yTTuXmtN7VZHEHOQOOt4VyH+uBVoSt1upm0SNdgge5TKudX9xfTl4cyYW0fUkeB1NtwmnM6nOlENkSu8wZc89lQ5x0aYgP8HphQgLdrB4mJJy5Ao1Xc0v1VdC/+981TI5zaoDz60FBohkUydrIpuDWwTKa+5IgNSgHGnlDJthQJMZSFFBG8n1NABjK9Msm7hRyNCe7kks8U1wdNuSemMrk5DvJc1S+waNlNID6lyV2kDMBggOXeQBga+uTGIQ/a/G9Rjs28PjnpUIqevXmZ8cYefYqFAmxFaoR/lDiqyBlL5rXkPG1Yv2h2E9UZNXhKE8fiqTFcfx9rTv1sLPjQIDAQAB
s2._domainkey.ayvens.comk=rsa; t=s; p=MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQCu5zBudaOOG9pQupAO42NxcQWMRVn1QfjvoTAMBHcsFtsEqFEarWbHx04UAGww4qX8ZVntgtumQxwo3taoa13c6dHEY5UKNdB+Z0UzWmhvqfcF1xKdiLIXa2g3sABC4jg0PDGPQW9h4Og519nHoOVHMJsYGfLLy0cVlQA2eAlLfwIDAQAB
mailjet._domainkey.ayvens.comk=rsa; p=MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQDqtdCytop3i0L35OrvSI5zG8QxFNH3dnH1UEnMrB92vdiTgQ/Z06FOnpvV5Ja/NCuQg5sHZh/rJUKJoCkBttgEOSr4oS6SXQDc52bNxeLgm5yoBYjHgkvjTfwyZyGZNL+htIgp/OiZaBgh1P5cdMbx+zEv172D23iQVdatJdQ6/wIDAQAB

Related IP addresses

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

IP addressUsed for/24 block
52.223.49.143Website52.223.49.0/24
35.71.146.240Website35.71.146.0/24
193.178.155.113Name server tigdns01.socgen.com193.178.155.0/24
193.178.155.114Name server tigdns02.socgen.com193.178.155.0/24
194.119.1.10Name server tigdns06.socgen.com194.119.1.0/24
194.119.0.10Name server tigdns05.socgen.com194.119.0.0/24
194.119.31.10Mail server mail.iap.socgen.com194.119.31.0/24
194.119.41.10Mail server secmail.iap.socgen.com194.119.41.0/24
217.29.35.204Authorized by SPF217.29.35.0/24
91.221.100.22Authorized by SPF91.221.100.0/24

WHOIS of the domain ayvens.com

Domain Name: AYVENS.COM
   Registry Domain ID: 2746371447_DOMAIN_COM-VRSN
   Registrar WHOIS Server: whois.nameshield.net
   Registrar URL: http://www.nameshield.com
   Updated Date: 2025-12-20T23:22:18Z
   Creation Date: 2022-12-22T10:06:09Z
   Registry Expiry Date: 2026-12-22T10:06:09Z
   Registrar: Nameshield SAS
   Registrar IANA ID: 1251
   Registrar Abuse Contact Email: [email protected]
   Registrar Abuse Contact Phone: +33241182828
   Domain Status: clientDeleteProhibited https://icann.org/epp#clientDeleteProhibited
   Domain Status: clientTransferProhibited https://icann.org/epp#clientTransferProhibited
   Domain Status: clientUpdateProhibited https://icann.org/epp#clientUpdateProhibited
   Name Server: TIGDNS01.SOCGEN.COM
   Name Server: TIGDNS02.SOCGEN.COM
   Name Server: TIGDNS05.SOCGEN.COM
   Name Server: TIGDNS06.SOCGEN.COM
   DNSSEC: unsigned
   URL of the ICANN Whois Inaccuracy Complaint Form: https://www.icann.org/wicf/
>>> Last update of whois database: 2026-10-02T12:55:43Z <<<

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.