Since this question's floated up to to the top of the front page, I'm going to give my contrarian answer, which is: obfuscate nearly no technical data in your question.

Michael has a point inasmuch as some data are supposed to be secret, and you shouldn't post them. Passwords, SSL secret keys (don't laugh, it's happened, though I can no longer find the post), pre-shared keys of all types,: all these are supposed to be secret, and you shouldn't post them. But usernames? Post them; if your security is dependent on keeping the usernames secret, it's bad security. Domain names? Post them. IP addresses? Post them. Mail headers? Post them.

Why do I say this? This question would have taken significantly longer to solve without knowing the address; this question, and this one would have taken significantly longer to solve without the domain name in question. I could quote tens more examples, just from my own canon.

Could they have been solved if those data had been redacted. Yes, of course; but it would have taken longer. Instead of being able to test hypotheses ourselves, we'd've had to guess, and wait for the OP to clarify. In some cases, the lack of redaction helps with the formation of hypotheses in the first place.

When you come to post on SF, you're a supplicant in need of assistance, so anything you can do to make it easier for other people to help you is a good thing.

I'm sorry if you don't want to embarrass your company, or if there's some idiot local security-through-obscurity policy that forbids you to disclose anything, down to the price of the coffee in the company machine. You've got a problem, or you wouldn't be posting here; don't be so discourteous to the pool of potential helpers as to make their lives deliberately difficult.

Obfuscation in an answer is different. There, you're trying to help. It may be that your answer is less helpful with redaction, but that's your call as a helper. The community will judge by voting, as it should.

Since this question's floated up to to the top of the front page, I'm going to give my contrarian answer, which is: obfuscate nearly no technical data in your question.

Michael has a point inasmuch as some data are supposed to be secret, and you shouldn't post them. Passwords, SSL secret keys (don't laugh, it's happened, though I can no longer find the post), pre-shared keys of all types,: all these are supposed to be secret, and you shouldn't post them. But usernames? Post them; if your security is dependent on keeping the usernames secret, it's bad security. Domain names? Post them. IP addresses? Post them. Mail headers? Post them.

Why do I say this? This question would have taken significantly longer to solve without knowing the address; this question, and this one would have taken significantly longer to solve without the domain name in question. I could quote tens more examples, just from my own canon.

Could they have been solved if those data had been redacted. Yes, of course; but it would have taken longer. Instead of being able to test hypotheses ourselves, we'd've had to guess, and wait for the OP to clarify. In some cases, the lack of redaction helps with the formation of hypotheses in the first place.

When you come to post on SF, you're a supplicant in need of assistance, so anything you can do to make it easier for other people to help you is a good thing.

I'm sorry if you don't want to embarrass your company, or if there's some idiot local security-through-obscurity policy that forbids you to disclose anything, down to the price of the coffee in the company machine. You've got a problem, or you wouldn't be posting here; don't be so discourteous to the pool of potential helpers as to make their lives deliberately difficult.

Obfuscation in an answer is different. There, you're trying to help. It may be that your answer is less helpful with redaction, but that's your call as a helper. The community will judge by voting, as it should.

Since this question's floated up to to the top of the front page, I'm going to give my contrarian answer, which is: obfuscate nearly no technical data in your question.

Michael has a point inasmuch as some data are supposed to be secret, and you shouldn't post them. Passwords, SSL secret keys (don't laugh, it's happened, though I can no longer find the post), pre-shared keys of all types,: all these are supposed to be secret, and you shouldn't post them. But usernames? Post them; if your security is dependent on keeping the usernames secret, it's bad security. Domain names? Post them. IP addresses? Post them. Mail headers? Post them.

Why do I say this? This question would have taken significantly longer to solve without knowing the address; this question would have taken significantly longer to solve without the domain name in question. I could quote tens more examples, just from my own canon.

Could they have been solved if those data had been redacted. Yes, of course; but it would have taken longer. Instead of being able to test hypotheses ourselves, we'd've had to guess, and wait for the OP to clarify. In some cases, the lack of redaction helps with the formation of hypotheses in the first place.

When you come to post on SF, you're a supplicant in need of assistance, so anything you can do to make it easier for other people to help you is a good thing.

I'm sorry if you don't want to embarrass your company, or if there's some idiot local security-through-obscurity policy that forbids you to disclose anything, down to the price of the coffee in the company machine. You've got a problem, or you wouldn't be posting here; don't be so discourteous to the pool of potential helpers as to make their lives deliberately difficult.

Obfuscation in an answer is different. There, you're trying to help. It may be that your answer is less helpful with redaction, but that's your call as a helper. The community will judge by voting, as it should.

Since this question's floated up to to the top of the front page, I'm going to give my contrarian answer, which is: obfuscate nearly no technical data in your question.

Michael has a point inasmuch as some data are supposed to be secret, and you shouldn't post them. Passwords, SSL secret keys (don't laugh, it's happened, though I can no longer find the post), pre-shared keys of all types,: all these are supposed to be secret, and you shouldn't post them. But usernames? Post them; if your security is dependent on keeping the usernames secret, it's bad security. Domain names? Post them. IP addresses? Post them. Mail headers? Post them.

Why do I say this? This question would have taken significantly longer to solve without knowing the address; this question, and this one would have taken significantly longer to solve without the domain name in question. I could quote tens more examples, just from my own canon.

Could they have been solved if those data had been redacted. Yes, of course; but it would have taken longer. Instead of being able to test hypotheses ourselves, we'd've had to guess, and wait for the OP to clarify. In some cases, the lack of redaction helps with the formation of hypotheses in the first place.

When you come to post on SF, you're a supplicant in need of assistance, so anything you can do to make it easier for other people to help you is a good thing.

I'm sorry if you don't want to embarrass your company, or if there's some idiot local security-through-obscurity policy that forbids you to disclose anything, down to the price of the coffee in the company machine. You've got a problem, or you wouldn't be posting here; don't be so discourteous to the pool of potential helpers as to make their lives deliberately difficult.

Obfuscation in an answer is different. There, you're trying to help. It may be that your answer is less helpful with redaction, but that's your call as a helper. The community will judge by voting, as it should.