Intelligence DNS

berkeleypayment.com

41 enregistrements DNS actuellement visibles publiquement, regroupés par type et brièvement mis en cache.

Rapport DNS permanentCopiez le lien de cette page pour partager les enregistrements actuels avec un collègue ou un hébergeur.

Ensemble d’enregistrements DNS

41 enregistrements trouvés

En cache
41 enregistrementsPage partageable

berkeleypayment.com

Résolveur récursif du système WhatIsMyIP.live

Relancer
Enregistrements d’adresse1A + AAAA
Serveurs de messagerie6Enregistrements MX
Serveurs de noms2Enregistrements NS
Politiques texte15Enregistrements TXT
A

A enregistrements

Adresse IPv4es used to reach this hostname.

1
berkeleypayment.com198.202.211.1
TTL 3,600s
MX

Enregistrements MX

Serveurs de messagerie chargés de recevoir les e-mails.

6
berkeleypayment.com10 alt3.aspmx.l.google.com
TTL 300s
berkeleypayment.com1 aspmx.l.google.com
TTL 300s
berkeleypayment.com5 alt2.aspmx.l.google.com
TTL 300s
berkeleypayment.com20 berkeleypayment-com.mail.protection.outlook.com
TTL 300s
berkeleypayment.com10 alt4.aspmx.l.google.com
TTL 300s
berkeleypayment.com5 alt1.aspmx.l.google.com
TTL 300s
NS

Enregistrements NS

Authoritative nameservers for this domain.

2
berkeleypayment.commartin.ns.cloudflare.com
TTL 3,600s
berkeleypayment.comevelyn.ns.cloudflare.com
TTL 3,600s
TXT

Enregistrements TXT

Policies and verification data such as SPF and ownership tokens.

15
berkeleypayment.comv=spf1 include:_spf.google.com include:zohocloud.ca include:transmail.net include:spf.protection.outlook.com ip4:35.182.45.133 -all
TTL 300s
berkeleypayment.comlinkedin-site-verification=62d431e6-6ea4-4bf9-8551-8258dd73d94f
TTL 300s
berkeleypayment.comDirectFedAuthUrl=https://sso.jumpcloud.com/saml2/microsoft365
TTL 300s
berkeleypayment.comzoho-verification=zb15681721.zmverify.zoho.com
TTL 300s
berkeleypayment.comgoogle-site-verification=mmM3L3t6Spv87Vk7K2YJefRed6wweQs6NL4XWqd1nS0
TTL 300s
berkeleypayment.comsophos-domain-verification=e0d9c438d08accecdd068a62d5050a588f67f7b6e081d66b9c67848fdd33d95d
TTL 300s
berkeleypayment.comzoho-verification=zb15482722.zmverify.zoho.com
TTL 300s
berkeleypayment.comanthropic-domain-verification-2ha3f4=6WDtSi35IVRAX33Oa0QZq93XM
TTL 300s
berkeleypayment.comproxy-ssl.webflow.com
TTL 300s
berkeleypayment.comapple-domain-verification=r7xRbJXoenD1XL7E
TTL 300s
berkeleypayment.comatlassian-domain-verification=vkMVolIqhpuyXREBdkMHuF9TflxMLjbrROvrBz8yc1NNGP1vqIstu/XClZU3wmRE
TTL 300s
berkeleypayment.comMS=ms40237967
TTL 300s
berkeleypayment.comatlassian-sending-domain-verification=7d10c2cd-ad69-448c-899e-bb807c6228d1
TTL 300s
berkeleypayment.comunbounce=611110
TTL 300s
berkeleypayment.comopenai-domain-verification=dv-uYKxZXwaI6OaQzqwRfW25WnZ
TTL 300s
SOA

SOA enregistrements

Autorité principale de la zone, numéro de série et valeurs temporelles.

1
berkeleypayment.comevelyn.ns.cloudflare.com dns.cloudflare.com 2405104784 10000 2400 604800 1800
TTL 1,800s
CAA

CAA enregistrements

Certificate authorities allowed to issue TLS certificates.

16
berkeleypayment.com0 issuewild godaddy.com
TTL 300s
berkeleypayment.com0 issuewild comodoca.com
TTL 300s
berkeleypayment.com0 issuewild letsencrypt.org
TTL 300s
berkeleypayment.com0 issuewild pki.goog; cansignhttpexchanges=yes
TTL 300s
berkeleypayment.com0 issuewild ssl.com
TTL 300s
berkeleypayment.com0 issuewild amazonaws.com
TTL 300s
berkeleypayment.com0 issue comodoca.com
TTL 300s
berkeleypayment.com0 issue godaddy.com
TTL 300s
berkeleypayment.com0 issue digicert.com; cansignhttpexchanges=yes
TTL 300s
berkeleypayment.com0 issue amazonaws.com
TTL 300s
berkeleypayment.com0 issue pki.goog; cansignhttpexchanges=yes
TTL 300s
berkeleypayment.com0 iodef mailto:[email protected]
TTL 300s
berkeleypayment.com0 issue letsencrypt.org
TTL 300s
berkeleypayment.com0 issue ssl.com
TTL 300s
berkeleypayment.com0 issuewild digicert.com; cansignhttpexchanges=yes
TTL 300s
berkeleypayment.com0 issuewild sectigo.com
TTL 300s
i
Les changements DNS prennent du temps

Les résolveurs mettent les enregistrements en cache selon leur TTL. Les changements récents peuvent apparaître différemment sur un autre réseau jusqu’à l’expiration du cache.

Communauté

Commentaires

Aucun commentaire approuvé pour le moment.