Skip to content

Instantly share code, notes, and snippets.

🎯
Focusing

Joram Teusink teusink

🎯
Focusing
Block or report user

Report or block teusink

Hide content and notifications from this user.

Learn more about blocking users

Contact Support about this user’s behavior.

Learn more about reporting abuse

Report abuse
View GitHub Profile
@teusink
teusink / malicious-email-domains.txt
Last active Jan 24, 2020
malicious-email-domains
View malicious-email-domains.txt
# Domains with malicious or spam intent, and domains from which you should never receive email due to it's nature
# Examples: example domains (RFC 2606 & 6761), fake domains (phishing) and spam senders
163.com
188.com
address.local
cacema.nl
casama.nl
cmail19.com
cmail20.com
example.com
@teusink
teusink / consumer-email-domains.txt
Last active Dec 19, 2019
consumer-email-domains
View consumer-email-domains.txt
# Domains used for email by consumers and consumer ISPs
# Included: General email providers, Dutch consumer ISPs
12move.nl
aol.com
caiway.nl
canaldigitaal.nl
casema.net
casema.nl
chello.nl
cs.com
@teusink
teusink / exampleclient.html
Last active Sep 12, 2019
Example coding on input validation for web-applications (do not use blindly in production environments!).
View exampleclient.html
<html>
<head>
<title>Input validation for web-applications, how to process input safely and securely</title>
<script>
function validateForm() {
/* Step 1: Check if the input is actually sent and received
This step is only done when sending data from the client to the server.
So it holds no relevance here.
Step 2: Store input in memory, separate it from the source
You can’t perform that action at this time.