How privacy works
Private lookups are not added to public searches, stored reports or change history. This does not remove a report that was already public. Your choice lasts for this browser session.
Who hosts hackernews.com?
Answer
news.ycombinator.com uses the M5 Computer Security network; the hosting company is unconfirmed.
Checked 2 hours ago from Cloudflare ZRH in 2.5 s. This is a saved result.
What needs attention
Prioritized observations from this check. Review changes with whoever manages the website.
- Improve
Review browser security headers
Content-Security-Policy, Referrer-Policy, Permissions-Policy did not meet the conservative header checks. This is not a complete security audit.
Next step: Review these headers with the site developer and test policy changes before enforcing them.
- Good to know
Only the network operator is identified
The visible IP network is known, but no hosting-specific evidence confirms the company or reseller serving the site.
Next step: Use the evidence as a network attribution and verify the hosting provider with the website owner if needed.
Evidence by layer
The company operating a network and the company selling the hosting can be different.
Network operators
M5HOSTING - M5 Computer Security, US
Network ownership alone does not confirm the retail hosting provider.
How we know
- 209.216.230.207 belongs to AS21581 (M5HOSTING - M5 Computer Security, US), reverse DNS news.ycombinator.com
- 2606:7100:1:67::26 belongs to AS21581 (M5HOSTING - M5 Computer Security, US)
Servers
The addresses the name points to and the networks that own them.
news.ycombinator.com (where the site redirects)
- 209.216.230.207M5 Computer Security
- 2606:7100:1:67::26M5 Computer Security
hackernews.com (the address you entered)
- 143.204.55.92Amazon CloudFront
- 143.204.55.15Amazon CloudFront
- 2600:9000:20a5:7200:c:bfb4:2d00:93a1Amazon Web Services
- 143.204.55.63
- 143.204.55.105
- 2600:9000:20a5:200:c:bfb4:2d00:93a1
- 2600:9000:20a5:7400:c:bfb4:2d00:93a1
- 2600:9000:20a5:6000:c:bfb4:2d00:93a1
- 2600:9000:20a5:2200:c:bfb4:2d00:93a1
- 2600:9000:20a5:a400:c:bfb4:2d00:93a1
- 2600:9000:20a5:2600:c:bfb4:2d00:93a1
- 2600:9000:20a5:9a00:c:bfb4:2d00:93a1
Reachable over IPv6.
Website
What the site answered when we visited its home page.
- Status
- 200 OK
- Address
- https://news.ycombinator.com/
- Page title
- Hacker News
- HTTPS
- Yes
- HTTP/3
- Not advertised
- Response time
- 542 ms from Cloudflare ZRH
Redirects (1)
- 301https://hackernews.com/
- 200https://news.ycombinator.com/
Security headers
- Strict-Transport-Security
- Content-Security-Policy (too weak)
- Clickjacking protection
- X-Content-Type-Options
- Referrer-Policy (too weak)
- Permissions-Policy
DNS
Who answers for the domain name, and its records.
- DNS provider
- Amazon Route 53
- Name servers
- ns-1352.awsdns-41.org
ns-1945.awsdns-51.co.uk
ns-578.awsdns-08.net
ns-60.awsdns-07.com - Zone
- hackernews.com
- DNSSEC
- Not signed
- Certificates
- issue amazon.com
All DNS records (17)
| Type | Name | Value | TTL |
|---|---|---|---|
| A | hackernews.com | 143.204.55.92 | 60 |
| A | hackernews.com | 143.204.55.15 | 60 |
| A | hackernews.com | 143.204.55.63 | 60 |
| A | hackernews.com | 143.204.55.105 | 60 |
| AAAA | hackernews.com | 2600:9000:20a5:7200:c:bfb4:2d00:93a1 | 60 |
| AAAA | hackernews.com | 2600:9000:20a5:200:c:bfb4:2d00:93a1 | 60 |
| AAAA | hackernews.com | 2600:9000:20a5:7400:c:bfb4:2d00:93a1 | 60 |
| AAAA | hackernews.com | 2600:9000:20a5:6000:c:bfb4:2d00:93a1 | 60 |
| AAAA | hackernews.com | 2600:9000:20a5:2200:c:bfb4:2d00:93a1 | 60 |
| AAAA | hackernews.com | 2600:9000:20a5:a400:c:bfb4:2d00:93a1 | 60 |
| AAAA | hackernews.com | 2600:9000:20a5:2600:c:bfb4:2d00:93a1 | 60 |
| AAAA | hackernews.com | 2600:9000:20a5:9a00:c:bfb4:2d00:93a1 | 60 |
| NS | hackernews.com | ns-1352.awsdns-41.org | 172800 |
| NS | hackernews.com | ns-1945.awsdns-51.co.uk | 172800 |
| NS | hackernews.com | ns-578.awsdns-08.net | 172800 |
| NS | hackernews.com | ns-60.awsdns-07.com | 172800 |
| CAA | hackernews.com | 0 issue "amazon.com" | 300 |
This domain does not receive email.
Anyone can still send mail pretending to be this domain. Publishing v=spf1 -all and a DMARC record with p=reject would stop that.
- Mailbox provider
- None
- SPF
- Missing
- DMARC
- Missing
- MTA-STS
- Not enabled
Domain registration
- Registrar
- Amazon Registrar, Inc.
- Registered
- 29 Jul 1998 (28 years ago)
- Paid until
- 28 Jul 2027 (in 273 days)
- Last changed
- 23 Jun 2026
- Status
- Transfer lock (registrar)
- DNSSEC at registry
- No
- Source
- rdap.verisign.com
Observed changes
A compact record of what changed between public checks. Rechecks happen only when someone requests them.
History starts with saved public observations. No earlier changes are inferred.
Something look wrong? Report an incorrect result
Tell us which result needs a second look. Reports are reviewed privately and do not change detection automatically. Please do not include personal or confidential information.
Last 10 searches
| Domain Name | Host |
|---|---|
| byd.com | Unknown |
| tesla.com | Akamai (host hidden) |
| x.com | Fastly (host hidden) |
| apple.com | Akamai (host hidden) |
| news.ycombinator.com | Unknown |
| seo.com | Kinsta |
| claude.ai | Unknown |
| dominom.com | Unknown |
| divinative.com | Cloudflare (host hidden) |