66.111.2.131
Open in
urlscan Pro
66.111.2.131
Public Scan
Submitted URL: http://66.111.2.131/
Effective URL: https://66.111.2.131/
Submission: On February 03 via api from US — Scanned from DE
Effective URL: https://66.111.2.131/
Submission: On February 03 via api from US — Scanned from DE
Form analysis
0 forms found in the DOMText Content
THIS IS THE WEB PAGE FOR SERGE, THE TOR BRIDGE DIRECTORY SERVER. If Serge reached out and touched you, no worries. It's what a bridge directory server does when a bridge is submitted to the Tor network to confirm the bridge is reachable. Enormous thanks to all the Tor bridge operators out there. Each one plays a critical role in assisting censored and surveilled internet users. To learn more about the Tor Project About Tor bridges Here's an example Tor bridge torrc on OpenBSD: SocksPort 0 # don't listen locally for SOCKS connections Log notice file /var/log/tor-notice.log # path to the log file RunAsDaemon 1 # DataDirectory /var/tor # the $TOR_DATA_DIR, usually some default on an operating system # on FreeBSD /var/db/tor ORPort 9001 IPv4Only # for a IPv4 bridge Nickname your-freeform-bridge-name # give it a name RelayBandwidthRate 6000 KBytes # bandwidth dedicated to the bridge RelayBandwidthBurst 7000 KBytes # and let it burst User _tor # ExitPolicy reject *:* # no network exit traffic BridgeRelay 1 # designate it's a bridge HeartbeatPeriod 1 hours # give us an hourly status on the log file above, while the default is 6 hours AvoidDiskWrites 1 # minimize writes to local disk ContactInfo # your contact email in case there are issues with your bridge configuration Important basic of running a Tor bridge and any other Tor server: Tor devices of all types are internet-facing network servers. Treat them with care by locking down and updating installed applications and the operating system regularly. Every Tor device should be dedicated as a Tor device, and should not be multi-functional. Run the operating system you are most comfortable building, configuring and maintaining, not the "coolest" one you've heard of. We're huge fans of the *BSDs clearly, but an operating system security is only as strong as the sysadmin building and maintaining the operating system. Make sure you configure NTPD or a replacement. Serge can't accept bridges if the bridge's time is not reasonably accurate. Regular rdate or ntpdate resets isn't the right way to do it. And ntpdate was deprecated a very long time ago anyways. AGAIN, HUGE THANKS TO ALL THE TOR BRIDGE OPERATORS OF THE WORLD. YOUR ROLE IS VITAL TO KEEPING THE ENTIRE TOR NETWORK HEALTHY AND VIBRANT!