zynga.com
O domínio zynga.com responde no endereço IP 3.174.46.81. O DNS do domínio é gerenciado por Akamai, que define para onde aponta cada subdomínio. O e-mail de zynga.com passa por 2 servidores; o de maior prioridade é mxb-002e0402.gslb.pphosted.com. Também publica 37 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
- 3.174.46.81 1716s
- 3.174.46.33 1716s
- 3.174.46.114 1716s
- 3.174.46.19 1716s
AAAA Registros AAAA
- 2600:9000:28eb:1400:d:1ef8:92c0:93a1 1800s
- 2600:9000:28eb:1600:d:1ef8:92c0:93a1 1800s
- 2600:9000:28eb:d600:d:1ef8:92c0:93a1 1800s
- 2600:9000:28eb:8e00:d:1ef8:92c0:93a1 1800s
- 2600:9000:28eb:1200:d:1ef8:92c0:93a1 1800s
- 2600:9000:28eb:c000:d:1ef8:92c0:93a1 1800s
- 2600:9000:28eb:1a00:d:1ef8:92c0:93a1 1800s
- 2600:9000:28eb:d800:d:1ef8:92c0:93a1 1800s
MX Registros MX
- 10 mxb-002e0402.gslb.pphosted.com 300s
- 10 mxa-002e0402.gslb.pphosted.com 300s
NS Registros NS
- a28-64.akam.net 21161s
- a5-65.akam.net 21161s
- a26-67.akam.net 21161s
- a18-66.akam.net 21161s
- a1-193.akam.net 21161s
- a9-66.akam.net 21161s
TXT Registros TXT
- notion-domain-verification=Jw0mymoAtERFAFdlX2eXR3yFFYDIuk5k6SZAC9kg3Ak 21600s
- google-site-verification=kdmZBaG1vbmr4ltAAEvWTOb2HQrJ1RR2l8T8ZJBTdo4 21600s
- flexera-domain-verification-jitumvwpwakeeoib 21600s
- slack-domain-verification=G2Y3xDM8sUIeBuhodYEH6MiWNUpmPeFMpqwis9du 21600s
- zapier-domain-verification-challenge=1c48ff84-5540-4aa0-8984-15536baaf00b 21600s
- openai-domain-verification=dv-1Gowtxt2dlrpysFmOY2sX1Nd 21600s
- atlassian-domain-verification=MMzWQ2TqcxeKliKSzrsMVl8JE34sjUX/AAseKUOLM2alhtHAS0zrgFt4+kBiRto/ 21600s
- yandex-verification: 510c74af1163ac6e 21600s
- v=spf1 include:%{ir}.%{v}.%{d}.spf.has.pphosted.com ~all 21600s
- docker-verification=b94e94f5-1edb-4207-bf5d-66abbb2184a9 21600s
- parsec-domain-verification=td_2VdTeO754HTwnPtLuEzbj6KTLSd 21600s
- canva-site-verification=gvoFIfQN_WrgCJzaOnQcKQ 21600s
- docusign=5d2c2a42-b00e-4ab6-9245-2d3dc1a96bbe 21600s
- _7lhiun414ryd0hh0d0gnkxyulxtsole 21600s
- IAQqFsTuqa4o3FlhcIPamt_b9qb7La8 21600s
- miro-verification=daabe1956031194d18cc1f53ce74428e231634ee 21600s
- flexera-domain-verification-dbzrsvfsqaudmpht 21600s
- google-site-verification=pQNIrcVKDQQ1-3GHV8-uRp3B9qSeeGzJandaOHBehwU 21600s
- anthropic-domain-verification-ja1ymb=ytBh7vrqhMjyONJ69OcbxNDCY 21600s
- ndDPGVmJKHy+qC+zpOZzvmLcTreMDYu7dW4iFz7xyO6s+uJtxwJtrT62NmF12diyyBMuOI7KmwCBLfCeTHWWSw== 21600s
- onetrust-domain-verification=0b240979d6104e2d9c7b55d7a34fa77e 21600s
- dropbox-domain-verification=1ddaaj0d5ryl 21600s
- flexera-domain-verification-ypvnkrrffvcvcijk 21600s
- notion-domain-verification=M88iew36Fe6C7e2Ptgc1JXyeuRZ83VisNhglBKSW7tt 21600s
- stripe-verification=4017633D9378ABFCDCCFBC635F9031CF513C3CF80AE17B6928BDFDD64DB6F0E2 21600s
- MS=ms48283609 21600s
- dtm-domain-verification=I8pciPypiwmneKdfiSS6Aavs1X8MgFFIiwTsxPeVreI 21600s
- google-site-verification=wsaFZu_s9ZO4UBj_3WqYIsiNSj0zqF6-4Da6Eiye2rc 21600s
- adobe-idp-site-verification=a84b2d9a-5df8-4cc4-b725-fad34ff5962d 21600s
- workplace-domain-verification=WZ1xdAUl4q2nKQIQJzO8Zm1M9N3J3L 21600s
- apple-domain-verification=JhYMvhamYQdIBH8m 21600s
- browserstack-domain-verification=769b8c9b-dc0e-4eff-b4f3-73cd4a2356f1 21600s
- smartsheet-site-validation=3mqM1o5UDez7O-oGsvdOehI4YBJPKcYh 21600s
- autodesk-domain-verification=okIEV3d59nqzlcmaHaAD 21600s
- google-site-verification=bMnoXJ0PaJrkrJ6QyWSyaGwd31J4E1e4rlGwfn4uTvU 21600s
- meltwater_sso_20230818_TRITON-15725 21600s
- docker-verification=69372972-3805-447f-8b20-1d63ecd61154 21600s
SOA Registros SOA
- pdns1.ultradns.net 300s
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á 8 horas.