affirm.com
O domínio affirm.com responde no endereço IP 172.66.0.33. Esse endereço pertence à Cloudflare, Inc., sediada em Canada. O DNS do domínio é gerenciado por Amazon Route 53, que define para onde aponta cada subdomínio. O e-mail de affirm.com passa por 3 servidores; o de maior prioridade é mailstream-central.mxrecord.mx. Também publica 41 registros TXT, usados para verificar a propriedade do domínio em serviços externos e para configurar a segurança do e-mail com SPF, DKIM e DMARC.
A Registros A
- 172.66.0.33 10s
- 162.159.140.33 10s
MX Registros MX
- 10 mailstream-central.mxrecord.mx 300s
- 20 mailstream-east.mxrecord.io 300s
- 20 mailstream-west.mxrecord.io 300s
NS Registros NS
- ns-614.awsdns-12.net 21600s
- ns-1890.awsdns-44.co.uk 21600s
- ns-1463.awsdns-54.org 21600s
- ns-217.awsdns-27.com 21600s
TXT Registros TXT
- docker-verification=7ac102e0-2b62-4b05-b134-775363b687a2 60s
- stripe-verification=3b73576e1b62f90177c431aed31f2c31a2db959eeae803df79170108c715258d 60s
- decagon-domain-verification-rx2vg4=xMQQmURySInNzb3Q753GcsV2n 60s
- _qm6p025ab7k2h7kb2y0j0zp9cwscrk9 60s
- pardot963153=538c428c1d9495f89dc9645e5ab71a6a39ad535358c9ac950d1b513070c5eebe 60s
- atlassian-sending-domain-verification=d1e7e26c-2a5c-4306-9df8-0e600bc70f7e 60s
- jumio-up-idp-domain-verification=96ab6d36-87c5-4b60-b28f-52d4b142b4d5 60s
- google-site-verification=pAkhUEXOAsw03YML584P4Mz6AGWKrI_rvVMIlMA4TMU 60s
- pardot778433=e67349940141eb000ae0e650dc81b761d64a27f949669078aec081322b1cbb6c 60s
- canva-site-verification=tICckyw9TNkjWqLhWySfNQ 60s
- stripe-verification=8894522d609849b1342f894c8055a03aa1ea7a88b8526f50aeb2d7721c4f8291 60s
- 4ljp7ydys3rtqbxq2yjdqrg9z321lq2b 60s
- sending_domain778433=c2dbea95d44d98d2a63c7469add3164700dbec73184e3037fa85361f93ec7ff3 60s
- HZIXGSRIU 60s
- docusign=b06e9be3-7666-4868-9dcc-4170a01f13fa 60s
- stripe-verification=2759d29e60c0bae7d9e8212a26bc1ec10e7908af6f0522bf956e547af7208cad 60s
- anthropic-domain-verification-h8f8k6=PpUd4cztMwsLI1DtU02QAu6j8 60s
- mongodb-site-verification=fqxbrWhHRvG385BWYMqDU3TDjQLSGHpg 60s
- notion-domain-verification=GwCK7iKBVct6TTvYCzMWbPgFaKUtZqdSrc9ZTQEDZ42 60s
- ca3-4f17d21d484146598a0674fbbbe45ecd 60s
- google-site-verification=s822qoydlNAOABuINWk0Znrj67HclLkvZ2VXCX6Nmhc 60s
- stripe-verification=ee3426c0fb21c0e8a3f1f5368401b06dc9b9eeb94d04f3ea91bf9e8223ecb3ec 60s
- sending_domain963153=538c428c1d9495f89dc9645e5ab71a6a39ad535358c9ac950d1b513070c5eebe 60s
- whz0k8v6zgmqlf35g8mlgtpjjxvjwvlg 60s
- smartsheet-site-validation=tqVQ74cZA1pKsWlc_D5QlMPNb8vYtvNb 60s
- slack-domain-verification=Zm7pKyRJuiFUsnxgltPQQC8Tp8Kxep2b29afZgy7 60s
- jamf-site-verification=szXyQtQBT9BqzeGBWTKfSw 60s
- stripe-verification=2d0b5051e630a87b101bdb649af6aab1469d7dfb8e724193dff3c74e184a9047 60s
- status-page-domain-verification=987w3nfgs7sg 60s
- ZOOM_verify_Pcvm9macqAX0TOiB7I4IH8 60s
- v=spf1 include:%{i}._ip.%{h}._ehlo.%{d}._spf.vali.email ~all 60s
- atlassian-domain-verification=DNaiSBS5ThZ8raU2CEfYYtOMwoTp18LXzmzqIAqebu9p01eO5kNlarSrfiBcHdv3 60s
- google-site-verification=oPKjTfgSY7Gb_ICYHM4lsKIvTDIumzw51ULdQByWEpI 60s
- facebook-domain-verification=mljae013pphr1v7s9qmjr1od0q4b37 60s
- openai-domain-verification=dv-g5d0T9rsUBFcnyS05B4NGInp 60s
- parallels-domain-verification=ca3b420b7d2543a59ed0bbd750f850e30ff2363e91444abf87ec5ed6397d5f4b 60s
- docusign=73b980e5-4728-47f9-92ed-d2319fef15e2 60s
- _globalsign-domain-verification=VPemhDee0EKRXi0IPzeSUrn849jHevrjIaTeDYOTZ4 60s
- onetrust-domain-verification=c63ef161ba274c75aefba3883ca2fc05 60s
- pardot778433=fb24e220f454dd50a1a8eb4ce4fb9e03ce8a578f671906e6a66968e824c5e169 60s
- cursor-domain-verification-8x01t1=NWLM4fVaIkaxy6uhunmiMP9vm 60s
SOA Registros SOA
- ns-1890.awsdns-44.co.uk 900s
O que significa cada registro
- A e AAAA: o endereço IP do servidor, em IPv4 e IPv6.
- MX: os servidores que recebem o e-mail do domínio. O número é a prioridade; o menor é tentado primeiro.
- NS: os servidores de nomes, que têm a palavra final sobre o DNS do domínio.
- TXT: texto livre. Usado sobretudo para SPF, DKIM e DMARC, e para verificar a propriedade perante terceiros.
- TTL: por quantos segundos o dado pode ficar em cache antes de perguntar de novo.
Consultado há 6 horas.