seoul-hotels-kr.com security report

Certificate, security headers, email authentication, DNS, registration, and exposed hosts — from public sources.

68risk

Elevated

Several issues worth triaging this week.

0Critical

2High

4Medium

4Low

2Info

Collected 9 hours ago14.4sfrom cache

Certificate Transparency1
DNS resolution1
Network ownership0
CDN / WAF detection0
Exposed ports & CVEs3
Registration
DNS posture4
Email authentication0
Certificate
Security headers0
Archived URLs
Analysis12

noteCertificate inspection is unavailable in this runtime.
noteNetwork ownership lookup is unavailable in this runtime; ASN and org are omitted.
noteCDN/WAF detection is unavailable in this runtime.

Nothing tells receiving mail servers which hosts may send as @seoul-hotels-kr.com, so anyone can. Phishing that impersonates this domain will land in inboxes.
What to do
Publish an SPF TXT record listing your senders and ending in -all.
asset: seoul-hotels-kr.com
SPF and DKIM alone do not protect the From: address a person sees. Without DMARC, a spoofed message can pass SPF for some other domain and still display yours.
What to do
Publish `_dmarc.seoul-hotels-kr.com TXT "v=DMARC1; p=none; rua=mailto:dmarc@seoul-hotels-kr.com"`, review the reports, then move to p=quarantine and p=reject.
asset: seoul-hotels-kr.com
Without HSTS the browser will still try http:// first on a fresh visit, which is the window an on-path attacker uses.
What to do
Send `Strict-Transport-Security: max-age=31536000; includeSubDomains` once you are sure everything works over HTTPS.
asset: https://www.seoul-hotels-kr.com/
CSP is the main defence that limits what an injected script can do. Without it, any XSS bug is fully exploitable.
What to do
Start with a report-only policy, tighten it against the reports, then enforce.
asset: https://www.seoul-hotels-kr.com/
No X-Frame-Options or CSP frame-ancestors directive, so another site can load this page invisibly inside its own and trick users into clicking.
What to do
Send `X-Frame-Options: DENY` or `Content-Security-Policy: frame-ancestors ’none’`.
asset: https://www.seoul-hotels-kr.com/
The browser will also send this cookie over plain http://, where it can be captured.
What to do
Add `Secure` to the cookie.
asset: https://www.seoul-hotels-kr.com/
Lets browsers guess content types, which turns some upload and text endpoints into script injection points.
What to do
Send `X-Content-Type-Options: nosniff` on every response.
asset: https://www.seoul-hotels-kr.com/
Full URLs — including any tokens or IDs in them — are sent to every third party the page links to.
What to do
Send `Referrer-Policy: strict-origin-when-cross-origin`.
asset: https://www.seoul-hotels-kr.com/
Exact versions in response headers let anyone match the server against a CVE feed without touching it.
What to do
Strip version tokens (`ServerTokens Prod`, `server_tokens off`, remove X-Powered-By).
asset: https://www.seoul-hotels-kr.com/
Answers for this domain are not signed, so a resolver cannot tell a forged response from a real one.
What to do
Enable DNSSEC at your DNS host and publish the DS record at the registrar.
asset: seoul-hotels-kr.com
Mail to this domain can be downgraded to plaintext by an on-path attacker, because senders have no way to know TLS is required.
What to do
Publish an MTA-STS policy (a TXT record plus a small HTTPS-hosted file).
asset: seoul-hotels-kr.com
Any public certificate authority may issue certificates for this domain. CAA lets you name the ones allowed to.
What to do
Add a CAA record naming your CA, e.g. `0 issue "letsencrypt.org"`.
asset: seoul-hotels-kr.com

final https://www.seoul-hotels-kr.com/status 200time 2176msstack cloudflare · Next.js 6.1.2

✓http:// redirects to https://
✗Strict-Transport-Security
✗Content-Security-Policy
✗Clickjacking protection
✗X-Content-Type-Options
✗Referrer-Policy
–Permissions-Policyoptional
–security.txt publishedoptional — tells researchers where to report bugs

✗Cookie PHPSESSID
no Secure · HttpOnly · SameSite=lax

✓Receives mail via 1 server
seoul-hotels-kr-com.mail.protection.outlook.com
✗SPF
no record
✗DMARC
no record
!MTA-STSinbound mail can be downgraded to plaintext

!DNSSECanswers can be forged
–CAAany CA may issue
–IPv6 (AAAA)IPv4 only
✓4 nameservers
dns1.bigrock.com dns2.bigrock.com dns3.bigrock.com dns4.bigrock.com

✓Registered with BigRock Solutions Ltd10.2 years old
seoul-hotels-kr.com
✓Registration expiry295 days
2027-06-29
✓Transfer lock
client transfer prohibited
✓4 nameservers at registry
dns1.bigrock.com dns2.bigrock.com dns3.bigrock.com dns4.bigrock.com

Address	Ports	CVEs	Edge	Network
158.247.205.191 seoul-hotels-kr.com +3	5380443	0	direct	—

Archived URLs

Endpoints the Wayback Machine has kept — config files, backups, scripts. Slow to fetch, so it is here on request.

seoul-hotels-kr.com security report

Elevated

Findings

Security headers

Email authentication

DNS

Registration

Hosts

Hostnames