Finding IP address of sender in Yahoo, Gmail, Hotmail.
Finding IP Address Of the Sender In Hotmail!!
# Log into your Hotmail account with your username and password.
# Click on the Mail tab on the top.
# Open the mail.
# If you do not see the headers above the mail message, your headers are not displayed . To display the headers,
* Click on Options on the top-right corner
* In the Mail Options page, click on Mail Display Settings
* In Message Headers, make sure Advanced option is checked.
* Click on Ok button
* Go back to the mails and open that mail.
# If you find a header with X-Originating-IP: followed by an IP address, that is the sender's IP address
* Hotmail headers : Daniel ,In this case the IP address of the sender
is [68.34.60.59]. This is be the IP address of the sender.
# If you find a header with Received: from followed by a Gmail proxy like this
* Hotmail headers : Daniel
* Look for Received: from followed by IP address within square
brackets[]. In this case, the IP address of the sender is
[69.140.7.58].
# Or else if you have headers like this
* Hotmail headers : Daniel
* Look for Received: from followed by IP address within square brackets[].
In this case, the IP address of the sender is [61.83.145.129] .
# If you have multiple Received: from headers, eliminate the ones that have proxy.anyknownserver.com.
Finding IP Address of the sender in Yahoo Mail!!
# Log into your Yahoo! mail with your username and password.
# Click on Inbox or whichever folder you have stored your mail.
# Open the mail.
# If you do not see the headers above the mail message, your headers are not displayed . To display the headers,
* Click on Options on the top-right corner
* In the Mail Options page, click on General Preferences
* Scroll down to Messages where you have the Headers option
* Make sure that Show all headers on incoming messages is selected
* Click on the Save button
* Go back to the mails and open that mail.
# You should see similar headers like this:
* Yahoo! headers : Daniel.
# Look for Received: from followed by the IP address between square brackets [ ]. Here, it is 202.65.138.109.
# That is be the IP address of the sender!
Finding IP Address of the sender in Gmail !!
When
you receive an email, you receive more than just the message. The email
comes with headers that carry important information that can tell where
the email was sent from and possibly who sent it. For that, you would
need to find the IP address of the sender. The tutorial below can help
you find the IP address of the sender.
* Log into your Gmail account with your username and password.
* Open the mail.
* To display the headers,
o Click on More options corresponding to that thread. You should get a bunch of links. Click on Show original
* You should get headers like this:
o Gmail headers : Daniel
* Look for Received: from followed by a few hostnames and an IP address
between square brackets. In this case, it is 65.119.112.245.
* That is be the IP address of the sender!!
NOTE:=
This will not work if the sender uses anonymous proxy servers.
Hack your Server to Speed up Internet explorer "With out any software"
# Open the Registry editor.
go to Start -->Run and typing regedit.
# Once in Registry editor window is opened, navigate to the key:
HKEY_CURRENT_USER\Software\microsoft\Windows\CurrentVersion\InternetSettings.
#Now right click on the window on your right and add a New DWORD Value.
Rename it MaxConnectionsPerServer.
# Next right click on MaxConnectionsPerServer to edit the Dword Value.
Choose a base.If it is Hexadecimal,set the value to 99.If you opt for Decimal,set it to 153.
# Create another DWORD and rename it MaxConnectionsPer1_0Server.
Here,too,put the value mentioned above.
#Restart Internet Explorer and watch the boost you get in your connection.
DNS TRICK:
When
you connect to a website,your computer sends information back
forth.Some of this deals with resolving the site name to an IP
address.This is the stuff that TCP/IP really deals with,not words.You
can increase the DNS cache by a simple Registry tweak.
#Open Notepad and copy-paste the
following code and save it with the filename dnscache.reg .
This is what you have to copy:
Windows registry Editor Version 5.00
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Dnscache\Parameters]
"CacheHashTableBucketSize"=dword:00000001
"CacheHashTableSize"=dword:00000180
"MaxCacheEntryTtlLimit"=dword:0000fa00
"MaxSOACacheEntryTtlLimit"=dword:0000012d
How To Become A Hacker
The Hacker Attitude Hackers
solve problems and build things, and they believe in freedom and
voluntary mutual help. To be accepted as a hacker, you have to behave
as though you have this kind of attitude yourself. And to behave as
though you have the attitude, you have to really believe the attitude.
But
if you think of cultivating hacker attitudes as just a way to gain
acceptance in the culture, you'll miss the point. Becoming the kind of
person who believes these things is important for you -- for
helping you learn and keeping you motivated. As with all creative arts,
the most effective way to become a master is to imitate the mind-set of
masters -- not just intellectually but emotionally as well. So, if you
want to be a hacker, repeat the following things until you believe
them:
1. The world is full of fascinating problems waiting to be solved.Being
a hacker is lots of fun, but it's a kind of fun that takes lots of
effort. The effort takes motivation. Successful athletes get their
motivation from a kind of physical delight in making their bodies
perform, in pushing themselves past their own physical limits.
Similarly, to be a hacker you have to get a basic thrill from solving
problems, sharpening your skills, and exercising your intelligence.
If
you aren't the kind of person that feels this way naturally, you'll
need to become one in order to make it as a hacker. Otherwise you'll
find your hacking energy is sapped by distractions like sex, money, and
social approval. (You also have to develop a kind of faith in your own
learning capacity -- a belief that even though you may not know all of
what you need to solve a problem, if you tackle just a piece of it and
learn from that, you'll learn enough to solve the next piece -- and so
on, until you're done.)
2. Nobody should ever have to solve a problem twice.Creative
brains are a valuable, limited resource. They shouldn't be wasted on
re-inventing the wheel when there are so many fascinating new problems
waiting out there.
To behave like a hacker, you have to believe
that the thinking time of other hackers is precious -- so much so that
it's almost a moral duty for you to share information, solve problems
and then give the solutions away just so other hackers can solve new problems instead of having to perpetually re-address old ones. (You don't have to believe that you're obligated to give all
your creative product away, though the hackers that do are the ones
that get most respect from other hackers. It's consistent with hacker
values to sell enough of it to keep you in food and rent and computers.
It's consistent to use your hacking skills to support a family or even
get rich, as long as you don't forget you're a hacker while you're
doing it.)
3. Boredom and drudgery are evil.Hackers
(and creative people in general) should never be bored or have to
drudge at stupid repetitive work, because when this happens it means
they aren't doing what only they can do -- solve new problems. This
wastefulness hurts everybody. Therefore boredom and drudgery are not
just unpleasant but actually evil.
To behave like a hacker, you
have to believe this enough to want to automate away the boring bits as
much as possible, not just for yourself but for everybody else
(especially other hackers). (There is one apparent exception to this.
Hackers will sometimes do things that may seem repetitive or boring to
an observer as a mind-clearing excercise, or in order to acquire a
skill or have some particular kind of experience you can't have
otherwise. But this is by choice -- nobody who can think should ever be
forced into boredom.)
4. Freedom is good.Hackers
are naturally anti-authoritarian. Anyone who can give you orders can
stop you from solving whatever problem you're being fascinated by --
and, given the way authoritarian minds work, will generally find some
appallingly stupid reason to do so. So the authoritarian attitude has
to be fought wherever you find it, lest it smother you and other
hackers.
(This isn't the same as fighting all authority. Children
need to be guided and criminals restrained. A hacker may agree to
accept some kinds of authority in order to get something he wants more
than the time he spends following orders. But that's a limited,
conscious bargain; the kind of personal surrender authoritarians want
is not on offer.) Authoritarians thrive on censorship and secrecy. And
they distrust voluntary cooperation and information-sharing -- they
only like `cooperation' that they control. So to behave like a hacker,
you have to develop an instinctive hostility to censorship, secrecy,
and the use of force or deception to compel responsible adults. And you
have to be willing to act on that belief.
5. Attitude is no substitute for competence.To
be a hacker, you have to develop some of these attitudes. But copping
an attitude alone won't make you a hacker, any more than it will make
you a champion athlete or a rock star. Becoming a hacker will take
intelligence, practice, dedication, and hard work.
Therefore, you
have to learn to distrust attitude and respect competence of every
kind. Hackers won't let posers waste their time, but they worship
competence -- especially competence at hacking, but competence at
anything is good. Competence at demanding skills that few can master is
especially good, and competence at demanding skills that involve mental
acuteness, craft, and concentration is best. If you revere competence,
you'll enjoy developing it in yourself -- the hard work and dedication
will become a kind of intense play rather than drudgery. And that's
vital to becoming a hacker. Basic Hacking Skills The hacker attitude is
vital, but skills are even more vital. Attitude is no substitute for
competence, and there's a certain basic toolkit of skills which you
have to have before any hacker will dream of calling you one.
This
tookit changes slowly over time as technology creates new skills and
makes old ones obsolete. For example, it used to include programming in
machine language, and didn't until recently involve HTML. But in late
1996 it pretty clearly includes the following:
1. Learn how to program.This,
of course, is the fundamental hacking skill. In 1997 the one language
you absolutely must learn is C (though it's not the one to try learning
first thing). But you aren't a hacker or even merely a programmer if
you only know one language -- you need to learn how to think about
programming problems in a general way, independent of any one language.
To be a real hacker, you need to have gotten to the point where you can
learn a new language in days by relating what's in the manual to what
you already know. This means you should learn several very different
languages.
Besides C, you should also learn at least LISP and Perl
(and Java is pushing hard for a place on the list). Besides being the
most important hacking languages, these each represent very different
approaches to programming, and all will educate you in valuable ways. I
can't give complete instructions on how to learn to program here --
it's a complex skill. But I can tell you that books and courses won't
do it (many, maybe most of the best hackers are self-taught). What will do it is (a) reading code and (b) writing code.
Learning to program is like learning to write good natural language.
The best way to do it is to read some stuff written by masters of the
form, write some things yourself, read a lot more, write a little more,
read a lot more, write some more ... and repeat until your writing
begins to develop the kind of strength and economy you see in your
models. Finding good code to read used to be hard, because there were
few large programs available in source for fledgeling hackers to read
and tinker with. This has changed dramatically; free software, free
programming tools, and free operating systems (all available in source,
and all built by hackers) are now widely available. Which brings me
neatly to our next topic...
2. Get one of the free UNIXes and learn to use and run it.I'm
assuming you have a personal computer or can get access to one (these
kids today have it so easy :-)). The single most important step any
newbie can take towards acquiring hacker skills is to get a copy of
Linux or one of the free BSD-Unixes, install it on a personal machine,
and run it.
Yes, there are other operating systems in the world
besides Unix. But they're distributed in binary -- you can't read the
code, and you can't modify it. Trying to learn to hack on a DOS or
Windows machine or under MacOS is like trying to learn to dance while
wearing a body cast. Besides, Unix is the operating system of the
Internet. While you can learn to use the Internet without knowing Unix,
you can't be an Internet hacker without understanding it. For this
reason, the hacker culture today is pretty strongly Unix-centered.
(This wasn't always true, and some old-time hackers aren't happy about
it, but the symbiosis between Unix and the Internet has become strong
enough that even Microsoft's muscle doesn't seem able to seriously dent
it.) So, bring up a Unix -- I like Linux myself but there are other
ways. Learn it. Run it. Tinker with it. Talk to the Internet with it.
Read the code. Modify the code. You'll get better programming tools
(including C, Lisp, and Perl) than any Microsoft operating system can
dream of, you'll have fun, and you'll soak up more knowledge than you
realize you're learning until you look back on it as a master hacker.
3. Learn how to use the World Wide Web and write HTML.Most
of the things the hacker culture has built do their work out of sight,
helping run factories and offices and universities without any obvious
impact on how non-hackers live. The Web is the one big exception, the
huge shiny hacker toy that even politicians admit is changing
the world. For this reason alone (and a lot of other good ones as well)
you need to learn how to work the Web.
This doesn't just mean
learning how to drive a browser (anyone can do that), but learning how
to write HTML, the Web's markup language. If you don't know how to
program, writing HTML will teach you some mental habits that will help
you learn. So build a home page. But just having a home page isn't
anywhere near good enough to make you a hacker. The Web is full of home
pages. Most of them are pointless, zero-content sludge -- very
snazzy-looking sludge, mind you, but sludge all the same .
Status in
the Hacker Culture Like most cultures without a money economy,
hackerdom runs on reputation. You're trying to solve interesting
problems, but how interesting they are, and whether your solutions are
really good, is something that only your technical peers or superiors
are normally equipped to judge.
Accordingly, when you play the
hacker game, you learn to keep score primarily by what other hackers
think of your skill (this is why you aren't really a hacker until other
hackers consistently call you one). This fact is obscured by the image
of hacking as solitary work; also by a hacker-cultural taboo (now
gradually decaying but still potent) against admitting that ego or
external validation are involved in one's motivation at all.
Specifically, hackerdom is what anthropologists call a gift culture.
You gain status and reputation in it not by dominating other people,
nor by being beautiful, nor by having things other people want, but
rather by giving things away. Specifically, by giving away your time,
your creativity, and the results of your skill. There are basically
five kinds of things you can do to be respected by hackers:
1. Write free software.The
first (the most central and most traditional) is to write programs that
other hackers think are fun or useful, and give the program sources to
the whole hacker culture to use.
Hackerdom's most revered demigods
are people who have written large, capable programs that met a
widespread need and given them away, so that now everyone uses them.
2. Help test and debug free softwareThey
also serve who stand and debug free software. In this imperfect world,
we will inevitably spend most of our software development time in the
debugging phase. That's why any free-software author who's thinking
will tell you that good beta-testers (who know how to describe symptoms
clearly, localize problems well, can tolerate bugs in a quickie
release, and are willing to apply a few simple diagnostic routines) are
worth their weight in rubies. Even one of these can make the difference
between a debugging phase that's a protracted, exhausting nightmare and
one that's merely a salutory nuisance.
If you're a newbie, try to
find a program under development that you're interested in and be a
good beta-tester. There's a natural progression from helping test
programs to helping debug them to helping modify them. You'll learn a
lot this way, and generate good karma with people who will help you
later on.
3. Publish useful information.>Another
good thing is to collect and filter useful and interesting information
into Web pages or documents like FAQs (Frequently Asked Questions
lists), and make those generally available.
Maintainers of major technical FAQs get almost as much respect as free-software authors.
4. Help keep the infrastructure working.The
hacker culture (and the engineering development of the Internet, for
that matter) is run by volunteers. There's a lot of necessary but
unglamorous work that needs done to keep it going -- administering
mailing lists, moderating newsgroups, maintaining large software
archive sites, developing RFCs and other technical standards.
People
who do this sort of thing well get a lot of respect, because everybody
knows these jobs are huge time sinks and not much fun as playing with
code. Doing them shows dedication.
Q: What language should I learn first?HTML, if you don't already know it. There are a lot of glossy, hype-intensive bad HTML books out there, and distressingly few good ones. The one I like best is HTML: The Definitive Guide.
When you're ready to start programming, I would recommend starting with Perl or Python. C is really important, but it's also much harder. Q: How can I get started? Where can I get a free Unix?Elsewhere
on this page I include pointers to where to get a Linux. To be a hacker
you need motivation and initiative and the ability to educate yourself.
Start now...
No comments:
Post a Comment