Nconnect.net - Enable NumLock on the Windows 10 Login screen/Lock …

Provided by Alexa ranking, nconnect.net has ranked N/A in N/A and 9,299,994 on the world. nconnect.net reaches roughly 331 users per day and delivers about 9,925 users each month. The domain nconnect.net uses a Commercial suffix and it's server(s) are located in N/A with the IP number N/A and it is a .net domain.

Enable NumLock by default in Windows 10, Windows 8, Windows 8.1 and Windows 7 Enable NumLock by default in Windows 10, Windows 8, Windows 8.1 and Windows 7This does not require any Registry hacks or changes to system settings. Simply boot to the login screen or the Lock screen and do the following:On the Logon/Lock screen, press the NumLock key on the keyboard to turn it on.The Login screen contains a power button in the bottom right corner. Use it to reboot Windows:The next time Windows boots, NumLock will be automatically enabled. If this trick does not work for you for some reason, try the Registry tweak below. It should work in all modern Windows versions including Windows 10 and Windows 8.x.102 thoughts on “How to enable NumLock on the Logon screen and Lock screen in Windows 10” 102 thoughts on “How to enable NumLock on the Logon screen and Lock screen in Windows 10”Setting InitialKeyboardIndicators to 2 works for me in Windows 8.1 and 10. Setting it to 80000002 broke the keyboard altogether. I had to use the onscreen keyboard to get back into my computer and fix the setting.Had to use the registry editor but it worked wonderfully. Thanks so much!boa noite… **já liguei, acendi num lock e reiniciei, p quando voltar estar com o led aceso… já mudei os valores para 2 em tudo o que é lugar que tenha initialkeyboardindicators, bem como também pra 2147483650 [o valor original era 2147483648]… nada disso deu certo! quando para 2 não deu certo, fui para 2147483650… nada! os dois ficaram me enganando por alguns dias e voltaram a ficar apagados!!! todo mundo reclama desse w10! uma bomba na mão de todo mundo**abraço.boa npoite… **um danado de um corretor corrompeu meu comentário. vê se dá p entender, por favor**abraço.Oi amigo, eh que depende do sistema que voce usa, e existe mais de um local para essas chaves: tem a current user (CU, so voce), Local machine (se aplica a todos), e tem mais uma. Quando voce ver isso, ja deve ter corrigido esse problema.Yes all those steps you tried and this is not success then only one steps missing. In my case please check following conf.1. Open CONTROL PANEL2. From Ease of Access Center menu find the Make the keyboard easier to use3. Begin of screen you will see Control the mouse with the keyboard. This is mean you control mouse from keyboard. On that time you have chance control from keyboard to mouse arrows of num keypad, that time propose of Num lock key is will change. 1st Home key PgUp cursor arrow etc. 2nd this arrow other key of num keypad is will control mouse4. Last un check Turn on Mouse Keys then Apply.Thank you.control panel worked turned off numkey arrows and one other and nothing else worked regedit didn’tIn Win 10, I thought the change to 80000002 was pretty drastic, so I used the 2nd suggestion (2147483650). The original key was 2147483648 so I was more comfortable with that. It worked, so far.That’s because 80000002 (hex) and 2147483650 (dec) are the same number. It just depends if you have hex or decimal checked when you put it into the registry key.The value is a string type. Yes storing numbers in string fields. What can I say.Anyway a value of 0x80000002 should work if you are comfortable with hexadecimal notation, otherwise 2147483650 should work. Or on a 32 bit system perhaps ‭-2147483646‬ would also work depending on whether a UINT32 or an INT32 is expected. However as others have had success with 2147483650 it appears that a UINT32 is being used.Please try this to restore the NUM keys by going toControl Panel Ease of Access Center Set Up Mouse Keys Other Settings: Use mouse keys when NUM LOCK is: Make sure OFF is selected. Done! Your welcome Merry Christmas!On my computer, register’s values are in DEC format : you have to convert the value you want from HEX to DEC. (In my case : InitialKeyboardIndicators = 2147483650)The “default” change didn’t work for me. The registry hack using 80000002 did the trick though.Couldn’t believe how ridiculously easy it was. Thanks!Thats not working at Windows 10. At Restart it works every time, but not permantly after shut down! What is the Setting in Registry for Windows 10 ?Set it to 80000002setting it to 80000002 worked for me on reboot in Win10look here for the Windows 10 Registry Key:http://tweаks.com/windоws/67063/еnable-num-lock-on-thе-windows-10-lоck-scrеen/Updated the articleNone of these proposed solutions helped :( Also i have to press control shift everytime i boot up win10 because it has my layout al scrambled.It happened when i upgraded from win8.1 to win10 legit way. And after a clean install with new win10 product key. (Educational key)I posted this on the Classic Shell Forum. Does this fix it for you?I’m using Classic Shell 4.3.1 . . . I have found that in order for this setting in the Registry to work, which will make NumLock “on”:HKEY_USERS \ .DEFAULT \ Control Panel \ Keyboard \ InitialKeyboardIndicators Default: 2147483648 Change it to: 2147483650It’s necessary to [un-check] “Enable hybrid shutdown”:Classic Start Menu Settings / Main Menu / [un-check] Enable hybrid shutdown . . . (Is this primarily for Win 8, which is not used much today? Maybe it should be un-checked by default?)Please see this page for the full story:With this BIOS setting, why isn’t NumLock enabled / “On” when it gets to the Login screen? . . . https://h30434.www3.hp.com/t5/Desktop-Software-and-How-To-Questions/With-this-BIOS-setting-why-isn-t-NumLock-enabled-quot-On/m-p/6186353#M68595Setting 2147483650 in my new Windows 10 virtual machine (VMWare Fusion) worked like a charm. Thanks!Just tripped across a simple and permanent fix. Sorry I forgot to bookmark the site and so I can’t re-find it. Anyway, start your PC in the normal fashion. When your logon screen appears, tap your numbers lock key to turn it on. At the lower right corner, there is a shutdown button. Shut down right away from there. Now, reboot and your problem should be fixed. Works on Windows 10, 8.1, 8, 7. I’ve done 10 cold starts since, and it appears to be permanent. T’care, Mike {;- )@Mike R.Your suggestion doesn’t work for me either. :( Given that these proposed registry edits also fail to solve the problem it seems to be as I expected, the keyboard drivers need updating on my Logitech K520 Wireless Combo. Still awaiting feedback from Logitech on that one.reg hax didnt work for me but this solution did, cheers!Worked perfectly thank you dear :)I have had to do this on four installs and could not for the life of me remember my missing step. Thank you Mike R. Top man!setting initial keyboard to value 2 on windows 10 pro 64-bit work for me tooGreatNone of the tricks above worked for me in Australia on the new windows 10. The only way I got the number lock to stay active on the lock screen was to use a combination of methods above First – You have to change the and let set the value “InitialKeyboardIndicators” to 2147483650 My PCs original setting was 2147483648. Second – I performed a shutdown of the PC. Third – I restarted the PC and at the lock screen and my number lock was still not active. Forth – When on the logon screen, I tap your numbers lock key to turn it on then in the lower right corner of the screen I pressed the shutdown button. and complete a shut down right away from there. The next time I turned on the PC the number lock stayed active at the lock screen. Once I did this it has insured the number lock stayed active on the lock screen for last 6 shutdown.This worked for me until I shut down after logging in to windows. It seems that shutting down from the login screen and shutting down from inside windows are different processes that affect how it will start up the next time.That’s exactly the process I went through to a tee :)Thanks a lot, It worked for me ! All the other solutions didn’t work.I talked too fast. Just like Frustrated, after shuting down from inside windows Num Lock was not active anymore :-(Ohh? Which value the mentioned Registry key has now?You are welcome :)Finally a solution the worked flawlessly, thank you very much…. (Running on Win 10)Please try this to restore the NUM keys by going toControl Panel Ease of Access Center Set Up Mouse Keys Other Settings: Use mouse keys when NUM LOCK is: Make sure OFF is selected.CraigJ. just wanted to say that i have been looking for a solution and tried all these on here (UK) before on my windows 10 laptop. I have the free upgrade from 8.1 to 10 version and your “Australian” solution worked for me too. I followed your method exactly and “hey presto!” its worked ever since. Thanks againPERFECT I found it necessary to change the registry key value AND press the Numlock key at the logon screen followed by the power button (right bottom corner) THANKSI could kiss you right on the mouth! FINALLY got that annoying little toggle to work properly!! Thank you!!I’ve tried every one of the suggestions for Windows 10 in this article .. By the way I’m in Australia .. And none of them have worked for me .. Yet. So is there anyone out there who has any other ideas .. Please???Pressing the Numlock key during login and shutting it down straightaway works for me.God damn it, Douglas Lee! You’re a goddamned genius! Thats the most outstanding answer I have ever heard! You must have a goddamned I.Q. of 160! You are goddamned gifted,Douglas Lee!Although it’s not mentioned clearly here, the correct method of setting Num Lock to ON is using the Bios settings at system start. Usually you can access the Bios by pressing F8 as soon as the PC is turned on.Look for ‘Boot Settings Configuration’ and set Bootup Num-Lock [ON] then exit the bios saving any changes.Some users may find that this has stopped working under Windows 10 as is my case, I’ve tested the above registry method but that didn’t work and so I’ve just done a restart from the power button on the login screen to test further. So far so good but I haven’t yet done a cold start to see if that works. Another possible reason for this is out of date drivers for your keyboard. I have a Logitech K520 Wireless Combo and have raised this issue with Logitech for further investigation.I just found this another site and finally Num-Lock stays on…, finally!!! :)Control Panel > Power Options > ‘Choose What the Power Buttons Do’ [text link; upper left of window] > ‘Change Settings that are Currently Unavailable’ [text link; upper middle of window] > Uncheck ‘Turn On Fast Startup’ [checkbox] > Save Changes [button]Working on Windows 10Ohh! Thank you for sharing this info.You’re welcome! :)Interestingly disabling the ‘Fast Startup’ option made no difference to how quickly my machine started. The bonus is that I’m now also saving several seconds more because I no longer need to activate Num-Lock manually! Yeehaw………..WORKS!!!!!! Awesome Thank YouYES! Thank you Chris. I tried all above solutions. None other than this one worked! Windows 10 pro x64Brilliant. Thanks for this tip. Its been bugging me since I got my machine over a year ago on both Windows 8 and when upgraded to Windows 10. Now I can go to sleep happy. Thank YouThat is the usable solution. I tried all above ideas. None other than this one worked! Windows 10 pro x64You are the man!!!! Thank you!!!!!!!!thx o lotTried all the other methods without success, but this one actually works and it’s easy to follow instructions.THIS IS THE ONE! DO THIS FIRST! It’s the only one that worked for me.None of the above NumLk hacks work for me on Windows 10. Any more ideas you can give me to try. Will be appreciated.@Richard,Have you by any chance tried setting Num-Lock to ‘ON’ in the System BIOS? That’s usually the best place to start. If that doesn’t work either then you’ll have to sit tight and wait for Microsoft to release a fix. Hopefully it won’t be long before they do, I think this is a global phenomenon and affects most users.I posted this in the Classic Shell Forum. Does it fix it for you?I’m using Classic Shell 4.3.1 . . . I have found that in order for this setting in the Registry to work, which will make NumLock “on”:HKEY_USERS \ .DEFAULT \ Control Panel \ Keyboard \ InitialKeyboardIndicators Default: 2147483648 Change it to: 2147483650It’s necessary to [un-check] “Enable hybrid shutdown”:Classic Start Menu Settings / Main Menu / [un-check] Enable hybrid shutdown . . . (Is this primarily for Win 8, which is not used much today? Maybe it should be un-checked by default?)Please see this page for the full story:With this BIOS setting, why isn’t NumLock enabled / “On” when it gets to the Login screen? . . . https://h30434.www3.hp.com/t5/Desktop-Software-and-How-To-Questions/With-this-BIOS-setting-why-isn-t-NumLock-enabled-quot-On/m-p/6186353#M68595My registry entry is set to 2. I changed to 80000002 and shut down and started. Numlock not on and registry was back at 2. I changed the key to 42147483650 and shut down and started. numlock was still not on and key was back to 2. I tried the third suggestion and at logon turned on the numlock then shut down. Now the numlock key is on at startup and the registry key remains at 2. I guess this will work until the next update :(‘try to set the value “InitialKeyboardIndicators” to 2147483650.’ worked for me on Windows 10 build 10240, thanks :-)Ah ha…! I found a permanent fix which will work for anyone! Stick some duck tape over the Num-Lock key!!!Joking of course LOL…, if only it were that simple! :)This pattern worked for me with Win10. Makes absolutely no sense but it worked. *** *** *** *** *** Win10: Change the value of …Control Panel/Keyboard/InitialKeyboardIndicators to 2147483650 for ALL USERS. not only for .Default (mine current user was 2). Then SHUTDOWN computer. Turn on computer and wait for login screen (NumLock is still off). Enable NUMLOCK SHUTDOWN computer. Turn on computer. Now I have always numlock enabled on login screen! (value in current user is again 2 :-) Crazy.This method worked for me! MSI GE60 2PC Windows 8 Upgraded to Windows 10! Thanks!Win10 64bit from a Win 8.1 machine. I did all of the above and nothing worked. Except the BIOS, I wont touch BIOS unless I really really have to. What did work in the end was the disabling the ‘Fast Startup’ option. Don’t know if it was a combination of all the ideas or just the Fast Startup was the key.I was changing the wrong registry key number. Misdirect to change the setting HKEY_CURRENT_USER which by default kept changing back to 2 on Windows 10. THIS IS NOT THE RIGHT LOCATIONThis needs to be done under HKEY_USERS and changed the initialkeyboardindicator for ALL users. HKEY_USERS => .DEFAULT=> Contorl Panel => Keyboard edit the Initial Keyboard Indicator registry file to 2147483650 close registry, shutdown, reboot, at logon screen enable Numlock, proceed straight to the bottom right corner choose shutdown, reboot computer and BOOOOM your Numlock key should be working now.TODAY, into the release at AUGUST/2015 (08/15) you will see (in Regedit) 2147483648 ………(48) CHANGE TO the well suggested 2147483650 SignOut your Windows 10’s USER & ALL RIGHT.Thank you very much! The registry tweak worked on my new Dell 17″ laptop running Windows 10 Pro.Much appreciated after spending a lot of time on this with other suggestions.What about Enbable Scroll Lock? What number I use instead of 2147483650?It didn’t workFound a solution which worked beautifully! On windows 10.I first tried to find a num lock option in the bios, none found. (ASUS G53SW)Then tried to reboot from login screen with num lock on to see if the system would remember it, didn’t work.Then tried changing values in the registry :HKEY_USERS\.DEFAULT\Control Panel\Keyboard –> “InitialKeyboardIndicators”changed from default value “214783648” to “214783650”, didn’t work.changed to “80000002”, didn’t work.changed to “2”, didn’t work.I reverted it to “214783650”, then for some strange reason i thought that maybe windows tries to activate it, but has trouble communicating with the keyboard controller.Went on my manufacturer’s support site, downloaded the intel chipset driver update utility…… and problem solved !!!new computer try window 10After having followed the solutions above back in August, the problem was fixed. However, with the recent November update the problem is back again. I checked everything. There was no newer driver, the registry setting was the same. But Microsoft in there great wisdom and knowing everything better had changed the power setting back to Fast StartUp. With that unselected again I can at least get the NumLock to be on when starting up. If MS want users to “enjoy the fast start experience” maybe they should fix the NumLock bug so the BIOS settings are used.The clue for me was that in fast startup mode, the machine retains the registry in a hibernation mode when shut down. Every time I changed the registry, then shut down and started up again, the registry values had changed back. The steps I took were 1. turn off fast startup. 2. Change the registry values as described by many. 3. Ensure that Num Lock is ON (this seemed to be most important!). 4. Shut down completely. 5. Switch the machine on and let it completely boot. 6. Check the registry values. (In my case, they had not altered). 7. Check the status of Num Lock. (In my case, it was now on). 8. Reinstate fast startup. I think the new registry values are now saved when the machine is switched off, and the computer has been started up and switched off many times, each time with the Num Lock ON!! I wonder what Microsoft programmers were thinking when they decided that Num Lock should be off? I imagine that many people like me have the numeric pad for a reason, and wish to use it. The other thing I did was to install TrayStatus, and it works a treat. Hope this helps and works for other frustrated users.For the one that doesn’t require Registry, that didn’t work too well. It did start the computer with the num lock on but when I enter my password it says “Parameter incorrect.”You computer is probably a laptop without the separate NumLock/digits block. So when NumLock is on, some letters act as numbers. I saw such issue on old Thinkpad models.Registry editing was worked for me. 2147483650Thanks for feedbackthank you, number 2147483650 worked like charmAfter the upgrade from Windows 7 to 10, nothing would enable the num lock on at startup or after a reboot. I accidentally found that I had to update the motherboard chipset drivers for num lock to be on at startup. (I was having USB driver issues and updated my system chipset.)The actions I wrote about on 27 December are working fine for me. Every time I start the machine, my Num Lock is enabled, just as I require. However, if I leave the machine for some time, letting it go into SLEEP mode, on wake-up, the Num Lock disables! At this stage, I have overcome that problem by going in to the power settings, and changing the time before the computer goes into SLEEP mode to NEVER. The screen still turns off after 5 minutes, but the computer is not asleep. On moving the mouse or touching a key, the screen comes on and the Num Lock is still enabled. I have changed that setting only on the setting for when the computer is on mains, which is how I usually use it. I intend to get hold of a program that will monitor the computer coming out of sleep, and step by step, tell me which programs are active. That will identify the culprit that is turning off the Num Lock when coming out of sleep. If anyone has such a program, please let me know, otherwise, I think I might be able to get one from a colleague. At this stage, I never have to re-enable my Num Lock, and all is good! Hope this helps someone.On my Toshiba laptop with Win 10, the value was already 80000002. Changed to 2147483650. Did nothing/no change/NumLock still does not automatically come on after a cold reboot.After many days looking for a solution to enable Num Lock on two different keyboards (Dell and Rapoo), adjusting the register, calling Dell, searching in tens of forums, I got a very simple and obvious solution that might also work for many people. Just go to Control Panel – Ease of Access Center – select Keyboard and turn off Use the keyboard as mouse pointer. It seems that on some keyboards the activations of this feature has priority over other settings and even if you set the NumLock on, it does not work. I hope it helps you.None of the methods listed worked for me but I found one that does work every time. It has to do with the last key hit before the computer shuts down. Here it is: 1. with the number lock key on (light on) shut down the PC. 2. when the light on NumLock key goes out during shut down hit the key again to turn it back on; this will be the last key hit before the PC actually shuts down. 3. you will see the light on the key go out again as the PC shuts down but the next time you turn it on the Num Lock key will be put on as PC boots up. This has worked every time since I tried it. The important thing is to watch the key light go out during shut down and then turn it back on and let PC shut down.nice find! thanks for sharing.Thanks. First advice (tick numlock and reboot) worked fine for me. I now has numlock on by default.this is very good!I have tried everything within the registry that was mentioned here, nothing worked. But I found a simple solution. Push the numlock key, and keep for about 8 seconds. Then a sound, and the numeric keypad is working. Until the next reboot, then again, push the ………The intial registry suggestion didn’t work for me either – build 10390 Windows 10 AE.So I did a scan of the registry for that key, and updated every entry I came across – there were 5 in all that had the be updated. Since then it’s working fine.Control Panel > Power Options > ‘Choose What the Power Buttons Do’ [text link; upper left of window] > ‘Change Settings that are Currently Unavailable’ [text link; upper middle of window] > Uncheck ‘Turn On Fast Startup’ [checkbox] > Save Changes [button].Thanks Chris, working well on Windows 10If for some reason Anniversary Update breaks your Numlock registry keys again, try this script: https://support.microsoft.com/en-us/kb/262625 It’s better than relying on Registry keys for numlock state. It can also be modified for CAPSLOCK or SCROLL LOCK.The 2147483650 registry hack works fine with windows 10, including the new Anniversary Update and can’t cause any damage. However you need to take care you’re in the correct InitialKeyboardIndicators key under HKEY_USERS and not the one under HKEY_CURRENT_USER. If the key has a single digit value, eg “2”, you are in the wrong one and it won’t work.@Bob So much work so such simple thing.. Why Microsoft won’t fix this :(@Anthony I’ve tried ‘2’ and ‘2147483650 ‘ but they’re not working.. Now I regret for updating to anniversary update.. :(Many thanks – it worked perfectly using 80000002 on Windows 10 Home…Scenario 1: Fast Startup enabled This mode helps to speed up the startup for regular hard drives (not much for ssd’s) 1.1 Registry solution will help only on restart (not shut down then powering up) 1.2 Enabling “Numlock” while in login screen and shutting down from there will be overridden later by the shutdown from desktop which disables the “Numlock” again This case is a bug in windows since very long times and was reported multiple of times to Microsoft Scenario 2: Fast Startup disabled Turn on “Numlock” and it is kept on for both restart and shutdown then powering up This mode is good if you have an ssd and considering the time to press the key and the frustration I suggest to keep it off until Microsoft solves this issue.Thank youIt’s work. I have tried everything within the registry that was mentioned here, nothing worked. But I found a simple solution. Push the numlock key, on windows logon and restart again. Thanks so muchAlso to be noted,if you use a regedit hack to put a Shut down icon in your tray,it will fast shutdown but NOT save keyboard settings like numlock,capslock etc.When you boot up again the keyboard will be returned to native setting.Nice Idea. Thank you.welp, i formated and installed win10 v1703, the numlock works at boot after doing this manip.now, how do i make it stay on, when i lock (win+L) the thing ?Activate numlock on logon screen worked fine for me! So simple! Thank you! ❤

Keywords on this domain

Search Results related to nconnect.net on Search Engine

Alexa Rank

Alexa

GLOBAL RANK

9,299,994
Alexa

Alexa Reach

0.0000146040
Alexa

Page length

N/A
Alexa

Alexa Rank Country N/A

N/A
Alexa

Daily Unique Visitors

331
Alexa

Monthly Unique Visitors

9,925

Vistor via Country

Country lang
Country code
Total visitor

United States

2,123

Indonesia

1,660

Taiwan

540

United Kingdom

479

Brazil

434

Nigeria

379

Egypt

319

Hong Kong

301

Canada

301

Australia

262

Philippines

188

India

183

Malaysia

180

Spain

149

Germany

145

Mexico

139

France

131

Italy

121

Turkey

111

Iraq

101

Thailand

99

Netherlands

95

Israel

94

Cambodia

78

Algeria

61

Ireland

55

Romania

53

Jordan

49

Poland

47

Ghana

45

Argentina

43

South Africa

39

Belgium

35

Czechia

32

Ukraine

30

Japan

30

Morocco

29

South Korea

28

Lebanon

27

Saudi Arabia

26

Austria

25

Hungary

24

Sweden

23

Singapore

22

Pakistan

21

Bangladesh

20

Denmark

19

Greece

18

Alexa Traffic Graph

Alexa daily traffic trend graph
Alexa Statistics Graph for nconnect.net
Alexa daily pageviews (percent) graph
Alexa Statistics Graph for www.nahklick.de
Alexa daily pageviews per user graph
Alexa Statistics Graph for nconnect.net
Alexa time on site (in minutes) graph
Alexa Statistics Graph for www.nahklick.de
Alexa bounce rate (percent) graph
Alexa Statistics Graph for nconnect.net
Alexa search visits graph
Alexa Statistics Graph for nconnect.net

SEOquake Zone

Title Tips
Description Tips
Keywords Tips
Viewport Tips
Icon
UTF-8

Mini site formation by Alexa Rank

MOZ Rank

DNS Record

Host Type Class TTL Extra

Hosting and Whois Zone

Domain infomation Domain Name: NCONNECT.NET
Registry Domain ID: 2019930_DOMAIN_NET-VRSN
Registrar WHOIS Server: whois.namecheap.com
Registrar URL: http://www.namecheap.com
Updated Date: 2019-11-12T16:49:00Z
Creation Date: 1995-10-13T04:00:00Z
Registry Expiry Date: 2026-10-12T04:00:00Z
Registrar: NameCheap, Inc.
Registrar IANA ID: 1068
Registrar Abuse Contact Email: [email protected]
Registrar Abuse Contact Phone: +1.6613102107
Domain Status: clientTransferProhibited https://icann.org/epp#clientTransferProhibited
Name Server: DNS1.REGISTRAR-SERVERS.COM
Name Server: DNS2.REGISTRAR-SERVERS.COM
DNSSEC: unsigned
URL of the ICANN Whois Inaccuracy Complaint Form: https://www.icann.org/wicf/
>>> Last update of whois database: 2026-04-13T13:41:01Z <<<

For more information on Whois status codes, please visit https://icann.org/epp

NOTICE: The expiration date displayed in this record is the date the
registrar's sponsorship of the domain name registration in the registry is
currently set to expire. This date does not necessarily reflect the expiration
date of the domain name registrant's agreement with the sponsoring
registrar. Users may consult the sponsoring registrar's Whois database to
view the registrar's reported date of expiration for this registration.

TERMS OF USE: You are not authorized to access or query our Whois
database through the use of electronic processes that are high-volume and
automated except as reasonably necessary to register domain names or
modify existing registrations; the Data in VeriSign Global Registry
Services' ("VeriSign") Whois database is provided by VeriSign for
information purposes only, and to assist persons in obtaining information
about or related to a domain name registration record. VeriSign does not
guarantee its accuracy. By submitting a Whois query, you agree to abide
by the following terms of use: You agree that you may use this Data only
for lawful purposes and that under no circumstances will you use this Data
to: (1) allow, enable, or otherwise support the transmission of mass
unsolicited, commercial advertising or solicitations via e-mail, telephone,
or facsimile; or (2) enable high volume, automated, electronic processes
that apply to VeriSign (or its computer systems). The compilation,
repackaging, dissemination or other use of this Data is expressly
prohibited without the prior written consent of VeriSign. You agree not to
use electronic processes that are automated and high-volume to access or
query the Whois database except as reasonably necessary to register
domain names or modify existing registrations. VeriSign reserves the right
to restrict your access to the Whois database in its sole discretion to ensure
operational stability. VeriSign may restrict or terminate your access to the
Whois database for failure to abide by these terms of use. VeriSign
reserves the right to modify these terms at any time.

The Registry database contains ONLY .COM, .NET, .EDU domains and
Registrars.