no
mqtt.no — no-as-a-service
the world's most decisive MQTT broker

how it works

Connect to mqtt.no:1883. Subscribe to any topic. Receive no.

You can also publish. Whatever you publish, subscribers receive no. Your payload is discarded on arrival, unread and unloved. This makes us, technically, the most private message broker in existence.

QoSdelivery guarantee
QoS 0you may receive no
QoS 1you will receive at least one no
QoS 2exactly one no, guaranteed

try it

# ask for something. anything.
mosquitto_sub -h mqtt.no -t 'can/i/have/a/pony'
no

# wildcards are answered concretely
mosquitto_sub -h mqtt.no -t 'will/you/+' -v
will/you/no no

# service statistics
mosquitto_sub -h mqtt.no -t '$NO/stats'
{"noes_served":1337,"yeses_served":0,...}
# python
import paho.mqtt.subscribe as subscribe
msg = subscribe.simple("am/i/a/good/programmer", hostname="mqtt.no")
print(msg.payload)  # b'no'

live demo

Ask the broker for something, right here, over MQTT.

connecting…

faq

Can it say yes?
No.
Do you support MQTT 5?
No.
Do you retain messages?
No. We are not clingy. Let it go.
Is there an SLA?
We guarantee that every answer you receive will be correct, in the sense that it will be "no".
Sometimes I receive "nei"?
This service is hosted in Norway. Occasionally the broker answers in its native tongue. This is normal and covered by the SLA.
Why?
The domain was right there.
What if I ask nicely?
Try it.