springtime

springtime, and everythings new: we moved hostonip to the new database. we are still sorting in servernames, but it should even now be bigger than the old one. the old db was static, the new one is dynamic: when you look up a hostname, we start some backgroundqueries automagically trying to gather more info.

when looking up hosts, you should really consider to repeat your query a minute later: you might be surprised about the findings, like we were, when we did a lookup for www.vatican.va

we fixed last bugs (looking up ips produced an error) and hope that it will stay as fast as it is now when it's grown bigger.

have fun,

tom

Where are you coming from today?

We implemented a little User-Info that's displayed on most pages and fixed a few minor bugs. Thanks to p0f and hostip.info.

Brothers im Net

hoi,
clez.net and serversniff.net are starting to team up some services.
clemens from clez.net proposed an API for services like traceroute or ping. If everything works out you'll be able to fire up traceroutes from different locations on both of our sites, maybe from even more sites round the world at some stage.
maybe you want to participate? - we are open for anyone who is willing to share services like traceroute or ping - all you need is a host where you are able to install an run software like hping, tcptraceroute etc.
drop us a note if you're interested: thomas.springer@gmail.com

Postgresql strikes back

We had perl-scripts hammering millions of new rows into our newly designed DB-Server, many of them running in parallel. The DB-Server strikes back now: It's running a postgres-thread eating up around 1 Gig RAM and 90 percent cpu-time. I don't know what's happening deep inside the db, i don't even know how to find out. i'm learning new stuff everyday but i'm still far from beeing a postgresql-geek.

I suspended the perls, giving postgres a few hours to sort things out.
I'm praying for a smll little knowledgable ghost helping out with database-design and operating. But I'm afraid I'll have to keep learning by failing, the hard way.

tom

outage

serversniff was offline for about 10 hours last night.
we had a full hd, requiring a bit of delete-action, log-tuning and finally a reboot.

after that, we were offline again, for the database didn't start with the system. i hope that everything's fixed now.

tom

serversniffs brother

serversniff's got a brother: clez.net. If I had found this site before, serversniff would not have been built, for Clemens did a very good job making many functions more mature and useful than they are at serversniff.
I like the clez.net-Layout. Serversniff used to have a similar, very plain layout, but people kept telling me that a website needs a more fancy layout.

Check it out!

tom

It's Vokswgen, and i think: lame users make lame cars

Many users want to have internal adresses checked. Guess what happens, if you try 192.168.0.1 - yup, nothing. It's a pity and i sometimes think of giving an errormessage for these adresses. Now I've seen the first failure that makes me real happy. It's only because...

We bought a car four years ago. A new Volkswagen, a New Beetle. It lasted 2 years - since then the car breaks down regularly. Many many things that shouldn't break in three year old vehicle. Expensive parts.

Volkswagen told me that the guarantee lasted two years - not a day more. Besides the "usual" stuff like inspection, oil, fluids, brakes and so on we put many thousand Euros into the New Beetle in the last 2 years. Way too much.

If you are really interested into details, send an email - I'll be happy to send you many many invoices from the friendly Volkswagen-Dealer.

And I didn't even bothered to have everything repaired.

People, whatever you do, remember me:

I WILL NEVER EVER BUY A NEW VOLKSWAGEN AGAIN. NEVER! NEVER! NEVER!

It was so happy to see that ServerSniff didn't work for Volkswagen, even if it was only because Mr. or Mrs. Volkswagen asked for a volkswagen-internal servername (a tld that is not known on the internet) on the ssl-check...

New Alpha-Version: Browsercheck

We made public a new Browsercheck that shows

• your browsers request-headers
• your browsers capabilites
• several JavaScript-Related Infos
• name and version of installed plugins
• your Java-Version
• your private IP-Number (java-based)

Find on Serversniff.net/Serversniff.de at "Tools, Browsercheck". You might consider this an "Alpha-Version" for it lacks some formatting and functionality, especially the plugin-checks on Internet Explorer. We made it public to gather a bit of experience, what browsers are around and (a silent hope) that somebody will respond what functionality you want us to add in the browsercheck. Tell us what you think, what you miss, write to thomas.springer@gmail.com.
tom

SSL-Check back online

The "old" SSL-Check is back online. The ancient OpenSSL 0.9.7e 25 Oct 2004 will be replaced with a more up to date version these days. Thanks again for the hint!

tom

SSLCheck broken

Anonymous pointed out on the wiki, that the script for checking ssl/tls/https-servers is broken. We investigate and restore functionality ASAP. Seems that the GnuTLS-Portion of the check is working while the OpenSSL-Part isn't.
We are on our way to redo the sslcheck anyway - we'll have a fully working version back online until monday, be it the old or rewritten new one.

tom