Robot | Path | Permission |
GoogleBot | / | ✔ |
BingBot | / | ✔ |
BaiduSpider | / | ✔ |
YandexBot | / | ✔ |
Title | LoginWithHN |
Description | (Unofficially) Login with (Unofficial) Login with |
Keywords | N/A |
WebSite | loginwithhn.com |
Host IP | 116.202.171.246 |
Location | India |
Site | Rank |
US$1,274
Last updated: 2023-05-15 21:55:00
loginwithhn.com has Semrush global rank of 0. loginwithhn.com has an estimated worth of US$ 1,274, based on its estimated Ads revenue. loginwithhn.com receives approximately 147 unique visitors each day. Its web server is located in India, with IP address 116.202.171.246. According to SiteAdvisor, loginwithhn.com is safe to visit. |
Purchase/Sale Value | US$1,274 |
Daily Ads Revenue | US$1 |
Monthly Ads Revenue | US$35 |
Yearly Ads Revenue | US$423 |
Daily Unique Visitors | 9 |
Note: All traffic and earnings values are estimates. |
Host | Type | TTL | Data |
loginwithhn.com. | A | 3599 | IP: 116.202.171.246 |
loginwithhn.com. | A | 3599 | IP: 88.198.25.107 |
loginwithhn.com. | A | 3599 | IP: 162.55.94.219 |
loginwithhn.com. | A | 3599 | IP: 188.40.104.212 |
loginwithhn.com. | NS | 26477 | NS Record: ns-1831.awsdns-36.co.uk. |
loginwithhn.com. | NS | 26477 | NS Record: ns-236.awsdns-29.com. |
loginwithhn.com. | NS | 26477 | NS Record: ns-659.awsdns-18.net. |
loginwithhn.com. | NS | 26477 | NS Record: ns-1489.awsdns-58.org. |
loginwithhn.com. | MX | 3600 | MX Record: 10 mail.loginwithhn.com. |
loginwithhn.com. | TXT | 3600 | TXT Record: v=spf1 a mx -all |
Home FAQ Credits App (Unofficially) Login with HN An OpenID Connect (OAuth2) provider for HackerNews Login With HN Register a OAuth2 application This project is not affiliated with HackerNews or YCombinator in any way Some Questions you might have How does it work? Assuming you understand how the OpenID Connect flow generally works, this app works quite simply: A user clicks "Login with HN" On LoginWithHN, the user is given a chance to enter their hackernews username LoginWithHN generates a unique one-time-use code that the user must then put into their profile within 5 minutes LoginWithHN watches the user’s profile until the code shows up Once LoginWithHN verifies the users profile contains the code, the user is is considered authenticated (OAuth2 is really about Authorization but we’ll ignore that distinction for now). The user is shown a consent screen (that AuthZ we were talking about) and the only claims possible will be the username As always with OAuth2, you must handle session |
HTTP/1.1 307 Temporary Redirect Location: https://loginwithhn.com/ Date: Fri, 14 Jan 2022 10:54:22 GMT Content-Length: 18 Content-Type: text/plain; charset=utf-8 HTTP/2 200 accept-ranges: bytes access-control-allow-credentials: true cache-control: public, max-age=0 content-type: text/html; charset=UTF-8 date: Fri, 14 Jan 2022 10:54:22 GMT etag: W/"1659-17e54c435a0" last-modified: Thu, 13 Jan 2022 18:47:32 GMT referrer-policy: same-origin strict-transport-security: max-age=63072000; includeSubDomains; preload vary: Origin x-content-type-options: nosniff x-frame-options: DENY x-powered-by: Express x-xss-protection: 1; mode=block content-length: 5721 |
Domain Name: LOGINWITHHN.COM Registry Domain ID: 2618854660_DOMAIN_COM-VRSN Registrar WHOIS Server: whois.registrar.amazon.com Registrar URL: http://registrar.amazon.com Updated Date: 2021-06-11T09:33:46Z Creation Date: 2021-06-11T09:22:45Z Registry Expiry Date: 2022-06-11T09:22:45Z Registrar: Amazon Registrar, Inc. Registrar IANA ID: 468 Registrar Abuse Contact Email: abuse@amazonaws.com Registrar Abuse Contact Phone: +1.2067406200 Domain Status: ok https://icann.org/epp#ok Name Server: NS-1489.AWSDNS-58.ORG Name Server: NS-1831.AWSDNS-36.CO.UK Name Server: NS-236.AWSDNS-29.COM Name Server: NS-659.AWSDNS-18.NET DNSSEC: unsigned >>> Last update of whois database: 2022-01-14T07:01:39Z <<< |