From Wikipedia, the free encyclopedia
Jump to navigation Jump to search

A refback is one of four types of linkbacks, methods for Web authors to request notification when somebody links to one of their documents. This enables authors to keep track of who is linking to, or referring to their articles.

A Refback is simply the usage of the HTTP referrer header to discover incoming links. Whenever a browser traverses an incoming link from Site A (originator) to Site B (receptor) the browser will send a referrer value indicating the URL from where the user came. Site B might publish a link to Site A after visiting Site A and extracting relevant information from Site A such as the title, meta information, the link text, and so on.[1]

Refback only requires Site B to be Refback enabled in order to establish this communication. Refback requires Site A to physically link to Site B. Refback also requires browsers to traverse the links.

Security issues[edit]

If the referred-to site does not validate the referring site URL, it may be subject to referrer spam (due to forged referrer headers) and may end up with links to dynamic web content and private web sites, such as web-based e-mail. Validating the referrer was considered to be a potential denial-of-service attack vector, but is such a trivial attack that modern web server software has been hardened against this kind of attack.[2]

See also[edit]

  • Linkback, the suite of protocols that allows websites to manually and automatically link to one another.
  • Pingback, a similar protocol but more difficult as it requires for physical links
  • Trackback, a similar protocol but more prone to spam
  • Search engine optimization


  1. ^ "Web Design Forum for Web Development and Programming - LinkBacks". Juno Web Design. Archived from the original on August 26, 2012. Retrieved October 28, 2012.
  2. ^ "IRC logs: freenode / #whatwg / 20111122". Archived from the original on December 4, 2011. Retrieved November 22, 2011.

External links[edit]


None of the audio/visual content is hosted on this site. All media is embedded from other sites such as GoogleVideo, Wikipedia, YouTube etc. Therefore, this site has no control over the copyright issues of the streaming media.

All issues concerning copyright violations should be aimed at the sites hosting the material. This site does not host any of the streaming media and the owner has not uploaded any of the material to the video hosting servers. Anyone can find the same content on Google Video or YouTube by themselves.

The owner of this site cannot know which documentaries are in public domain, which has been uploaded to e.g. YouTube by the owner and which has been uploaded without permission. The copyright owner must contact the source if he wants his material off the Internet completely.

Powered by YouTube
Wikipedia content is licensed under the GFDL and (CC) license