dns   39552

« earlier    

Domains abfangen mit der FritzBox als DNS-Server | Adrian Jagusch
Schritt 1
Der Computer, auf den die Verbindungen umgeleitet werden sollen, muss im Netzwerk angemeldet sein. Er benötigt jetzt eine feste IP-Adresse. Das geht im Fritz-Box-Interface über das Menü Heimnetz und den Bearbeiten-Button neben dem ausgesuchten Gerät. Hier muss das Häkchen bei Diesem Netzwerkgerät immer die gleiche IPv4-Adresse zuweisen. gesetzt werden. Abspeichern und IP-Adresse merken - diese brauchen wir im nächsten Schritt.
server  dns  fritzbox 
7 hours ago by syrabo
Fox-IT reveals hackers hijacked its DNS records, spied on clients' files
Protect your website's DNS entries. Choose decent, unique passwords. Enable two-factor authentication on the account. And, if you have the clout, request that your DNS registrar confirm with a manual phone call if there is ever an attempt to point the records elsewhere.
dns  hacking  mitm 
2 days ago by whip_lash
Chrome 63 forces .dev domains to HTTPS via preloaded HSTS
Chrome 63 (out since December 2017), will force all domains ending on .dev (and .foo) to be redirected to HTTPS via a preloaded HTTP Strict Transport Security (HSTS) header
chrome  dev  DNS  TLD  domain  redirect  https  issue  security 
2 days ago by ebouchut
xip.io is a magic domain name that provides wildcard DNS for any IP address.
xip.io is a magic domain name that provides wildcard DNS
for any IP address. Say your LAN IP address is
Using xip.io, resolves to
www. resolves to
mysite. resolves to
foo.bar. resolves to
development_tools_online  devops  dns 
2 days ago by slavko
Fox-IT hit by cyber attack - Fox-IT (ENG)
What a wonderfully transparent after-action review of an incident. Though changing the registrar password regularly doesn't seem like it would buy them much, as they kept their password in a vault and rarely used it (low chance of extraction/exfil), and the subtle implication the registrar got owned. Though as a mitigation to lack of 2FA, at the registrar, maybe worthwhile. But the real need is watching for abnormal events, which requires a registrar change feed or external monitoring, as you need to trigger on registrar change events or general DNS SOA changes.
DFIR  case  study  DNS  registrar  hijack  MitM  reference  information 
3 days ago by asteroza

« earlier    

related tags

2017  adblock  adfraud  admin  amazon  android  app  apple  asg  auto53  autoscaling  aws  bestpractices  bgp  bind  blacklists  block  blockchain  blocklists  bonjour  botnet  cache  case  censorship  certbot  certificates  certonly  check  chrome  cname  conference  crypto  ddos  dec17  dev  development_tools_online  devops  dfir  diy  dns.leak  dnsproxy  dnssec  dnsspy.io  documentation  domain  domains  encryption  facebook  fix  free  fritzbox  future  gaming  git  go  golang  google  graylog  hacking  haproxy  heroku  hijack  hosting  hostnames  howto  http  http2  https  ietf  information  infosec  internet  iot  ip  isp  issue  lang:en  lede  letsencrypt  linux  lists  loadbalancer  location  macos  malware  manual  metasploit  meterpreter  microsoft  mikrotik  minecraft  mirai  mitm  netneutrality  network  networking  networks  nslookup  ntp  openconnect  openwrt  ops  pentesting  policy  priacy  privacy  propagation  protocol  protocols  proxy  python  quic  r53  reddit  redirect  reference  registrar  reputation.data  research  route-53  router  rpi  russia  scams  script  security  server  service-discovery  service  ssl  standard  study  styleguide  sysadmin  systems  t  tcp  tech  technology  test  testing  tld  tls  tool  tools  torrent  trends  trust  tunnel  tunnelling  txt  udp  url  veracity  video  vpn  web-site  webdev  webhosting  webrtc  whois  work 

Copy this bookmark: