infopact.nl TXT records

TXT Human readable text
5m
Atlassian
Domain verification
atlassian-domain-verification=gPRT4ScGuZ0jvNjWFua3lOGKwfXECy8bW7bBggtQUVDLNQLUXXDeJ8pDDK6lRx4f
Digicert QuoVadis
Domain verification
QuoVadis=be01a19c-436c-48dc-ae54-be11deb5ef08
Google
Domain verification
google-site-verification=hz3WHaB1V8ieGC7-4712Rn_dKLk-x7hngJTvQ6kJqho
Microsoft
Domain verification
MS=ms87642069
bw=kMUOufsehd9gSJWgInh1YTrzTrNzZ47sqkYCTa2bXeqV
FUXqEYshtvO7fS3PgnIKo0O9Ibfa139J5lpTnBz1FqhNx+Bqa8Gzh3u312YAgsGc7vUqRr+DXSvAjHTgKBpBlw==

Question and response

Question

dig infopact.nl. TXT

Answer

infopact.nl. 300 TXT "FUXqEYshtvO7fS3PgnIKo0O9Ibfa139J5lpTnBz1FqhNx+Bqa8Gzh3u312YAgsGc7vUqRr+DXSvAjHTgKBpBlw==" infopact.nl. 300 TXT "MS=ms87642069" infopact.nl. 300 TXT "QuoVadis=be01a19c-436c-48dc-ae54-be11deb5ef08" infopact.nl. 300 TXT "atlassian-domain-verification=gPRT4ScGuZ0jvNjWFua3lOGKwfXECy8bW7bBggtQUVDLNQLUXXDeJ8pDDK6lRx4f" infopact.nl. 300 TXT "bw=kMUOufsehd9gSJWgInh1YTrzTrNzZ47sqkYCTa2bXeqV" infopact.nl. 300 TXT "google-site-verification=hz3WHaB1V8ieGC7-4712Rn_dKLk-x7hngJTvQ6kJqho" infopact.nl. 300 TXT "v=spf1 include:spf.infopact.nl include:spf.protagonist.nl include:spf.protection.outlook.com include:emsd1.com include:_spf.netwerkplan.nl include:spf.eu.exclaimer.net ip4:82.150.141.221 ~all"

Authority

infopact.nl. 172800 NS ns-1458.awsdns-54.org. infopact.nl. 172800 NS ns-1632.awsdns-12.co.uk. infopact.nl. 172800 NS ns-339.awsdns-42.com. infopact.nl. 172800 NS ns-898.awsdns-48.net.

Additional

. 0 OPT ; payload 4096, xrcode 0, version 0, flags 0

About these results

This page shows the TXT records for infopact.nl. TXT records publish arbitrary text values in DNS. They are widely used for domain verification and email-related policies such as SPF, DKIM, and DMARC.

Find other DNS records for infopact.nl:

The results on this page are freshly fetched just for you when you loaded this page. Wirewiki queried the authoritative DNS servers for infopact.nl. That means that these results are guaranteed to be accurate, because there are no caches in between that could potentially cause staleness.

To look up TXT records for another hostname or domain name, go back to TXT lookup, or use DNS lookup to find all DNS records.